If your company is based in Andorra and you want to sell subscriptions, a Stripe dependency can become a problem when you connect your business software. With AndorPay, we can prepare a recurring payment journey using your banking payment service and its enabled capabilities: customer sign-up, initial payment, renewals and subscription tracking.
Start with a practical question: what should happen in your business whenever someone subscribes or renews? A digital service may need to grant access; a membership may need to extend a period; an in-person activity may need to keep a place reserved. This guide explains how to organise that journey and what to review before setting it up.
From a Stripe dependency to a workable payment journey
Stripe's official availability list, checked on 5 October 2026, does not include direct onboarding for Andorran companies. If your software depends on that connection, you need to review how it can be replaced within the sales journey.
A page that accepts cards does not cover the whole life of a subscription. There is an ongoing relationship between a customer, a plan, a service period and its associated payments. The integration needs to keep those elements connected from sign-up through later renewals.
At AndorPay, we work on that operational process. The bank and Redsys retain their processing and settlement responsibilities. AndorPay organises the payment cycle and communicates the changes your application needs. Our page on taking payments from Andorra introduces this approach.
What to decide before creating a subscription
What the customer receives, and for how long
Describe the service precisely. “Access to the platform for a month” defines a period. “Sessions used over time” introduces a usage balance as well. Both offers might be sold regularly, but delivering them involves different rules.
Define when access begins and how its end date is represented. Decide what happens when someone joins partway through a month. The business policy needs to be clear before choosing the dates and events used by the integration.
It also helps to distinguish the subscription from individual bookings or deliveries. A membership might remain active while an appointment changes. Your system should know which change affects billing and which belongs to the service schedule, so that an ordinary booking adjustment does not accidentally change a renewal.
When the first payment happens
Sign-up may begin with a payment or, where the product and configuration support it, a trial period. In either case, the customer should understand when the relationship starts, when the next charge is due and how to manage continuation of the service.
The sales page and configuration need to agree. If an introductory period is offered, the dates shown after registration should match that offer. Checking this consistency is part of testing the integration before launch.
Which decisions belong to your business
The system needs rules for common situations. If payment fails, will access continue temporarily while the issue is resolved? If someone cancels, will the service end immediately or at the end of the current period?
Those choices describe the service you sell. We then review how to implement them using the available capabilities. This prevents a software default from silently becoming a commercial condition your business never chose.
The full subscription journey with AndorPay
1. The customer chooses a plan
Your sales page should explain the service, its billing interval and when it starts. Checkout receives the relevant product or plan. Its identity should remain consistent from the offer through to the subscription record, so the customer and your team can recognise the same purchase.
If you have several plans, document what changes between them: access, limits or included services. Preparing that structure does not require publishing AndorPay's commercial terms. Your catalogue should represent what your own business will deliver.
2. Sign-up and the first payment are completed
The buyer opens checkout and completes the required actions. Bank authentication may be part of this step. Confirmation then needs to reach the server and be linked to the correct customer and product.
The return page guides the buyer, but your system still needs the result if the browser closes. Our payment lifecycle documentation explains how AndorPay separates the screen the customer sees from confirmation of the payment.
3. Your system activates the service
Your application should interpret events according to their meaning. A confirmed payment records the financial result; a subscription status describes its situation and period. Activating the service should use the information required by the rule you have defined.
For example, an ongoing course needs to connect a learner's account to the subscription. A business application needs to apply the capabilities of the purchased plan. These are examples of integration work to prepare, rather than customer stories or external connections that can be assumed to work already.
4. Renewals follow
Later charges use the enabled recurring payment capabilities. Redsys documents tokenisation and merchant-initiated transactions, allowing a payment reference to be used for authorised later operations with the appropriate configuration.
Our product documentation describes AndorPay initiating subsequent payments as MIT when the payment service supports tokenisation and recurring transactions. The integration must reflect each operation's result and relate the new period to the correct subscription.
What to do when a renewal does not complete
First identify the actual payment status. A pending result, a required customer action and a confirmed decline are different situations. Your team should be able to distinguish them without treating every unresolved response as a final failure.
| Situation | Operational response to prepare |
|---|---|
| Result still pending | Check the status before starting another attempt |
| Payment declined | Identify the issue and follow the defined recovery process |
| Customer action needed | Explain the action and provide the appropriate journey |
| Payment confirmed | Update records and service access according to the agreed rules |
A useful customer message identifies the affected subscription, explains what to do and provides a contact. Avoid contradictory notices from different tools. Once payment is confirmed, later communications should reflect that change.
An apparently outdated screen should not trigger another charge blindly. Before a new attempt, the system needs to know the outcome of the previous one. Our guide to failed subscription renewals develops the operational follow-up.
Give your team a consistent way to record the next action. One subscription might be waiting for a customer update, while another is awaiting a confirmed processor result. Keeping that distinction visible helps staff communicate accurately and prevents an unresolved case from being handled twice by different people.
Cancellation, plan changes and service access
Cancellation and refunds are different operations. Cancelling a subscription controls its continuation; it does not establish that an earlier payment has been returned. Your team and customer messages should keep this distinction clear.
AndorPay's documentation includes cancellation and plan-change management. Available actions depend on the subscription's capabilities. For your integration, we need to establish which event the application receives and when customer access changes.
A calendar example without prices
Imagine a monthly service with a period starting on the 10th. The customer asks to cancel on the 24th, and the business allows access until the current period ends. The request needs to be recorded, the next renewal needs to reflect scheduled cancellation and access needs to follow the promised end date.
This example checks consistency between policy, configuration and communication. If the customer receives cancellation confirmation while the application still announces another renewal, a connection remains unresolved. Test the whole journey before launch.
If you already use membership or business software
Tell us which software you use and its role in payment management. Some tools control access; others also hold the catalogue and renewal schedule. We need to identify the system responsible for each piece of information to avoid conflicting versions of the same subscription.
Review where customers are created, what determines the active plan, which system schedules renewal and how confirmation is received. API and webhook documentation helps define possible connections. That overview is also useful to the developer maintaining your application.
If the tool only accepts its original integration, that limitation needs examination before promising a direct replacement. Preparing AndorPay to take payments does not automatically modify an external application. The agreed work should cover the required connections and identify dependencies.
If that tool is Billsby, our guide to preparing a Billsby alternative in Andorra explains what to review in the catalogue, billing cycles and continuity of existing subscriptions.
Moving existing subscriptions
Prepare an inventory of customers, plans, current periods and upcoming renewals. The transition should avoid both systems charging for the same period or customers losing access while records are updated.
The portability of saved payment methods requires a specific review. If new customer authorisation is necessary, the communication and relevant link are part of the transition. Also define when new sign-ups will stop using the previous journey.
Assign responsibility for monitoring the change. Whoever answers customer questions should be able to identify the system holding each subscription and the next expected action. This avoids asking customers to do unnecessary work while records from different stages are being reconciled.
How to check that you are ready to sell
Testing should cover more than the first accepted payment. Prepare a journey for each behaviour you offer: sign-up, activation, renewal, payment problems and cancellation. Use the relevant test environment and specify what your application should do in each case.
Check that receiving an event twice does not activate a service twice or create duplicate records. Review delayed notifications too. Our webhook guide explains notification verification and handling redelivery.
Your team should know where to investigate an issue and which references connect the customer, subscription and payment. They should be able to reconstruct what happened without asking the buyer to pay again to see whether it works.
Keep the test results with the agreed scope. They provide a reference when settings change or you add a new plan. The people running the service can then identify which behaviours need to continue working and where to check an unexpected result.
Frequently asked questions
Does an existing payment service mean I can charge automatically?
Its enabled recurring capabilities need to be reviewed, and subscription management needs to be prepared. The first payment, later renewals and service statuses are all part of setup. We help review your starting point and the connections required.
Can I keep my current software?
We assess its integration options and the actions that need connecting. Share its name and explain how it handles sign-ups, renewals and cancellations. That information helps define the work without assuming compatibility that has not been checked.
Does subscription management also cover all taxes?
Payment collection, documents and tax handling have different responsibilities. Tell us your customer markets and the tools you use so we can define what information needs to move between systems. Tax management or an agreement with a third party should not be assumed included unless it appears in the proposal.
How can I get a proposal for my business?
Describe your service, platform, billing interval and whether you already have a banking payment service or active subscribers. We review the journey and provide the terms privately, including the integration scope and its dependencies.
Prepare subscriptions for your business in Andorra
If your software asks for Stripe and that is holding up your launch, start by describing the service you want to sell and the steps you need to automate. With AndorPay, we review how sign-up, payment and renewals connect to your business.
