To collect recurring payments through Redsys from an Andorran business, you need an online payment terminal configured for those operations, an initial authorisation from the buyer and an integration linking each charge to its subscription. You also need to define the schedule, service period and what happens after a failure, change or cancellation.
At AndorPay, we connect these parts using the capabilities enabled on your terminal. Redsys participates in payment processing; we manage the documented collection journey and its states; your application uses that information to deliver the service. This guide explains the complete cycle and the decisions to make before starting.
The requirements at a glance
Before setting up a subscription with Redsys, check four things:
- Enabled terminal: confirm with your bank which recurring operations and tokenisation features are available to your business.
- Authorised signup: define what the customer agrees to and how the reference for later charges is obtained.
- Schedule and status: associate each charge with its subscription and update the service when confirmation arrives.
- Ongoing management: decide how failures, cancellations and plan changes will be handled before opening signups.
The official MIT tokenisation documentation, in Spanish, describes the technical process. The following sections explain how these pieces fit your business and what we review when preparing an AndorPay integration.
What recurring payment means
A recurring payment is a charge repeated according to an accepted relationship and set of terms. In a subscription, those payments usually cover successive service periods. The payment frequency, access duration and renewal date should be understandable to the customer.
This is different from sending a link every month and waiting for a new manual purchase. It is not necessarily an instalment sale either: that divides one purchase into payments with a planned end. Define the relationship you are offering first, so the system can follow the appropriate rules.
You should be able to express the intended outcome simply: “This customer has this service for this period; this payment confirms it, and this is the next scheduled action.” That relationship prevents the business from depending on a list of transactions without context.
One-off or recurring payment: what is being agreed?
| Model | What the customer authorises | Example |
|---|---|---|
| One-off payment | A specific purchase, without renewals under that consent | Buying a product or a single session |
| Recurring subscription | Later charges under the agreed terms and frequency | Monthly membership or an annual service |
| Instalment payment | Several payments for one purchase with a planned end | A course with its total price split into instalments |
With a subscription, stopping future renewals and refunding a past charge are separate actions. Explain both conditions before sign-up and avoid presenting a recurring payment as a one-off purchase.
The roles of your bank, Redsys, AndorPay and your application
| Party | Responsibility in the journey | What you need to know |
|---|---|---|
| Contracted bank or institution | Terminal setup, enabled operations and settlement terms | Which terminal and capabilities you can use |
| Redsys | Processing the operation and returning the payment network outcome | Payment result and references |
| AndorPay | Session, operations, statuses and documented subscription cycle | Related customer, payment, period and events |
| Your store or application | The offer, fulfilment and access permissions | What the customer should receive in each situation |
| Your team | Commercial rules and incident handling | Who owns the case and what action is needed |
One project can coordinate several parties, but their roles still matter. Banking activation does not automatically connect payment to course access. An application with a member list does not enable recurring operations on the terminal either.
Our guide to the difference between gateways and subscription management expands on this division. Here we focus on how the whole arrangement works when the payment infrastructure uses Redsys.
Redsys does provide recurring capabilities
Official Redsys documentation includes tokenisation, subsequent operations and customer management with scheduled payments. The question is which journey is enabled for your merchant account and how it connects to the service you sell.
If you already have a schedule in the banking portal or another platform, identify it before adding a new one. Two systems trying to renew the same relationship can produce conflicting actions. Each subscription needs a clear owner responsible for requesting its payments.
In our flow, AndorPay coordinates subsequent charges through the connection prepared for the account. That schedule should not be duplicated in another dashboard unless a specific design requires it and keeps the operations separate.
Tokenisation, the first payment and MIT explained
A reference for subsequent payments
Tokenisation allows a payment method reference to be used instead of handling complete card details directly in the business application. The reference is obtained through the authorised journey and used according to the provider's configuration.
Your team needs to associate the method with the right customer and subscription. A member or user ID is not the banking token: those references perform different jobs. Keeping them separate lets you change commercial data without confusing it with the credential used for payment.
The buyer takes part in sign-up
During the initial operation, the buyer participates and accepts the relevant terms. Their bank may require authentication. In Redsys terminology, an operation initiated by the customer is called a CIT.
This initial step prepares the recurring relationship. A successful first payment does not prove, on its own, that the terminal supports later charges. That capability must be enabled and supported by the integration.
The merchant initiates renewals
MIT means a merchant-initiated transaction. It is the flow used for later charges within the authorised relationship, without requiring the customer to repeat the whole purchase every period.
The Redsys tokenisation documentation and its MIT guide explain these distinctions. An MIT may fail to confirm and require attention. Automatic collection does not mean guaranteed collection.
What to confirm with your bank before integrating
Explain that you need subscriptions with an initial buyer operation followed by renewals. Describe the business, service and intended frequency. Simply asking for an online payment terminal may leave the necessary operations undefined.
Confirm the merchant and terminal details, tokenisation or reference payments, and recurring capabilities. For our card flow, we also review inSite and the test and production environments. The production preparation guide provides the technical requirements.
Capabilities depend on the configuration enabled for that terminal. AndorPay uses what is available; integration does not replace banking activation. If the current terminal has a limitation, we identify it before preparing launch.
Check where operations and settlements can be viewed as well. A confirmed renewal needs a reference that can be followed through administrative review. The point when the bank settles funds has its own terms.
Give the banking and integration contacts the same description of the service. If one party understands a one-off purchase while the other prepares monthly renewals, a working first payment can hide an incomplete setup. A consistent example helps expose that mismatch early.
Define the subscription before its charges
Write down what the customer buys each period, when it starts and when it renews. A monthly offer should explain whether its period follows sign-up or an agreed calendar. The configuration needs to make the advertised terms match what is executed.
Define what happens when a customer changes plans or requests cancellation too. You do not need to design every future offer. You do need a clear rule for the subscription you intend to sell now.
If there is an initial trial, a discount or a special start date, check how it is represented in the product and configuration. Do not resolve a difference by informally changing a charge amount without preserving its relationship with the subscription.
Our digital subscription services guide covers the offer and delivery. Here, those decisions provide the basis for the schedule the system must maintain.
How initial sign-up works
The journey starts by identifying the buyer and recurring product. The integration creates the appropriate session and presents payment. The customer recognises the offer and completes the required steps, including authentication where necessary.
When the result arrives, the journey's resources are linked. In our documentation, a recurring product can generate a subscription, payment and invoice during reconciliation. Each describes a different part of the sale.
Your application needs to retain its customer reference and the subscription relationship. It can then activate the service for the correct person and recover the operation if the browser closes before returning.
Before treating sign-up as complete, check the financial outcome, service period and intended fulfilment. If the offer includes a delayed start or trial, apply that specific rule. Creating a subscription does not always mean money has been collected.
Keep the initial offer identifiable after purchase. A support request may arrive weeks later, when the public sales page has changed. Your team needs to know which service and period belong to this subscription, rather than assuming every customer accepted the current offer.
What happens during renewal
When renewal becomes due, the responsible component identifies the subscription and the period to collect. In AndorPay's documented flow, subsequent charges are initiated as MIT operations on a terminal with tokenisation and recurring capabilities enabled.
Each operation has its own result. A successful first purchase does not make every following month a confirmed payment. The payment method may need updating, the charge may be declined or its result may remain pending.
Once payment is confirmed, subscription management and your application update what belongs to that period. The customer does not need to visit checkout for the business to learn the result of a subsequent charge.
Retain the link between subscription, period and operation. If someone asks about two transactions or their next renewal, you can inspect specific records. You will not have to infer the service period solely from the date a message arrived.
Payment schedule and service period are different records
The scheduled payment date, the time of the attempt and the service period being sold need to be distinguishable. A technical delay should not accidentally change the offer the customer purchased.
Imagine a renewal for the next month of service whose result arrives late. Your team needs to know which period it is resolving before extending access or requesting another payment. The notification date alone does not explain that relationship.
Keep one owner for the schedule and record changes with their effective date. When a plan changes, review actions already scheduled. Avoid a dashboard showing one date while another tool retains a different renewal instruction.
Use information consistent with the actual configuration when communicating renewal dates. If the business operates around a particular day and time zone, the technical team should check that displayed and processed dates follow that convention.
Confirming payment and updating the service
In AndorPay, payment.succeeded communicates a confirmed payment. Subscription events describe status or period changes. Invoice events concern the associated document. Our payment lifecycle documentation explains how to distinguish them.
Your application verifies the notification and applies the appropriate action. Visual browser confirmation supports the buyer's experience but does not replace that check. Renewals may also complete without any customer visit.
The same event may arrive more than once. The integration must recognise it to avoid another delivery, an additional access extension or a second record of the same outcome. Reprocessing an existing confirmation is different from requesting a new charge.
It must also be possible to recover the state if the application was temporarily unavailable. Payment information remains linked to the operation. Recovery means applying the correct outcome to the corresponding purchase.
A complete example: monthly access to a service
Imagine a professional resource library with a monthly plan. Someone creates an account, accepts the offer and completes sign-up. The system links their user account, subscription, initial period and payment result. The application grants access according to those terms.
At renewal, AndorPay requests payment within the configured flow. If it is confirmed, the new period is identified and the application maintains access. If the notification arrives again, that period remains unchanged instead of being extended twice.
Now suppose payment is confirmed but the application does not update access. The incident is resolved by examining receipt and application of the result for that same payment. Charging again would not fix the missing access.
If the operation is declined instead, the team reviews the available reason and required action. The commercial policy determines what the customer can continue using while the issue is resolved. If they request cancellation, it is recorded with its intended effect and any pending actions are reviewed.
This example illustrates the aim of the whole setup: money, period and service should tell the same story. The payment system provides the financial result, and the application connects it to what the customer bought.
Failure, waiting and non-execution are different problems
A confirmed decline means that attempt finished without collection. A pending outcome requires checking the existing operation. A renewal that never started calls for a review of scheduling and execution. Grouping all three under “card not working” hides the difference.
| Situation | What to inspect first | Action that avoids confusion |
|---|---|---|
| Pending payment | Existing operation's status | Follow its resolution before requesting another charge |
| Confirmed decline | Available result and required action | Apply the appropriate recovery process |
| Renewal not started | Schedule, account and execution | Correct the cause preventing the attempt |
| Confirmed payment without access | Period and application update | Repair fulfilment against the same payment |
| Cancellation with renewal scheduled | Effective date and outstanding actions | Align the schedule with the recorded decision |
The customer message should reflect what you know. Do not attribute a decline to insufficient funds if the response does not confirm that. Do not announce cancellation while still investigating a pending outcome.
Our failed renewals guide covers recovery in more detail. The principle is to identify the case before acting and give the buyer an understandable next step.
Retries and payment method updates
Repeating an attempt needs a rule and an owner. Do not schedule several independent mechanisms against the same renewal. Do not adopt a generic retry timetable without checking that it matches the product and integration in use.
Some incidents require the buyer to act. Our API documents a hosted action for updating a subscription's payment method, subject to the necessary capabilities. The update has its own outcome and must be associated with the correct customer.
Completing that change does not mean every earlier outstanding payment has automatically been resolved. Check what happened to the affected renewal and which action is scheduled next. Once payment is confirmed, close reminders that are no longer relevant.
Your team needs to know where automated handling ends and who receives unresolved cases. Recovery is easier to manage when the state shows what has been attempted and what still needs doing.
For example, a record saying “payment method updated, previous renewal still awaiting resolution” is more useful than a general “customer updated” note. It separates the completed action from the remaining financial question and helps prevent two people taking conflicting steps.
Cancellations and plan changes without losing the period
Cancellation affects the subscription's continuation. Establish when it takes effect, which access remains and which operations were already in progress. The customer's decision needs to be linked to the right subscription with a response they can understand.
A plan change also needs an effective date and a verifiable result. Our API documents change operations and cancellation of scheduled changes. Their behaviour must follow the endpoint contract and the offer's configuration.
An accepted request does not prove that the update is complete. Review the status and related change before presenting new terms as active. The API reference lists the available operations.
Cancellation is not automatically a refund. Where a refund is required, it is a separate operation. Redsys refunds are not enabled through our current API; the applicable process must be agreed before offering an automated customer action.
Invoices, payments and bank settlement
Link each document to the relevant customer, order or subscription. A created document and a confirmed payment represent different facts. If collection fails, that distinction helps explain what remains outstanding.
Settlement into the bank account is checked under the terms agreed with the institution. Do not use access status as a substitute for financial tracking, or a transaction list as the only record of service delivery.
Document handling needs to fit your administrative process. If you use another invoicing or accounting tool, define what data it needs and who maintains the correspondence. Having an invoice API does not complete every tax configuration or external connection by itself.
When a customer asks for a document, your team should be able to locate the relevant period without recreating the sale. That is another reason to retain shared references across the subscription, payment and document rather than relying on names or dates alone.
Changing connections with existing subscriptions
A migration affects new sign-ups and existing relationships differently. You can prepare a new journey for a new customer. For an active subscription, you need to inspect the period, schedule and available payment reference.
Do not assume tokens transfer freely between providers, merchants or terminals. Portability depends on the reference's conditions and supported operations. Buyer action may be necessary and should be planned without making it look like a duplicate purchase.
Prepare an inventory of active subscriptions, upcoming renewals and outstanding payments. Decide which system owns each relationship during the change. Avoid keeping two active schedules for the same period.
Retain the history needed to answer questions about earlier operations. Changing a connection does not remove the need to locate an old payment or explain a cancellation. The transition is complete when every relationship has an owner and customers understand any action they need to take.
A practical review can separate subscriptions into active relationships without issues, unresolved payments and scheduled changes or cancellations. Those groups may need different treatment. The person coordinating migration should be able to explain what will happen to each before opening new sign-ups.
What needs to be ready for launch?
| Area | Useful check before starting |
|---|---|
| Business and terminal | Activity, terminal and recurring operations confirmed |
| Offer | Understandable period, start, renewal and cancellation |
| Sign-up | Customer, subscription and outcome linked |
| Renewal | One schedule owner and an identifiable operation |
| Access | Defined application and recovery rules |
| Communication | Messages for confirmation, waiting and required action |
| Operations | Owner for incidents and documents |
| Production | Real configuration reviewed and validation agreed |
The test environment lets you verify sign-up, renewal and relevant states without treating them as real sales. Production validation is a separate check. Our payment integration testing guide explains how to record scenarios and outcomes.
For the technical owner, the useful references are the payment lifecycle, API, webhooks and production preparation. For the business, a description of the offer, platform and current service management is enough. You do not need to translate your operation into banking parameters before speaking with us.
Keep the launch scope explicit. If the first release supports one monthly offer, the completed checks should describe that offer. Adding another frequency, a trial or a new platform later may require reviewing the affected journey even though the original cycle works.
What to monitor once the cycle is running
Check how many renewals were due, which were initiated and which have confirmed results. Review cases requiring intervention separately from payments whose access has not been updated. This helps identify the step needing attention.
Preserve the service period context when reviewing those figures. Comparing attempts with subscriptions without distinguishing retries can produce a misleading picture. One renewal may generate multiple events without representing several new customers.
Review support questions too. If customers do not understand their renewal date or how to update a payment method, the journey may need clearer communication. Improving that message is part of managing recurring collection properly.
Use operational observations to choose the next improvement. A scheduling issue, an unclear message and a missed access update need different fixes. The value of tracking the cycle is knowing which task to improve, rather than treating every unsuccessful outcome as a banking problem.
Before opening sales, use the recurring payment test matrix: sign-up, MIT renewal, decline or pending result, duplicate notification and effective cancellation. Keep each result with its subscription and period; a successful first charge does not replace these checks.
Frequently asked questions
Can any Redsys terminal collect subscription payments?
It needs the operations required for the chosen journey to be enabled. We review the terminal, tokenisation, recurrence and configuration with the bank. A successful one-off payment does not prove those capabilities on its own.
Do I need to store card numbers in my application?
Our flow uses the prepared connection and payment references. Your application retains the necessary commercial relationships; it should not copy complete card details to manage renewals.
Does the first purchase validate every renewal?
No. A subsequent cycle, its results and its effect on the period need to be checked. Renewal uses a different operation at a different time from the initial sign-up.
Can I keep my current bank?
We review the available configuration first. Our guide to adding subscriptions to your existing terminal helps prepare that starting point without assuming the entire infrastructure must change.
Prepare your recurring payment cycle with AndorPay
Tell us which service you sell, the platform you use and how you want to organise the periods. We will review the terminal, sign-up, renewals and access connection to prepare a proposal with a clear scope.
Explore our online payment solution for Andorran businesses or request a proposal for your subscriptions. We start with how your business operates and connect each payment to the service it needs to maintain.
