Andorpay
Back to the blog

Published on · Updated on

Subscriptions with your existing Andorra gateway

Connect subscriptions to your existing payment setup. Plan bank requirements, first payments, renewals and access with AndorPay.

Bank, recurring calendar and store connected to illustrate subscription payments.

You can add subscriptions to an existing payment gateway when your bank, payment setup and application support the full recurring payment journey. Start with what you already have: your banking relationship, your online merchant facility and the store or service your customers use. Then connect the first payment, subsequent renewals and customer access so that every billing period has a clear outcome.

At AndorPay, we approach the setup as a complete process. Charging a card is one step. Knowing which customer the payment belongs to, which period it covers and what happens if it fails is what makes a subscription manageable. This guide explains how to prepare that connection while making use of your existing business setup.

Establish what your existing payment setup includes

In Andorra, the term TPV may refer to a card machine in a shop, an online payment facility provided by a bank, or software used to manage sales. Online subscriptions require an ecommerce payment setup. Owning a card reader that takes payments at a counter does not establish that your online terminal is configured for recurring charges.

Gather the name of your bank, the platform you sell through and the available documentation for your online terminal. Identify who maintains the current integration: your own team, an agency or your software supplier. This gives us a useful starting point before discussing any additional tools.

If you already take one-off payments online, describe a normal purchase. Where does the customer select the product, enter their card details and see the order confirmation? Keep configuration references and test records available, but do not send passwords or secret keys through a sales form. The initial review needs a picture of the setup; access arrangements come later through an appropriate channel.

What you may be able to keep

Your existing setup may already provide the banking relationship, product catalogue, customer accounts and service delivery. Subscriptions add responsibilities: retaining an appropriate payment reference, determining the next billing period and coordinating changes in payment and subscription status.

For example, a training platform selling individual courses may keep its content and user accounts when introducing monthly access. It then needs rules for when each month begins, how access is extended and when it ends. Those are product and integration decisions even if the bank's online terminal continues to process the payments.

Confirm the required payment functionality with your bank

Taking subsequent payments without asking the customer to enter all their details each time requires a payment arrangement that supports this use. Availability depends on the terminal and its configuration. The Redsys developer documentation describes its integrations and services; your bank confirms what is enabled for your merchant account.

Explain the intended journey in practical terms: “We want to charge for a monthly service by card, with an initial customer payment followed by recurring renewals.” That is more useful than asking whether the terminal “supports subscriptions”, which might mean either processing repeat payments or managing an entire commercial subscription.

Prepare these questions for the review:

  • Does our contracted terminal support the operations required for subsequent charges?
  • What activation and documentation are needed to use payment references?
  • How do we test the setup before using the production configuration?
  • What happens when an operation requires further action from the customer?
  • Where can we check the outcome of an operation and reconcile it?

You do not need to become an expert in banking parameters. These answers provide the practical information needed to assess the connection. Our guide to recurring payments with Redsys covers authorisation and payment references in more detail.

Give each part of the journey a clear owner

Your offer defines what customers receive. The banking payment setup processes the transaction. AndorPay connects payment management with the events your application needs. The system delivering the service applies the relevant access rules. Clear responsibilities make the journey easier to implement and easier to explain when a customer needs help.

Part of the journey Information or decision required What to verify
Offer Service, frequency and renewal terms Customers understand the subscription
First payment Associated customer, plan and transaction The outcome belongs to the right purchase
Renewal Billing period and scheduled date A period does not produce conflicting charges
Access Start date, duration and exception policy Service availability follows the agreed rules
Cancellation Effective date and current period end Later actions respect the cancellation

Avoid using a single “active” label to describe everything. A customer account may still exist after paid access ends. A subscription may have been created while its first payment is awaiting confirmation. Preserving these distinctions gives your support team the information needed to explain the situation and identify the next action.

To organise these connections and decide which tasks to automate first, read the guide to automating payment workflows in Andorra.

Decide which system owns the billing calendar

The calendar answers a simple question: when is the next payment due? Your schedule may follow each customer's signup date or a common billing date, depending on your offer and the available implementation. Document the rule, including what happens in months of different lengths. “Monthly” should mean the same thing on your sales page and in your application.

Also identify the system that initiates renewals. If a store extension schedules a charge while another tool schedules the same period, you may create duplicate attempts. The setup needs one owner for the billing calendar and a defined way for other components to receive the result.

Include plan changes in this discussion. When a customer changes plans partway through a period, determine when the new features become available and when the next payment changes. Applying a change at the next renewal can be a straightforward starting policy when it fits your service. More complicated rules should come from a real customer need.

Choose an integration based on the journey you need

A store using a compatible extension and a custom application require different implementation work. In both cases, verify the journey supported by your actual installation: signup, payment, renewal, failure and cancellation. A platform logo on an integrations page is not proof that every part of your subscription model is covered.

For a store, identify the component that manages subscriptions, the component that processes payments and the component that updates orders. Record the versions in use. An extension that accepts one-off payments does not automatically demonstrate compatibility with every recurring payment rule or membership extension.

For a custom application, your team needs to associate the purchase with the right customer and handle relevant events. Our payment lifecycle documentation distinguishes confirmed payment from subscription events. This lets an application update a service period without treating subscription creation as proof that money has been received.

A diagram of your application and the intended customer journey is enough to start the review. Technical details can then be scoped around that journey. Our page about taking online payments from Andorra explains how we approach the connection between your business and its payment setup.

Follow the first payment through to renewal

Consider a service offering monthly access to a professional resource library. The buyer selects the monthly option, creates an account and completes the first payment. The purchase maintains the relationship between the user, plan, payment and service period.

The first payment activates the correct period

The browser may display a confirmation screen, but the application uses the confirmed payment outcome to activate paid access. If the customer closes the window after paying, access should still update when the appropriate payment notification arrives.

Test the reverse case too. Returning to the website without completing payment must not automatically activate a paid period. A return URL helps the customer continue their journey; the financial outcome comes through the channel designed to confirm it. This distinction matters even when the normal checkout experience looks immediate.

Renewal extends access once

On the next due date, the responsible system identifies the outstanding period and requests the corresponding payment. Once confirmed, the application extends access. The transaction remains linked to the billing period so that your team can investigate a later question without guessing which renewal it belongs to.

If the same notification arrives again, it must not add another month of access. Processing the same message twice does not represent the sale of two periods. This is an important test because notification systems may deliver a message again after a temporary interruption or delayed acknowledgement.

A failed renewal starts a recovery journey

When a payment is declined, follow the agreed policy: explain the issue, provide the required next step and manage service continuity. If the result is still pending, check its status before treating it as a rejection. Asking the customer to pay again before resolving the first attempt can create another problem.

Our guide to failed subscription renewals covers recovery in detail. At the setup stage, the key is to include that journey from the beginning. Your first unsuccessful renewal should not be the moment you start deciding what to tell the customer.

Plan the transition if you already have subscribers

Launching new subscriptions and moving existing subscriptions are different projects. During a transition, establish which periods have already been paid, when each expires and which system has scheduled actions waiting to run. The handover date must prevent two tools from charging for the same cycle.

Do not assume that a saved card reference can be transferred between providers or terminals. That depends on the payment arrangement and the parties involved. If the new journey requires customers to update their payment method, prepare the instructions, timing and follow-up before starting the move.

Grouping subscribers by their next renewal date can make the transition easier to organise. You can then check each group and send instructions relevant to its timing. Keep a record of exceptions, including payments awaiting confirmation, cancellation requests and periods that still belong to the previous system.

It also helps to decide who resolves those exceptions. A commercial contact may explain the transition, while a technical owner checks payment status. Giving both people access to the same operation reference prevents a customer from receiving inconsistent answers during the handover.

Test the whole cycle before opening signups

A successful first payment is necessary, but it leaves much of the subscription journey untested. Prepare scenarios using test accounts and check the outcome in both the payment system and the application delivering the service.

  1. Completed signup: the correct customer receives the intended plan and period.
  2. Abandoned signup: returning to the site does not grant paid access.
  3. Repeated notification: one payment does not create another delivery or extend access twice.
  4. Successful renewal: exactly one period is updated and its reference is retained.
  5. Declined renewal: the agreed notice and service continuity policy apply.
  6. Pending result: the system continues checking without independently creating another charge.
  7. Cancellation request: the end date and subsequent actions match what the customer was told.
  8. Production configuration: test credentials and terminals remain separate from live ones.

Record the expected result and what actually happened. A visible error should be traceable to an operation and a time, rather than an isolated screenshot. This makes support conversations more productive: your team can establish whether the issue concerns payment, access or a delayed update between the two.

What to send us for a setup review

To begin, tell us your bank, platform, type of service and billing frequency. Explain whether you are starting from scratch or already have subscribers, who maintains the website and what should happen when someone pays, renews or cancels.

Include the exceptions you actually use, such as trials, plan changes or access for multiple users. We can review how those requirements fit the proposed scope. Commercial terms are prepared privately based on your installation and the work required.

If you are still defining the offer, read our guide to selling a digital service by subscription. If the offer is ready, ask us to review your existing payment setup for subscriptions. Explaining how you take payments today lets us identify what can be reused and what needs connecting.

Frequently asked questions

Do I need to change banks?

Start by reviewing your existing terminal and the functionality your bank can enable. That establishes whether the current configuration can be reused or needs adjustment. You do not need to decide on a new banking relationship before gathering this information.

Is installing a plugin enough?

The plugin must work with the payment setup and the software organising subscriptions. The full cycle also needs testing. Installing a component does not automatically settle access rules, plan changes or the transition of existing subscribers.

Can a renewal happen without the customer returning to the website?

That is the journey the enabled recurring payment arrangement needs to support. Preparing it includes the initial payment and the reference used later. Some failures require a new customer action, which is why recovery and customer communication belong in the setup too.

WhatsApp