Redsys is a payment processing platform that may form part of your business’s online card payment setup. Its name comes up when you prepare to accept payments because it helps process transactions and communicate their results. If you sell from Andorra, it is useful to understand how it connects with your bank, website and order management.
At AndorPay, we organise that connection around the way you sell. This guide explains each party’s role and the questions to settle before opening your checkout to customers.
Bank, virtual terminal, Redsys and AndorPay: who does what?
Your bank is the institution with which you review the contract and configuration for the relevant payment service. A virtual payment terminal, often called a TPV in local documentation, enables a merchant to process online payments. Redsys provides processing infrastructure for connections that use it.
AndorPay connects payment with your business workflow: products, customers, orders and subscriptions where relevant. Your shop or application retains its own responsibilities, including presenting the offer, delivering goods or providing access to a service.
You do not need to memorise every technical term to get started. You do need to know who prepares the payment, who confirms its outcome and where a completed sale should appear. That distinction explains why arranging a payment service with a bank and having a shop ready to trade are separate steps.
| Party | Practical question |
|---|---|
| Bank and contract | Which service is enabled for my business? |
| Payment processing | What is the outcome of the transaction? |
| AndorPay connection | How is the payment linked to my sale? |
| Shop or application | What should the customer receive or gain access to? |
What the buyer sees and what your business needs
The buyer sees an offer, chooses what they want and reaches a payment page. They need to recognise the purchase, see the amount and understand the action being requested. They then expect confirmation and the agreed product or service.
Your business needs additional information: which order the payment belongs to, whether it is confirmed and what the team should do next. In a shop, that may mean packing a delivery. For a service, it could mean activating access or confirming a booking.
These two views should agree. A thank-you screen is not enough if the shop cannot identify the order to fulfil. The reverse can happen too: a payment may be confirmed while the buyer still sees a waiting screen. The integration should let you resolve those differences by finding the same transaction.
The stages of an online purchase
The shop prepares the transaction
The starting point is the purchase: products, customer and required details. The integration links that purchase to a payment reference. Keeping this relationship allows you to find the transaction later, even if the customer contacts you through another channel.
For WooCommerce, our plugin uses the order information and your shop’s catalogue. The requirements are explained in the AndorPay installation guide. You do not need to duplicate that catalogue to prepare the connection.
The buyer completes payment
The payment page presents the available methods and guides the authorisation process. The journey depends on what is enabled for the merchant and which method the buyer chooses. If an additional step is needed in the banking environment, the buyer should be able to follow it while retaining the context of their purchase.
This step can be presented in different ways. The Redsys documentation describes several integration models. The technical choice should suit your platform and the experience you will be able to maintain.
Your business receives confirmation
The integration receives the result and links it to the order. Your application uses that confirmation to decide what happens next. The return page helps inform the buyer, but it should not be the only evidence that a payment has succeeded.
Our payment lifecycle guide explains this distinction. It matters when someone closes the window, loses their connection or returns to the shop before the screen has updated.
Why an in-store card reader does not prepare your website
Paying at the counter and paying on a website follow different workflows. Accepting a card in your premises does not establish that an ecommerce connection is active or that an online order will receive the payment result.
If you already work with a bank, explain that you want to accept payments online and name your platform. Also explain whether you plan to sell one-off purchases or subscriptions. This information helps identify the configuration to review and avoids preparing a service that does not cover the intended use.
Our guide to banks and online payment terminals in Andorra helps you prepare for that conversation. The starting point is to retain the useful parts of your current setup.
What about Apple Pay, Google Pay or Bizum?
Each payment method requires compatible configuration. Wallets and Bizum have their own requirements in our integration. Displaying their logos does not establish that they are ready to use. Nor does a provider mentioning the service somewhere on its website.
Availability can also depend on the buyer. Two people may see different choices because of their devices and the payment methods set up in their environment. The review should check the actual shop journey with the methods you intend to offer.
Our payment methods guide explains how they fit shops, payment links and services. Keep a clear alternative available for buyers who cannot use a particular method.
A subscription continues beyond the first payment
A one-off purchase ends with payment and fulfilment. A subscription maintains a relationship: service periods, renewals, changes and cancellations. Someone or some system must therefore own the schedule, and each payment outcome needs to connect with access to the service.
Recurring payments require the relevant capabilities and configuration. A card having paid for a purchase does not establish that subsequent renewals are ready. It also does not mean that a separate access system will update automatically without a connection being implemented.
Our guide to recurring payments with Redsys in Andorra covers that setup in more detail. Here, the key distinction is between authorising one transaction and running the full subscription lifecycle.
How to investigate a problem without starting again
If a customer is unsure whether they have paid, check the existing transaction first. Gather the order reference, time and status shown by the shop. A browser that is still waiting does not prove that the payment was declined.
If payment is confirmed but the order remains pending, focus the investigation on the shop update. If a decline is confirmed, prepare the appropriate next step. If the outcome is uncertain, resolve that uncertainty before asking the buyer to make another payment.
It also helps to distinguish a repeated notification from a second payment. The same message can arrive more than once without representing another sale. The integration should recognise this so that it does not duplicate a delivery or extend access twice.
What to prepare before starting with AndorPay
Share your bank, platform, what you sell and how customers reach the payment step. Tell us whether you already have an online payment service and whether any transactions or subscriptions are active. We can then review what should be retained and what needs connecting.
Define the expected result of a normal sale: an order ready to ship, a confirmed service or activated access. Include what should happen when payment does not complete. These decisions allow us to prepare a private proposal with a concrete scope.
Before opening to customers, we check the intended journey in the appropriate environment. Our testing guide explains how to verify payment and the resulting state in your application. Seeing a button or saving settings is a preparation step; the complete journey still needs to be checked.
Frequently asked questions
Do I need to learn how to integrate Redsys myself?
We can review the work required for your platform and team. A shop using a plugin and a custom application need different connections. Start by explaining the customer journey you want to provide and the systems you already use.
Does AndorPay replace my bank?
The bank and processor retain their roles. We connect payment with the intended business workflow and define the setup around your situation. Knowing these responsibilities makes it easier to prepare the launch and route questions afterwards.
How can we review my project?
Tell us how you want to accept payments from Andorra. Share your website and the point where you need help so that we can define the connection, checks and launch steps.
