You can offer Apple Pay and Google Pay through an Andorran online store when your payment setup, integration and the shopper’s environment support them. At AndorPay, we connect that payment journey to the order your business needs to fulfil. Getting ready to launch means checking both the customer’s screen and the result recorded by your store.
This guide covers preparation, the WooCommerce integration and practical checks when a wallet button is missing or an order does not reflect the payment outcome. It is for merchants who want to add a useful payment option without leaving the rest of the checkout unfinished.
Your customer’s card issuer and your payment setup
A bank supporting Apple Pay or Google Pay for its cards answers a customer’s question: can I pay with my phone? Your business needs to check something different: whether its merchant agreement and website integration support accepting that payment.
Do not choose a store integration solely because your bank advertises a digital wallet in its app. Tell your banking contact that you want to accept Apple Pay or Google Pay at your online checkout, then confirm the requirements with whoever manages the integration. Test a complete purchase, including the order confirmation. Both the customer’s card compatibility and your merchant configuration need to support the journey.
What changes for a shopper using a digital wallet
Apple Pay and Google Pay let shoppers use a payment method already saved in a compatible environment. Instead of entering their card details from scratch, they choose an available method and complete the authorisation requested on screen.
That can make a practical difference on mobile: the shopper does not need their physical card beside them to complete the purchase. However, a wallet button handles only part of the journey. Your store still needs to identify the order, collect the details required for delivery and explain the payment result clearly.
Adding a logo does not guarantee a conversion increase. To understand its effect on your store, look at which shoppers can use the wallet, how many payments are confirmed and where people need help. Those observations are more useful than assuming the same result for every business.
In-store contactless payments and online checkout
Accepting a wallet on your shop’s card terminal is a different setup from offering it on your website. Online payments involve your ecommerce connection, domain and the methods enabled for that particular integration. A working contactless terminal does not establish that the website is ready.
When requesting activation, explain that you want to take payments online. Include your ecommerce platform and whether customers use an embedded or hosted payment page. If you also run a physical shop, identifying the channel prevents time being spent on the wrong configuration.
What needs to be ready before activation
Your business and payment terminal configuration
We start with your bank, whether you already have a virtual payment terminal and the methods enabled for it. In our WooCommerce integration, Apple Pay and Google Pay require X-PAY together with the relevant bank and wallet configuration.
The Redsys Apple Pay documentation describes different integration paths. The instructions followed must match the connection being implemented. Steps for a direct integration cannot automatically be applied to a hosted payment page.
The website where customers will actually pay
The review includes the store’s address and the checkout reached by the customer. If initial testing uses a temporary domain, moving to the live domain needs to be reflected in the setup. The meaningful check is the journey buyers will use after launch.
A firewall, maintenance page or access restriction can interrupt parts of the connection. If something fails, identify the blocked request or missing resource before changing unrelated settings. This helps preserve the working parts of the store and makes the fix easier to verify.
The shopper’s device and payment method
Two people can see different payment options on the same checkout. Availability depends on the supported environment, the shopper’s prepared payment method and your merchant configuration. A difference between devices is not enough on its own to establish a fault.
The Google Pay web documentation explains its integration journey. When testing your store, use a device and account prepared for the method being checked. Keep a clear card payment route available for customers who do not have a compatible wallet.
How WooCommerce and AndorPay work together
Our plugin connects WooCommerce to AndorPay and presents the available methods during checkout. The methods share the connection settings; you then enable those supported for your merchant account.
Your catalogue remains in WooCommerce. When a payment is prepared, the plugin sends the order information calculated by the store, including its lines and product references. You do not have to recreate that catalogue in AndorPay for this integration.
The WooCommerce installation guide covers the current requirements and configuration. Before changing a live setting, identify the plugin version installed on your store and use the corresponding instructions. That matters when investigating a behaviour that may have changed between versions.
From the wallet button to a paid order
The buyer chooses the method and completes authorisation. AndorPay receives the result and the integration associates it with the order. Your team needs that confirmation in the system used to fulfil the sale, not only on the customer’s screen.
A launch check therefore includes both the confirmation page and the final order status in WooCommerce. It also needs to cover a buyer closing the browser before returning to your store. The order must be handled according to the confirmed payment result, rather than depending solely on the return page being opened.
Delivery details still belong to the checkout
A store shipping physical goods needs a usable address and suitable contact details. A digital service may require a different set of information. Decide what your business needs before testing, then inspect what is actually stored against the final order.
Do not assume that every wallet journey will supply every field your store requires. The checkout needs a clear way to collect missing information. This is particularly relevant if you have customised checkout fields, shipping rules or the way an address determines delivery options.
Run a complete check before making the method public
Start in the appropriate test environment. The store, credentials and AndorPay connection must all belong to that environment. Wallets have specific testing conditions: displaying a button or opening the wallet sheet does not prove that an authorisation can be completed.
Next, work through the purchase from the beginning. Add an item, choose delivery, select the payment method and complete the requested action. Finally, inspect the order in the store administration. Jumping straight to a payment button can miss a problem earlier in the checkout.
| Check | What you need to observe |
|---|---|
| Availability | The method appears in a supported, enabled environment |
| Purchase | The amount and reference match the order |
| Authorisation | The result is received and correctly identified |
| Order | Its status reflects the confirmed payment |
| Delivery | The saved details allow the sale to be fulfilled |
| Cancellation or decline | The shopper understands the result and can continue |
Keep the order and payment references for each check. If the two systems disagree, these identifiers help trace the existing operation. They also prevent a troubleshooting conversation from becoming an unnecessary request for the customer to pay again.
Include a realistic shipping example
For a physical product, use the same shipping rules customers encounter. Check an address that selects a delivery option, any required contact field and the order summary shown before authorisation. Then inspect the stored address rather than assuming that a successful payment means delivery information is complete.
For a digital product, check the account or email that will receive access. The payment method may be identical, but fulfilment depends on different information. Testing both journeys is useful when your catalogue includes physical and digital goods.
Troubleshooting the most common symptoms
The wallet button is missing
First check whether the method is enabled for the merchant and in the store. Then look at the shopper’s device, browser and available payment method. Compare environments while keeping the product and purchase conditions the same.
If the button appears nowhere it should, start with the merchant connection and settings. If it is absent only on certain devices, use that difference to narrow the investigation. Record what happens before changing settings so the eventual fix can be checked against the original symptom.
Authorisation seems complete but checkout keeps waiting
Inspect the payment status before starting another attempt. A delayed screen update does not establish that the authorisation failed. First link the order to its existing payment and find the result confirmed by the server.
Our payment lifecycle guide explains the difference between browser navigation and the recorded payment state. Keeping those separate helps handle delayed updates without creating a second authorisation to resolve an interface problem.
The payment is confirmed but the order is pending
In this situation, inspect communication between the integration and WooCommerce. The plugin documentation describes notifications and recovery mechanisms that bring the order into line with the confirmed payment.
The immediate task is to update the existing order from the existing successful operation. Your team should identify that operation before giving the customer further payment instructions. An order synchronisation issue needs a matching status update, rather than an assumption that another purchase must be made.
What to measure after launch
Review started attempts, confirmed payments and orders requiring intervention by payment method and device. Use comparable time periods, and account for changes in traffic sources. A new campaign may bring a different group of shoppers, affecting the overall completion rate independently of checkout changes.
Customer support questions provide useful context. If buyers frequently ask whether they paid, review the confirmation message. If your team has to request delivery addresses after payment, review the information collected during checkout. Successful authorisation is one part of a successful purchase.
Frequently asked questions
Do I need to offer both Apple Pay and Google Pay?
Prepare the methods that fit your audience’s devices and are available for your merchant setup. Keep an understandable route for customers who use neither wallet. The aim is a checkout people can complete in their own environment.
Can I enable wallets if card payments already work?
A working card connection is a starting point, but wallet settings need their own review. Share your bank, virtual terminal and ecommerce platform so we can identify what preparation your store requires.
Is seeing the button enough to launch?
Check authorisation, confirmed payment status, the final order and the information needed for delivery. A visible button is the beginning of the journey; the check ends when your team can fulfil the purchase correctly.
Prepare wallets for your online store
See how we connect a virtual payment terminal in Andorra, or read our payment methods guide if you are planning the whole checkout. Tell us which platform and bank you use and how you currently take payments.
Request an integration review. We will work through the required AndorPay setup and provide your proposal privately.
