To manage recurring payments for creators, treat each cycle as a repeatable collection workflow: confirm the agreed schedule, prepare the payment instruction, submit the collection and follow its progress (Rebeam). The practical task is to connect customer permission, collection handling and record updates without confusing them (SEPA Direct Debit Core Scheme Rulebook).
Start with the groundwork in our earlier article: SEPA Direct Debit vs bank transfer for recurring euro payments
How do I manage each recurring payment cycle for my memberships?
Run each cycle in the same order, beginning with the agreement: check the collection against the member’s agreed subscription and mandate rather than treating the mandate as permission to collect independently of it (SEPA Direct Debit Core Scheme Rulebook). Next, tell the member each collection’s amount and due date in advance, as the rulebook requires (SEPA Direct Debit Core Scheme Rulebook). Then prepare and submit the collection on the agreed schedule and follow its progress, including any returns or exceptions (Rebeam). Finally, match the reported outcome to the membership record so your records stay aligned with your collections (Rebeam). This workflow concerns recurring euro collections through SEPA Direct Debit Core, not every recurring payment method.
The customer’s recurring mandate authorises regular collections initiated by you, so authorisation and the management of later collections are distinct parts of the relationship (SEPA Direct Debit Core Scheme Rulebook).
Prepare eligible euro collections using the API or batch submission route available through Rebeam. Confirm the submission deadline with your payment service provider so your instruction can reach the customer’s provider within the required processing period (SEPA Direct Debit Core Scheme Rulebook).
The European Payments Council’s rulebook requires the customer’s provider to receive the collection at least one inter-PSP business day before the due date. That deadline is for receipt by the customer’s provider, so do not treat it as your deadline for submitting the collection to your own provider.
Include the mandate-related information with every recurring collection, allowing it to travel with the collection through the payment service providers (SEPA Direct Debit Core Scheme Rulebook). If you extract that information from an electronic mandate, preserve its content rather than changing it while preparing the collection data.
The customer’s payment service provider must debit the customer’s account if the account status allows this (SEPA Direct Debit Core Scheme Rulebook). Use that condition when planning the cycle: the due date identifies when the debit is due, rather than an unconditional promise that it will happen.
Recurring collection workflow to use each cycle
Action | Rule or basis | How to verify |
|---|---|---|
Notify the customer of the amount and due date | Before the collection is sent to your provider, the customer is notified of its amount and due date. | Check that the notice states both and went out before the collection was sent. |
Include mandate-related data and meet the submission timeline | Every recurring collection carries mandate-related data; the payer's PSP must receive it at least one inter-PSP business day before the due date. | Check that the instruction contains mandate-related data and meets the stipulated advance-submission period. |
Investigate a reported duplicate | AM05 indicates that an identical collection was considered recently sent or processed. | Check whether the collection really was duplicated before deciding what to do next. |
Does the customer’s mandate replace the notice for later collections?
The mandate authorises collections under the agreed terms, so your customer does not need to initiate a separate bank transfer for every payment (Rebeam). It does not replace the notice, though: before you send each collection to your payment service provider, you must still notify the customer of the amount and due date (SEPA Direct Debit Core Scheme Rulebook).
Send that notice at the latest 14 calendar days before the due date unless another timeline is agreed between you and the customer (SEPA Direct Debit Core Scheme Rulebook). The notification of the amount and due date may be sent together with or as part of other commercial documents, such as an invoice, or separately, so a renewal does not necessarily need its own email.
An agreed schedule can provide advance notice for repetitive collections over a defined period, rather than requiring a separate notice containing only the next collection (SEPA Direct Debit Core Scheme Rulebook). For your membership workflow, check whether the forthcoming charge is covered by that schedule or needs its own notification of the amount and due date.
What should I do when a collection needs attention?
Read the reported outcome and any reason code before deciding how to respond, because the reason for a failed collection helps determine your next action (Guidance on reason codes for SEPA Direct Debit R-transactions). Rebeam states that collections can fail, be returned or be refunded, so submission alone is not proof of successful payment.
Exception messages distinguish refusals, rejects, returns, refunds and reversals according to where the issue arises in processing and who initiates or sends the message (Guidance On Reason Codes for SDD R-transactions).
For insufficient funds, the European Payments Council’s Guidance On Reason Codes for SDD R-transactions recommends contacting the customer to ensure funds are available in the account. AM04 identifies insufficient funds: the customer’s account does not contain enough funds to debit the full collection amount.
For a duplication report, check whether the collection really was duplicated before choosing your response (Guidance On Reason Codes for SDD R-transactions). The guidance explains that such a report means the interbank clearing house or the customer's bank considers an identical collection to have been sent or processed very recently.
For a refund request from the customer, the guidance suggests contacting the customer (Guidance On Reason Codes for SDD R-transactions). MD06 identifies a refund request by the end customer.
If the customer refuses a collection, contact the customer rather than assuming the payment failed for a technical reason (Guidance On Reason Codes for SDD R-transactions). The guidance describes a refusal as the customer deciding to refuse the collection after receiving advance notice, so the customer’s objection is the issue to address. MS02 identifies customer refusal of the collection at presentation.
Where the reason code reported for a failed collection is unspecified, do not invent a cause; base your reaction on what was actually reported (Guidance On Reason Codes for SDD R-transactions).
How do I keep subscription records aligned when payments or memberships change?
Use Rebeam’s reconciliation reporting to match collections to your business records. Keep the recorded payment outcome separate from the subscription decision, because a collection is a transaction distinct from the underlying customer contract (SEPA Direct Debit Core Scheme Rulebook).
Apply the customer agreement when deciding what a reported payment event means for the customer’s membership, rather than assigning an access consequence solely from the collection status (SEPA Direct Debit Core Scheme Rulebook).
On WordPress.com specifically, cancelling a recurring payment stops future charges, and the customer keeps access until the end of the period already paid for (Manage your recurring payments). Removing a subscription there ends it immediately, and the customer loses access to it right away (Manage your recurring payments).
On WordPress.com, changing the prices of a payment plan does not affect existing payments (Create and manage payment plans). Deleting a payment plan does not stop them either: existing payments will continue (Create and manage payment plans).
Mandate cancellation is handled between you and the customer without either payment service provider being involved in that cancellation process (SEPA Direct Debit Core Scheme Rulebook). You are responsible for archiving the cancellation, so include that record in your handling of the customer’s instruction rather than assuming the providers maintain it for you.
Once a mandate is cancelled, stop generating subsequent collections under it; if a further direct debit is needed, a new mandate must be established (SEPA Direct Debit Core Scheme Rulebook). The same applies after inactivity: if you do not present a collection under a mandate for a period of 36 months, starting from the date of the latest collection presented, even if rejected, returned or refunded, you must cancel the mandate and can no longer initiate collections under it (SEPA Direct Debit Core Scheme Rulebook).
After cancellation, a signed paper mandate must be retained under applicable national legal requirements and at least for the unauthorised-transaction refund period (SEPA Direct Debit Core Scheme Rulebook).
Sources
- SEPA Direct Debit Core Scheme Rulebook, European Payments Council AISBL, 05 October 2025
- Guidance On Reason Codes for SDD R-transactions, European Payments Council AISBL, 30 September 2026
- Guidance on reason codes for SEPA Direct Debit R-transactions, European Payments Council, 30 Sep 26
- Create and manage payment plans, WordPress.com, October 5, 2026
- Manage your recurring payments, WordPress.com, October 1, 2026