Taking online payments from Andorra means connecting the shopper’s payment method to the way you sell and the work that follows a purchase. Cards and digital wallets are payment methods. A payment link, checkout page and API integration are ways to present or connect that payment. Understanding the distinction helps you build a journey that still works when it is time to ship an order or activate a service.
At AndorPay, we start with your sale: a store with a basket, a service agreed before payment or a subscription that renews. We then prepare the connection and confirmation your store or application needs. This guide helps you identify that journey before adding buttons or changing platforms.
Start with the way you sell
| How the sale begins | What to prepare |
|---|---|
| A customer selects products and confirms a basket | A checkout connected to the order, using payment methods enabled for your business. |
| You agree a service or quote before payment | A payment link tied to that sale and a confirmation you can match to it. |
| A customer signs up for a service that renews | Initial signup, authorisation for subsequent charges and service-period management. |
Start with the row that describes your business, then check your terminal and platform requirements. Payment methods do not necessarily work the same way in every journey. This helps define a practical proposal and avoids adding options that leave your team checking payments manually.
Payment method, checkout and business management
A card describes how the buyer pays. Apple Pay and Google Pay let them use a payment method saved in a compatible environment. The checkout is where they review the purchase and complete payment. A payment link takes them there from a message, email or proposal.
The integration communicates the result to the rest of your business. When a store marks an order paid or an application activates access, that connection is doing useful work. Subscription management adds the periods, renewals and changes that continue after the initial purchase.
These parts can work together. One shopper opens a link and pays by card; another arrives from their basket and chooses a wallet. Both need the sale to be identified correctly and your business to receive a confirmation it can use for fulfilment.
Choose around a specific purchase
Consider three sales. In a clothing store, the buyer selects a size and delivery option: checkout must retain both. For consultancy agreed by email, a payment link tied to the accepted quote may be enough. For classes with a monthly membership, you also need renewals and a way to cancel.
The deciding factor is what your team needs to do next: ship a parcel, start the work or keep a membership active. If you currently match every incoming payment to a sale by hand, ask how the new setup will do that before buying another tool. This gives you a practical selection criterion beyond the number of payment buttons available.
Cards: a foundation for many checkouts
A card payment lets you collect for a purchase through the relevant authorisation. In our WooCommerce integration, secure Redsys fields appear within the AndorPay payment journey. WordPress does not receive the sensitive card information identified in our plugin documentation.
For the buyer, the priority is understanding the purchase, the amount requested and any extra action required by their bank. Your team needs the result associated with the correct order. A form that accepts card details is not a complete solution if its confirmation never reaches the system used to fulfil the sale.
When the bank asks for extra authentication
Keep the purchase context clear while the shopper completes the bank’s request. An ambiguous message can make them think they need to start again. The authentication outcome must remain linked to the same payment attempt.
If the browser closes, check the recorded state before sending another request. Closing a page does not establish whether the payment succeeded. Our payment lifecycle guide explains how the browser’s return and the server’s confirmed result differ.
Apple Pay and Google Pay: using a saved payment method
Digital wallets let buyers select a saved method and authorise payment in their supported environment. They can make the mobile journey more convenient, especially when someone does not have their physical card to hand.
Availability depends on the merchant setup, virtual terminal, integration and shopper’s device. That is why the actual store configuration needs checking. The Google Pay web documentation describes its integration, but does not replace validation of your own checkout.
In our WooCommerce plugin, Apple Pay and Google Pay require X-PAY and the corresponding preparation. You also need to inspect the delivery information saved with the order. Our wallet guide for Andorran merchants covers activation and practical tests in more detail.
Bizum: taking payments in a banking app or your store
Bizum is worth considering if your customers use it. MoraBanc offers Bizum Pro Empresas in its app, while Creand describes support through TPV Virtual and TPV Link. Activating the banking app service does not automatically add Bizum to your online checkout.
For ecommerce, the payment must be linked to the order and its confirmation sent to the store. AndorPay uses the Redsys Bizum RTP connection, which requires activation on your terminal. Do not assume that accepting a one-off payment also enables subscription renewals through Bizum. Our guide to Bizum for businesses in Andorra explains what to check before activation.
A payment link works well when the sale already has context
A link is useful when the customer knows what they are buying: a service agreed by email, a booking or an engagement discussed beforehand. It lets them reach payment from the channel where the sale is already taking place.
The accompanying message should identify what the payment covers and explain what happens next. Assign an internal reference your team can find later. Working out which customer paid solely from an amount becomes unreliable when several sales have the same value.
With an AndorPay integration, creating a session provides a checkout address for the next step. Sharing that address through your chosen channel and linking it to the engagement are parts of the process to prepare. This documented connection should not be confused with assuming every email or messaging automation is already configured.
Example: a service accepted by email
The customer accepts the scope and receives a payment request associated with that engagement. Once payment is confirmed, the result retains the same reference. Your team can communicate the planned start date or the next step in delivery.
If the customer later asks whether the payment went through, you can find the operation using that reference. You do not need their card details, and you do not need a second charge to investigate the first. Preparing that link between service and payment makes support easier for both sides.
Hosted checkout and a checkout connected to your store
A hosted checkout presents payment on a page prepared by the payment platform. Your application creates a session, sends the buyer to that page and uses the confirmed outcome to continue the sale.
A store integration connects payment to the existing shopping journey. With WooCommerce, our plugin shares order information and presents the available methods. The choice depends on your ecommerce platform, the development work you can maintain and the experience you want customers to have.
An API connects systems; it is not a payment method shoppers select next to a card option. If you have your own application, the REST integration guide explains session creation. Our hosted checkout and API guide explores the responsibilities involved.
A subscription continues after the first payment
A recurring business needs to organise signup, the first charge and future renewals. Define when service begins, which period each payment covers and what happens if a renewal fails or the customer cancels. A card button on a website does not resolve those decisions.
In AndorPay, recurring journeys require the subscription capability and a connection prepared for recurrence. Our documentation describes subscription operations and events your application can use to update its state. The service’s access rules need to correspond to those confirmed outcomes.
For example, an outstanding renewal and a final cancellation may call for different responses. Decide what the customer sees, whether access continues and when your team intervenes. The guide to subscriptions with an existing virtual terminal develops this setup further.
Keep the commercial promise and the payment schedule aligned
A monthly service needs a clear explanation of the next renewal and how a customer can end it. If you change what the service includes, the account, subscription and customer message should describe the same arrangement. Otherwise, a technically correct charge can still create a support problem.
Write down those rules before implementation. This gives the person configuring payment and the person managing customers a common reference. It also makes testing useful: you can compare what happened with the service you actually promised.
Instalments and subscriptions have different end points
An instalment arrangement divides an agreed purchase into a planned set of payments. A subscription maintains a service relationship that renews according to its conditions. Both can involve several charges, but the commitments and end points differ.
The final instalment completes the purchase schedule. In a recurring service, the next period follows the renewal and cancellation rules. Define which model you sell before configuring messages and access. Sending the same payment link every month does not, by itself, establish recurring authorisation.
Our guide to one-off payments, instalments and subscriptions explains the operational differences and what each journey needs to manage after the first payment.
What to prepare if you use WooCommerce
Our plugin keeps products and order calculations in WooCommerce. The connection sends the lines and references required to prepare the payment, so you do not need to recreate the catalogue in AndorPay for this integration.
The store review includes checkout type, custom fields, shipping rules and enabled methods. If another system receives orders for fulfilment, include that handoff in your test. The useful journey continues beyond bank authorisation until somebody can deliver what the customer bought.
The expected result is straightforward: the buyer understands they paid, and your team finds a consistent order. The WooCommerce installation guide contains the current steps. Our virtual payment terminal page explains how we approach that connection for an Andorran business.
Prepare launch with concrete information
Tell us which platform and bank you use and whether you already have a virtual payment terminal. Add a short description of what you sell: physical products, services, digital access or subscriptions. This lets us prepare a relevant proposal, with terms provided privately.
Describe the journey from start to finish: arrival, selection, required details, payment and delivery. A simple outline is enough. What matters is knowing which system holds each piece of information and who needs the confirmation to take the next step.
Start in the appropriate test environment, then check production configuration separately. Credentials and enabled methods must match the public journey. A working demonstration in another environment does not establish that customers can already complete a live purchase on your site.
What to check before signing off the setup
Ask for a test purchase on a phone: the customer should recognise the product, see the total and know when payment is complete. Then check that your team can find the order without hunting through screenshots or separate emails.
Test a cancellation too. The buyer should be able to try again without ending up with two paid orders. Your integration team can use the webhook guide to check payment confirmations.
Finally, agree how a purchase will be refunded. API refunds are not yet enabled on our Redsys connection, so establish the available process before offering it to customers.
What to improve after you start collecting payments
Find where the journey stops: before payment, during authentication or after a confirmation that does not update the store. These situations need different fixes. Treating them all as abandonment hides the information needed to investigate the actual cause.
Associate support requests with specific orders. A question about two charges needs payment records; a delivery question needs the order and fulfilment status. Shared references mean your team can respond without reconstructing each sale from scattered messages.
Compare equivalent periods by device, payment method and sales channel. If a campaign changed alongside checkout, do not attribute the entire difference to the new button. Look at confirmed sales and the work needed to manage them, as well as clicks or started attempts.
Frequently asked questions
Is a payment link an alternative to a card?
They can work together. The link takes a customer to checkout, where a card may be the method used to pay. Decide how customers arrive first, then which payment methods will be available there.
Do I need to change platforms to take payments from Andorra?
That depends on your current system and its integration options. We review the existing setup before proposing a migration. A WooCommerce shop and a custom application require different implementation work.
Can one journey cover single purchases and subscriptions?
Parts of the experience can be shared, but recurrence needs its own configuration and ongoing management. One successful purchase does not establish that renewals, cancellations and subscription changes are ready.
Connect payment to the way your business sells
Tell us where you sell, what you deliver and whether payment is one-off or recurring. We will work through the AndorPay journey and identify what needs to be ready before launch.
Request a proposal for your payment setup. We will review your situation and provide the terms privately.
