To start accepting online payments from Andorra, you need to connect four things: the business making the sale, the bank or payment provider, the platform where the customer buys and what happens after payment. Start with a specific sale: what you offer, who buys it and how you will deliver the product or service.
At AndorPay, we help prepare that journey from your current starting point. You may already run a store, sell services through conversations or be planning a subscription. This guide explains the decisions to make, the information to prepare and the steps from your idea to the first payment, with a clear way to follow each sale.
Can online businesses in Andorra accept Bizum?
Yes. Bizum has an e-commerce payment service in Andorra. Creand’s official Bizum business documentation explains that merchants with a Virtual POS or POS Link can request activation of Bizum payments. This service is distinct from transfers between individuals.
Confirm the contract, terms and POS integration with your bank. Availability for an online purchase does not establish that your terminal supports recurring charges, subscriptions or every B2B transaction. These capabilities need a separate check for your business.
If your customers are outside Andorra
Start with a specific sale: an Andorran business sells a product or service to a customer in another country. The customer’s country, displayed currency, charge currency and settlement currency are separate details. Selling internationally does not automatically establish support for every card or currency.
Prepare these questions for your bank and integration provider:
- Does the service support the cards and countries of your intended customers?
- Which currency is displayed and charged? Is it also the settlement currency?
- If conversion is involved, who handles it and which terms apply?
- How is the sale confirmed, and how are refunds or failed renewals handled?
Our guide to preparing your bank’s virtual terminal helps structure that conversation. For the commercial side, see what to check in a payment proposal. Terms are provided privately for your business and configuration. This lets you compare the scope of the service instead of choosing solely on an advertised transaction fee.
Start with the first sale you want to support
Before choosing tools, describe an ordinary purchase in plain language. Someone finds a product on your website, chooses delivery, pays and receives the order. Or a client accepts a proposal, receives a payment request and agrees with you when the service will begin.
That description reveals what payment needs to support. A store must pass through the correct order and total. An agreed sale can use a payment link. A subscription needs to relate the first payment to later periods and the customer's access.
Define what a completed sale means for your business. It might be an order ready to pack, a confirmed service date or an account with active access. Payment is one step towards that outcome, and setup needs to reach it.
Write down five answers: what you sell, where the purchase is agreed, when the customer pays, what they receive afterwards and who checks completion. That gives us enough to start a useful conversation without asking you to choose a technical architecture first.
The four parts of online payment collection
| Part | What it contributes | What to establish |
|---|---|---|
| Your business | The offer and relationship with the buyer | Activity, seller and service terms |
| Bank or payment provider | The operations required to process payments | Eligibility, payment arrangements, capabilities and settlement |
| Website or platform | The purchase journey and its data | Order, customer, amount and payment connection |
| Work after payment | Delivery, access and customer support | Confirmation, responsibilities and follow-up |
These parts can be coordinated within one project, but they perform different jobs. Having a bank account does not mean you have a connected store. Likewise, a published website may still need the configuration that lets it collect and recognise payments.
Our work is to examine those connections against your actual sale. We start with what already works. Where something is missing, we define the work needed to complete the purchase you want to offer.
Which journey suits the way you sell?
A store with a catalogue and orders
If customers choose products, quantities and shipping in a store, payment needs to form part of that purchase. The total and reference must reach the payment connection correctly, and the result must update the matching order.
Include the usual variations: a discount, a different delivery address or a changed basket. The integration needs to follow your store's rules so that the person preparing the order can see what the customer actually paid for.
Our Andorra ecommerce payment gateway guide covers store integration in more detail. Your first step here is to identify the platform and any features that affect the sale.
Services sold after a conversation
Consultancy, a workshop or a bespoke project may be agreed after speaking to the customer. Once the offer is accepted, a payment link can take them to payment without turning that sale into a full product catalogue.
The request should make clear what they are paying for and what happens next. If a date, place or delivery is involved, retain that relationship. Payment does not automatically reserve a resource in every other tool you use.
You can start with fulfilment managed by your team and connect further tasks when needed. Our payment links guide explains how to prepare, check and share that journey.
Subscriptions and ongoing services
If customers pay while using a service, define the service period, renewal and cancellation arrangements. You also need to decide what happens to access when a payment is pending or not confirmed.
The first purchase and later charges need separate checks. Your connection must have recurring operations enabled, and the application must know which customer and period each result belongs to.
The guide to subscriptions on an existing payment terminal explores this preparation. To start, explain what the customer receives, how often they pay and how their access is currently managed.
A purchase paid in several instalments
For a sale paid in agreed instalments, identify the original purchase, payment schedule and final instalment. This is different from a service that continues renewing while active.
Set out what you deliver after each step and how you will handle a pending payment. Dividing an amount does not necessarily mean a third party finances the purchase. We review the arrangement and conditions you need before proposing the connection.
If you do not have a website yet
You do not need to settle every design detail first. Start with where the purchase decision happens: a page explaining the service, a sales conversation or a store where people select products.
If the sale needs a conversation, a clear presentation followed by a payment link after acceptance may be a suitable starting point. If buyers need to select items, quantities and shipping, you need a store that manages those details.
Decide who will edit the offer and handle sales too. A platform suited to a technical team may require more maintenance than you want to take on. The initial journey should let you sell and operate with the resources available, within a defined scope.
At AndorPay, we coordinate payment preparation with that starting point. Tell us what you have and what is missing. You do not need a finished website before discussing how customers will pay you.
A useful first version can focus on one representative offer. For a workshop, that could mean a clear description, the date, what is included and the next step after acceptance. You can then judge whether the journey works before expanding the catalogue or adding more complicated sales rules.
If you already have a website or store
Gather the address, platform name and a description of how customers buy. Note what works and where the problem appears: obtaining payment services, connecting them or managing the work after payment.
For WooCommerce, we have a documented integration connecting orders to AndorPay. The catalogue and calculations stay in WooCommerce. The review includes store customisations and extensions involved in the purchase.
If you use Shopify, we examine the available journey for your case before promising a connection. Where the platform cannot meet the need, we review an alternative with you and explain the work involved. That decision needs to consider the catalogue, orders, content and day-to-day operation.
For a custom application, your development team can examine the API connection and confirmations. Our hosted checkout and API guide explains the division of work without requiring you to build every part of the payment interface.
A demonstration can help clarify the case. Show an ordinary purchase using the screens you already have and identify the point where the customer should pay. The commercial goal can be understood without opening the code or making you choose the implementation beforehand.
What to discuss with the bank or provider
The business and activity receiving payment
Introduce the business making the sale, the product or service and the planned channel. Acceptance depends on the provider and activity; a list of payment methods is not a substitute for that review.
Explain what customers buy, when they pay and how they receive what was agreed. The bank or provider will specify the information and documents needed for your application. Different activities and payment arrangements may follow different processes.
The payment terminal needed for online sales
An in-store card terminal and an online payment terminal support different journeys. If you already accept payments in person, establish which service you have and what needs to be added for online sales.
Andorran banks publish services for these uses. You can consult MoraBanc's online payment terminal, Creand's ecommerce service and Andbank's online payment terminal. The contracted journey and capabilities need confirmation for your business.
Our guide to preparing your payment terminal with your bank brings together the relevant questions. You do not need to change banks before reviewing the infrastructure already available to you.
The payment methods and operations in your project
Explain whether you want one-off payments, subscriptions, wallets or several arrangements. In our connection, the capabilities enabled on the terminal must match the prepared journey. A visible button does not activate a payment method by itself.
Establish where operations can be viewed and how bank settlement is identified. The person checking collections needs to connect each sale to its payment without relying on screenshots sent by the buyer.
It is useful to keep one contact for the banking setup and one for the website connection. This makes it easier to route a question about an enabled capability separately from a question about an order that failed to update. The responsibilities should be clear to the person coordinating launch.
Which payment methods should you offer first?
Start with how your customers buy and what your connection supports. Cards, Apple Pay and Google Pay can form part of the journey, subject to the terminal, device and relevant configuration.
There is little value in presenting methods that will not work for the buyer. Check their appearance on eligible devices and maintain a clear experience when an option is unavailable. If Bizum is part of the project, we specifically confirm the required flow and activation.
The payment methods guide for Andorran businesses explains those differences. At this stage, choose the set that supports your first sale and can be checked all the way through.
If Stripe does not support your business
Andorra is not listed among the countries supported for direct Stripe account opening. That limitation can become apparent after you have chosen a tool that depends on Stripe to collect payments.
The next step is to work out how to accept payment through your Andorran business. At AndorPay, we examine your platform, banking setup and sales model to prepare a suitable journey.
If the restriction affects an existing store or service, identify what depends on Stripe: the payment form, renewals or customer management. That information helps establish the connection required. Our guide to Stripe alternatives in Andorra explores this situation further.
Setup, step by step
1. Define the journey and expected outcome
We agree on a representative sale and its completion: an order ready to fulfil, a confirmed service or updated access. We also identify the information that needs to remain available for customer support.
The scope includes the payment arrangements you will use from the start. Further options can be reviewed later against the established journey. This makes the first launch complete and understandable rather than an isolated payment button.
2. Confirm the required configuration
We review the platform, terminal status and capabilities the project needs. We identify what each party must prepare and which decisions remain outstanding.
Credentials are handled through the agreed configuration channel. To request a proposal, simply describe your situation. You do not need to submit banking secrets or API keys through a commercial enquiry form.
3. Prepare the connection and customer messages
We connect the point of purchase to the payment outcome within the agreed scope. The sale retains a reference that makes it recognisable in the store, dashboard or relevant application.
We also review what customers see. They need to know what they are paying for, whether the operation has finished and what happens next. A pending payment requires a different message from a delivery confirmation.
4. Test the complete journey
A successful purchase, a decline and a cancellation are checked in the test environment. The review covers the total, reference, final status and action after payment.
For subscriptions, it includes the lifecycle scenarios the business will use. For wallets, it distinguishes opening the payment sheet from completing authorisation. The payment integration testing guide provides the detailed checks.
5. Prepare launch and ongoing checks
Production uses its own credentials and enabled capabilities. Live validation follows an agreed scope before treating the journey as open to customers.
Your team needs to know where to find a payment, how to locate the related purchase and what to do when something is unclear. Setup is complete when the prepared journey can be used and understood in daily operations.
Keep a simple handover record for the people handling sales. It can identify where orders are viewed, who receives questions and which details to collect when an operation needs investigation. This is particularly useful when the person managing the website is not the person answering customers.
Three examples to help you choose a starting point
These illustrative situations show how to apply the guide to your business: what needs to be ready now and what you can add later.
A store that receives orders but takes bank transfers
Imagine that a buyer selects products and receives bank transfer instructions. You check the bank account, find the order and update its status before shipping. The specific problem is the gap between the purchase and its confirmation.
The first improvement is to connect payment to the order you already have. Keep the catalogue, variants and delivery rules. Ask for a purchase that can be completed on a phone and linked to the correct order. If you use WooCommerce, this is the starting point for our integration.
Before adding more methods, check whether you spend less time finding incoming payments and whether buyers understand when their order will ship. More payment buttons alone will not fix an unclear confirmation.
A professional who sells after a quote is accepted
Imagine a session, project or repair agreed by email. The customer has already accepted what the service includes. Building a complete product catalogue for this sale may add work without making the decision easier.
A payment link tied to the quote lets you request payment at the right moment. Decide whether payment confirms a booking, is due when the work is finished or covers a project stage. The message should explain that agreement and what you will do once payment is confirmed.
If the booking depends on a calendar, decide who reserves the slot. Your team can handle that initially. If you need automation, the calendar connection must be included in the scope. A payment link does not automatically reserve a place in another application.
A course provider that wants to stop chasing monthly fees
You need to define the joining date, the period covered, renewal and cancellation. Sending a link every month can make payment easier, but the customer still needs to act. It is not the same as an automatic subscription.
Before choosing the connection, explain what happens when someone joins halfway through a month or cancels before the next charge. Decide how you will contact them if a renewal fails. These are service rules that need to be reflected in payment collection and access to classes.
Setup should include a test renewal and cancellation as well as the initial signup. Our guide to subscriptions using an existing virtual terminal covers this case in more detail.
What to review after the first payments
Observe where purchases get stuck and what questions your team receives. Repeated uncertainty about the next step may mean the confirmation needs clearer wording. An order without a usable reference may reveal an incomplete connection.
Distinguish a confirmed payment, a prepared order and funds settled by the bank. They are related stages with different records. Keeping them separate helps answer both the buyer and the person reviewing the accounts.
If an operation is pending, check its status before starting another. If you need a refund, review the available process: Redsys refunds are not enabled in our current API. We establish how that requirement is handled within your operation.
When expanding the catalogue or changing the store, check the affected journey again. Adding a subscription, a delivery option or another tool can change the information that needs to accompany payment.
Assign someone to review those initial results. A simple list of purchases, incidents and questions can be enough to identify adjustments. What matters is turning useful observations into specific improvements to the customer journey.
Understanding the commercial proposal
Ask for banking services, the platform connection and required support to be distinguished. These parts need to be explained against the same use case so you can assess the proposal as a whole.
Check what preparation includes, what assistance you will have after launch and which changes would sit outside the initial scope. If you already have a banking agreement or integration, share that context so we can review what can be retained.
At AndorPay, we prepare a private proposal based on your volume, payment arrangements and setup needs. Our guide to payment terminal costs explains the components worth understanding before deciding.
A checklist for starting without every answer
| Information | What you can prepare now |
|---|---|
| Your offer | Product or service description and an ordinary purchase |
| Your sales channel | Website, store, application or sales conversation |
| How you collect payment now | Transfer, link, terminal or another existing journey |
| What you want to add | Website payments, links, instalments or subscriptions |
| Banking situation | Bank and whether an online terminal is available |
| What happens afterwards | Shipment, service start or access to activate |
| Who manages it | Person handling sales and technical help, if available |
| Your obstacle | A specific problem or undecided question |
You do not need to fill every box before contacting us. A clearly described sale and your current situation are enough to identify the next step. Technical decisions can be refined during the project review.
Frequently asked questions
Can I accept payments without a complete online store?
Yes. An agreed sale can use a payment link. You need to identify the offer and manage what follows payment. If customers need to choose products, quantities or shipping, we review a store-based journey.
Is an account with an Andorran bank enough?
The account is one part. You also need to confirm the payment service contracted, required capabilities and connection to your website or commercial process.
Do I need to replace my entire platform?
We first review what you use and the sale you need to support. An existing connection may provide a starting point. If there is a limitation, we explain the options and their scope before proposing changes.
How long does setup take?
It depends on the platform's readiness, banking activation, payment arrangements and integration work. After reviewing your case, we can organise the steps and explain which dependencies affect the schedule.
Prepare your first payment journey with AndorPay
Tell us what you sell, how customers pay now and what you would like to offer. We will review the platform, payment connection and work after the sale with you, so that you understand what is needed and what setup includes.
Request a proposal for online payments from Andorra. You can start from your current situation, with a solution defined around the sale you want to make.
