Recurring payments through a bank service using Redsys need the right operations enabled by the bank and an application that manages the schedule and service. A successful one-off payment does not prove that renewals are ready.
What to ask your bank
Describe the recurring service and request confirmation for your specific merchant terminal. Check permitted operations, contract terms, test access and the technical contact. “Automatic payments” is too vague unless you explain what you sell and how often you expect to charge.
Tokenisation and MIT payments
Redsys documentation describes reusable payment references and merchant-initiated transactions with prior authorisation. Their use must match the permitted operation. A stored card reference is not a complete subscription system.
| Component | Responsibility to assign |
|---|---|
| Bank and merchant terminal | Activation and operating terms |
| Integration | Preparing requests and checking responses |
| Subscription management | Who owes what, and when |
| Store or service | Opening and maintaining the relevant access |
| Administration | Matching payment, service period and document |
From signup to renewal
In a fictional monthly-access service, the customer sees the terms and authorises the initial journey. Confirmed payment opens the relevant period. The next renewal must be linked to that subscription, with its result recorded before deciding what happens to access.
The browser’s return to your site is part of the experience, but it should not be the only evidence of payment. Your server needs to check the result even if the customer closes the tab.
When renewal does not complete
Separate a confirmed decline from an unknown result. Resolve the previous attempt before requesting another charge. See how to handle unsuccessful renewals and decide what happens when someone requests a subscription pause.
Before switching it on
- Confirm operations for the merchant terminal.
- Explain terms and frequency to the buyer.
- Test initial payment and renewal.
- Handle repeated notifications without repeating actions.
- Stop scheduling when cancellation takes effect.
- Assign ownership of payment incidents and service access.
Already have a bank and website? Tell us which ones and how you want renewals to work. We can review what needs connecting.