A payment gateway for an Andorran online store needs to connect the purchase to payment and return a result that lets your team manage the order. The customer needs to pay without losing the purchase context; your team needs to know whether fulfilment can begin. That complete journey is what needs integrating, even though the card button is its most visible part.
At AndorPay, we connect payment to the banking infrastructure and the store or application your business uses. This guide covers ecommerce integration: platform, checkout, order data, payment states, exceptions and launch. If you are still deciding how to sell, start with our general guide to taking online payments from Andorra.
What the gateway needs to do for your store
The gateway participates in payment authorisation and communicates its outcome. The integration associates that outcome with the purchase. When both are prepared, a confirmed payment belongs to a specific order and the buyer receives a clear explanation.
The store keeps other responsibilities: calculating the purchase, collecting required information, managing stock and delivering. A successful charge does not complete a missing address or decide which product to ship. Launch checks therefore need to follow the purchase from basket to order fulfilment.
A missing button, an order still pending after payment and an absent confirmation email are different symptoms. Separating them helps you intervene at the right point without rebuilding the store to resolve a problem affecting one connection.
The parts involved in a purchase
The buyer sees one journey, but the store, payment connection and banking infrastructure work together. Your management system may add another stage to prepare shipping or activate a service.
| Component | Role in the sale | Information to retain |
|---|---|---|
| Store or application | Prepares the purchase | Order, lines, amount and customer |
| Checkout | Presents the payment action | Session associated with that purchase |
| Processing | Obtains the authorisation outcome | Operation and confirmed state |
| Integration | Updates the sale | Relationship between order and payment |
| Delivery or access | Fulfils the purchase | Shipment or service status |
You do not need to manage every part manually. You do need a clear relationship between them so your team can find a sale without reconstructing it from scattered messages, screenshots and similar amounts.
Review the store you already have
Identify the platform, checkout type and customisations that affect orders. Include taxes configured within the store, delivery options, coupons, variants and any tool receiving orders after payment.
Choose a representative purchase and follow it through. Note where the total is calculated, when the address is collected and which screen your team uses to prepare delivery. This review defines what the payment integration needs to preserve.
If you already have a gateway, describe what works and what needs improving. A missing method, excessive manual work and an order update problem call for different changes. A specific requirement lets you keep the project focused and check afterwards whether the issue was resolved.
Your platform determines the starting point
WooCommerce
Our plugin connects WooCommerce to AndorPay. Products and calculations remain in the store; the plugin sends the lines and references required for payment. You do not need to recreate the catalogue in AndorPay for this integration.
The documentation covers classic checkout, Checkout Blocks, HPOS and payment for an existing order. Before installing or updating, identify the WooCommerce and plugin versions and any extension that changes checkout. Use the current WooCommerce guide to prepare the corresponding setup.
Shopify and platforms controlling their checkout
The platform determines which connections it allows and how payment is presented. A provider being compatible with a tool does not automatically make every method or recurring model available within that integration.
If you use Shopify, we review the supported journey and the way you sell before proposing changes. If the platform cannot cover the requirement, another option needs to be assessed with its full scope: products, orders, delivery and your team’s work. The decision starts with the actual operation.
A custom application
Your server prepares the purchase and creates a session through the API. The customer opens the returned checkout address, while your application processes events communicating the outcome. The REST integration guide describes that connection.
Define the relationship between customer, product, order and payment from the beginning. The API connects systems; fulfilment and access rules remain part of your application. Keeping that distinction makes it easier to preserve the journey when your catalogue or screens change.
Hosted checkout and the store experience
A hosted checkout uses a payment page prepared by the payment platform. Your application creates the session and sends the buyer to its address. It then receives the confirmation required to continue the sale.
In WooCommerce, our plugin connects the usual shopping process to the available payment methods. The customer retains the order context while completing payment. The experience you choose needs to account for the platform, ongoing maintenance and the information you must collect.
An API integration can use a hosted checkout; these are not mutually exclusive approaches. The API describes how systems communicate, while checkout describes where the person pays. Our hosted checkout and API guide explores the distinction and the responsibilities it creates.
Prepare the virtual terminal for the operations you will offer
The banking connection needs to match your sales journey. Identify whether you need one-off purchases, digital wallets or recurring payment. Each has preparation and activation requirements; holding a virtual terminal agreement does not establish that every option is enabled.
In our WooCommerce integration, cards require Redsys inSite. Apple Pay and Google Pay require X-PAY and the relevant bank and wallet configuration. The methods offered depend on merchant activation and the buyer’s supported environment.
Useful initial information includes your bank, virtual terminal situation and ecommerce platform. We use that to define preparation and scope. Our guide to Andorran banks and virtual terminals helps structure the conversation with your bank.
Preserve the link between basket and payment
The authorised amount must match the purchase prepared by the system. It includes the products, variants, discounts and delivery calculated for the order. If something changes before payment, the journey must apply that change consistently.
For example, changing the delivery country may affect available shipping options. The buyer needs to review the correct total before authorising. Using an earlier amount creates a discrepancy your team will later have to resolve.
Keep a common reference between the order and payment operation. Following a cancellation or decline, record which attempt belongs to the purchase as well. This lets you recover the sale without confusing an earlier unsuccessful attempt with the result of the next one.
Delivery information is part of checkout
For physical goods, define the fields required to ship the product. Inspect the address, contact details and delivery option on the final order. For a digital product, identify the email address or account that will receive the resource.
Wallets can simplify data entry, but do not assume they provide every required field in every situation. The journey needs a way to collect missing information. Include custom fields and address-dependent rules in your tests.
The useful check ends with a purchase that can be fulfilled. If somebody has to contact the customer for a required detail afterwards, identify where it was missed. Payment can be correct while another part of checkout still needs adjusting.
What needs to happen during authorisation
The shopper selects a method and completes the requested action. Additional authentication or a waiting period may follow. The screen should retain the purchase context and explain what is happening without encouraging another attempt before the result is known.
A decline needs an understandable next step. Voluntary cancellation should allow a return to the shopping journey. A pending response needs separate handling because it is not yet a final outcome.
Our payment lifecycle documentation describes AndorPay states. The integration team uses those states to determine when another attempt is appropriate and when the existing operation should continue to be checked.
Browser return and payment confirmation are different events
A thank-you page guides the buyer, but does not replace the result confirmed by the server. The browser may close before returning, and a notification may arrive later. The integration needs to cover both situations.
AndorPay events communicate the outcome to your application. Your system verifies the notification and applies the corresponding update. The webhook guide explains the connection and signature verification.
If the same notification arrives again, it must not trigger another delivery. The application recognises the operation already processed. You can check that behaviour by repeating the relevant test event rather than creating a second payment to see what happens.
Translate payment outcomes into order states
Your team works with commercial statuses such as awaiting payment, ready to fulfil, shipped and complete. Their rules need to reflect payment, but also the product and delivery work remaining.
| Payment outcome | What the store needs to do |
|---|---|
| Confirmed | Associate it with the order and apply fulfilment rules |
| Pending | Retain the reference and wait or query the result |
| Action required | Allow the buyer to complete the requested step |
| Failed | Keep the order unpaid and offer appropriate recovery |
Do not mark an order delivered simply because payment succeeded. Do not ask for another payment merely because a fulfilment screen has not updated. First identify which stage finished and which still needs synchronising.
Keep payment attempts distinct from purchases
One order can need more than one payment attempt after a genuine decline. Your records should show the attempts while preserving a single purchase to fulfil. Otherwise, a recovery attempt can look like an additional order to somebody processing shipments.
The reverse distinction matters too: two legitimate purchases from one customer are still separate orders. Shared customer details or an identical amount are not sufficient to merge them. Use the order and payment references assigned to each journey.
Practical WooCommerce preparation
Install the appropriate plugin version and open its payment settings. The guide documents the API and checkout addresses, the test-environment key and activation of available methods. Follow that sequence so the components all use the same environment.
Saving the connection prepares the plugin identity and notification registration. The communication route must remain reachable, and scheduled tasks must be able to run. If a firewall blocks a request, adjust the specific access required by the integration.
The documentation explains how to inspect scheduled actions and synchronise an order with AndorPay. Use these tools to restore consistency with an existing payment. Manually completing an order or requesting payment again without examining that operation can hide the original problem.
Prepare a clear response to incidents
If a customer says they paid while the page is still waiting, find the order and operation first. Check the confirmed result before deciding whether another attempt is needed. The immediate task is explaining what happened to that purchase.
If payment is confirmed but the order remains unchanged, inspect communication between the systems. If the order is correct but an email is missing, investigate customer notification. Separating these cases prevents unnecessary changes to the authorisation journey.
Retain references, timing and the observed outcome. You do not need the customer’s full card number to investigate. Your team needs information that identifies the journey, together with a clear way to explain its current state and the next step.
Refunds and cancellations need an agreed process
Cancelling before payment, ending a service and refunding a collected payment are different actions. Define what customers can request and how your team handles each case. The store should reflect the operation that has actually occurred.
Our documentation states that the current Redsys adapter does not support refunds through this API. The refund procedure therefore needs defining for the merchant connection before automation is offered. Recording an internal request must not display a refund as though funds have already been returned.
Associate that work with the original order and payment. It lets you answer later questions and distinguish a requested refund from a completed one. Commercial terms and payment actions need to remain consistent throughout the follow-up process.
If the store sells subscriptions
Recurrence adds a lifecycle after the first purchase. Define the period, renewal, changes and cancellation, together with the associated delivery or access. One successful initial authorisation does not establish that the whole cycle is ready.
In AndorPay, this journey requires the subscription capability and a suitable connection. Your application uses available events and operations according to its service rules. Our Redsys recurring payments guide explains the specific preparation.
If migrating subscriptions, establish how saved payment methods and the next collection will be handled. Do not assume portability or leave two systems scheduling the same service period. The transition must assign each relationship to a system and an effective date.
Build a test around the sales you actually make
Select common orders: a shipped product, a variant, a discount if used and a digital resource if part of your catalogue. Inspect the total before authorisation and the stored details afterwards. There is no need to invent combinations your store does not offer.
Include success, decline, cancellation and browser closure. Add a repeated notification and a delayed confirmation. For each case, define in advance what the buyer should see and which state your team expects. The test then compares an observed result with a concrete requirement.
| Scenario | Outcome to inspect |
|---|---|
| Normal purchase | Order, amount and confirmation match |
| Delivery change | The buyer’s reviewed total is used |
| Cancellation | The purchase keeps an understandable state |
| Delayed response | The store recovers the existing result |
| Repeated event | No duplicate shipment or access activation |
| Compatible wallet | Authorisation and required details are retained |
The testing guide explains environments and scenarios. Keep references for each case so an issue can be investigated without involving another customer transaction.
Include the person who fulfils orders
Ask them to inspect a test order through their usual screen. They need to recognise the product, delivery option and payment result. The information useful to a developer is not always the information required by the person preparing a shipment.
For a digital product, do the same exercise with whoever manages access. If a status is ambiguous, clarify its wording or business rule before launch. This small check prevents a technically working integration from still requiring a conversation for every sale.
Launch with production configuration
Before opening the journey, check the domain, credentials and production methods. If tests used a temporary address, review the settings affected by the move to the final domain. Keep a clear record of the version and integration in use.
Prepare the team’s response if a problem appears during opening. It may involve stopping new requests through the affected method while outstanding operations are reviewed, preserving their existing information. Avoid leaving customers with two attempts and no explanation of which belongs to their purchase.
Launch is complete when the published journey and its management have been checked according to the agreed plan. Deploying files, saving settings or displaying a button are intermediate steps rather than proof of the complete purchase experience.
Review sales and operational work after the change
Inspect confirmed payments, outstanding orders and customer questions by device and payment method. If a campaign changes at the same time, account for it when interpreting results. Different traffic sources can change buying behaviour independently of the checkout.
Also examine how much work a sale requires before it is ready to fulfil. Authorisation can succeed while delivery or confirmation still generates questions. Those enquiries help identify the next useful adjustment.
Use shared references to inspect specific cases. Improvement should appear in a clear buying journey and manageable orders as well as the page’s appearance. That foundation makes it easier to add payment methods or automation when the business needs them.
Frequently asked questions
Do I need to replace my store to use AndorPay?
We review the platform and existing journey before proposing changes. WooCommerce has a documented integration. Other platforms need assessment of their available connections and the scope required for your sales.
Can I keep my WooCommerce catalogue?
Yes. Our plugin uses the lines and references calculated by the store. You do not need to duplicate that catalogue in AndorPay for this connection.
What if the buyer closes the page after paying?
The result should be recovered through server communication and linked to the order. Returning in the browser is not the only route for receiving confirmation.
When should I add more payment methods?
When they give buyers a useful option and the connection is prepared. Check each method’s complete journey, including delivery details and the final order state, before offering it publicly.
Connect payment to the whole store
Tell us which platform and bank you use and what needs improving. We will examine the complete purchase and prepare a defined proposal for your AndorPay integration.
Explore our virtual payment terminal for Andorra and request a review of your store. Scope and terms are provided privately.
