A payment gateway connects a purchase to payment processing. Subscription management organises the relationship that continues afterwards: the customer's plan, renewal dates and what happens when they change or leave the service. Invoicing records and documents the sale. These functions may sit within one platform or be shared across several tools.
For your Andorran business, the useful decision is which tasks you need to cover and how to connect them. A store selling individual products and a service offering monthly access have different operational needs. This guide helps you distinguish each function and choose a setup your team can manage day to day.
What the gateway handles during a purchase
When a customer pays, the payment connection submits the operation to the relevant system and makes its outcome available. The journey may include additional buyer authentication and a later confirmation. That outcome must remain associated with an identifiable purchase.
The immediate business questions are straightforward: which order was paid, what amount was authorised and what is the payment status? If you sell physical products, this information allows you to continue towards packing and shipping the order.
Settlement into your bank account follows its own schedule and conditions. A confirmed authorisation and the settlement date are different things. Preserve the relationship between sale, payment and bank movement so that any discrepancy can be investigated.
A gateway can also offer recurring capabilities. For example, Redsys documents tokenisation and recurring operations. The label “gateway” alone does not tell you how much business management a particular proposal includes.
What subscription lifecycle management adds
A subscription connects a customer to a service over successive periods. Alongside collecting payment, you need to retain the selected plan, the current service period and decisions that affect the relationship's continuation.
Before launching, you should be able to explain when access starts, when the next renewal falls due, how cancellation works and what happens if payment is not confirmed. These are rules of your offer that the integration needs to represent.
Subscription management coordinates those rules with payment events. Some tools cover several functions together. For example, MONEI's subscription documentation shows that a payment provider can also include this capability. Compare the actual scope of each connection rather than deciding solely by its commercial category.
Service access: who opens and closes the door?
Collecting payment and allowing someone to use a service are related actions. However, the payment system does not automatically know the customer's user account, purchased lessons or permissions within your application.
Your business needs a clear relationship between customer, subscription and access. A custom application receives relevant changes and applies the agreed rule. If you use a content or membership platform, check which connection maintains that relationship.
For example, a confirmed renewal may extend the access period. Receiving the same confirmation twice should not extend it twice. Cancellation may stop future renewals while preserving paid access until the agreed date. The precise behaviour must match your offer and the available integration.
This distinction matters when answering a customer who says, “I paid but cannot get in.” You need to locate both the payment and the entitlement. Finding a successful transaction does not, by itself, explain whether the application applied it to the right account.
Invoicing and documents are another responsibility
A payment confirms a collection operation. An invoice documents the sale with the relevant details. You need to link them without treating them as one record or assuming that a payment receipt replaces every document your business uses.
Identify where buyer details are maintained, which system generates the documents and how they reach your administrative team's software. If you already use an invoicing application, check the information it needs and who will handle corrections.
AndorPay has invoice resources associated with the documented payment flow. Their existence does not mean every tax configuration or accounting connection is automatically complete. Define the documents and data exchange your activity needs, particularly if it involves several markets or customer types.
Map responsibilities before comparing tools
Assign a person or system to each task before evaluating software. An empty row shows a part of the sale that still needs a solution.
| Task | Required outcome | Question for your project |
|---|---|---|
| Record the sale | Identified product, customer and terms | Where is the purchase created? |
| Process payment | Outcome linked to the operation | Which connection confirms collection? |
| Manage the period | Subscription dates and status | Who schedules and records renewal? |
| Deliver the service | Access or fulfilment matching the purchase | Which system applies the outcome? |
| Document the sale | Document linked to customer and operation | Where is it generated and retained? |
| Resolve incidents | Enough information to explain and fix them | Who can trace the whole journey? |
This map does not require six tools. It may be covered by a platform and a small integration, or by systems you already use. What matters is that every task has an owner and that references let your team move between the different records.
Example: first payment, renewal and monthly access
Imagine a training service with a library that is updated every month. The offer includes access while the subscription remains in force. Each buyer has an account in the service's application.
When the customer subscribes
The application identifies the user and the selected offer. The payment system processes the first payment and communicates the outcome. Subscription management records the period and its relationship with the customer. The application activates access according to that confirmation.
Your team should be able to answer “what did this person buy, and how long can they access it?” without searching through scattered conversations. The sales document is linked to the same operation.
When renewal is due
The component responsible for the billing cycle identifies the scheduled renewal and requests payment according to the enabled configuration. When payment is confirmed, the period is updated and the application maintains the corresponding access.
There are two different pieces of information here: the outcome of that payment and the subscription's current service period. Looking only at the last checkout screen cannot manage a monthly relationship. The records must remain available even when the customer does not visit your website on renewal day.
If renewal is not confirmed
A failed payment and a pending payment need different handling. The person helping the customer needs to identify the affected operation and the action that can move it forward. The application applies the access policy defined for that state.
Creating another subscription is not necessary to investigate the incident. Start with the existing subscription, the affected period and the operation's outcome. If the buyer needs to update their payment method, that step also needs to remain linked to their account.
Three sales models with different operational needs
| Model | What needs coordinating | What to avoid |
|---|---|---|
| Product purchased once | Order, payment, shipment and document | Adding subscription management without a real need |
| Purchase paid in agreed instalments | Original sale, schedule and outstanding payments | Treating it as a service that renews indefinitely |
| Monthly service access | Sign-up, periods, renewals, incidents and cancellation | Limiting the solution to the first payment form |
An instalment purchase is one sale with a planned end to its payments. In a subscription, the relationship continues according to the agreed terms. Both may involve several collections, but their rules are not necessarily interchangeable.
If you are still defining the model, our guide to subscription-based digital services helps clarify what the customer receives each period. Your tools should follow that offer.
Where AndorPay fits
At AndorPay, we connect payment collection with the operation of your Andorran business. Our documentation distinguishes payments, orders, subscriptions and invoices. Each resource represents part of the journey, while events keep the connected application informed of relevant changes.
For recurring products, the documented flow can create a subscription and relate it to the payment and corresponding document. Later collections require the necessary tokenisation and recurring capabilities on the online payment terminal. We review that configuration during setup.
Our payment lifecycle documentation explains these responsibilities. Connecting your platform remains necessary so that the outcome activates the exact service you sold. We also establish which operations your account needs and how exceptions will be handled.
Compare proposals through your actual customer journey
Ask for a complete example from your business. Start with an ordinary sale and continue through the next renewal or delivery. Then introduce an incident: a pending payment, a cancellation or a payment method update.
At each step, identify what is included, what needs configuration and what requires development. “Supports subscriptions” does not explain how access will update in your application. “Has an API” does not prove that a ready-made connection exists for your particular platform.
Check who retains customer, order and period data. A shared reference prevents your team from guessing which payment belongs to an account. If two tools can change the same schedule, define which one owns that decision.
Review work after launch as well: who handles a pending operation, how a plan is changed and where history can be found. For example, Redsys refunds are not enabled through our current API, so the applicable process needs to be agreed. A useful proposal explains both the standard journey and its limits.
Ask what happens when the person responsible is unavailable. The answer may be a clear record that another team member can read, rather than another automation. The system should make the work understandable as well as reduce repetitive steps.
When does additional management become useful?
The clearest signal is a repeated task that keeps service delivery connected to payment: checking renewals, copying statuses, granting access or finding transactions to answer customers. Describe that task and the missing information before looking for another tool.
A store that already links orders, payments and shipping correctly may have its normal journey covered. A monthly service relying on someone to remember each renewal and manually change permissions is a good reason to review the full cycle.
Who will maintain the connection matters too. Useful automation leaves an understandable state when something fails and lets the team pick up the work. Fewer manual steps are valuable when you can still understand what is happening with each customer.
Frequently asked questions
Does a gateway replace accounting software?
Do not assume it does. Check the documents it generates, the data it retains and the connections available. Your administrative process needs to relate sales, payments and the documents used by the business.
Does every store need a subscription platform?
No. It depends on the offer and the tasks required after payment. A one-off sale may be fully served by a connection that correctly links the order, payment and fulfilment.
Can I keep my existing payment terminal and add management?
We review terminal compatibility, enabled operations and your platform. The guide to adding subscriptions to an existing payment terminal explains that preparation.
Connect the tasks that are still separate today
Tell us where you record the sale, how you collect payment and what you do afterwards to deliver or maintain the service. That information lets us prepare a proposal with a defined connection and scope.
Request a review of your payment journey. At AndorPay, we start with how your business operates so that payment becomes part of a sale you can manage from beginning to end.
