Andorpay
Back to the blog

Published on · Updated on

Payment fees in Andorra: what to review

Understand your banking service, website integration and payment management. Prepare a private proposal for your business in Andorra.

Calculator between two stacks of receipts and coins for comparing payment costs.

If you are researching payment gateway fees in Andorra, you probably need a practical answer: what do you have to arrange to accept payments, and what does each service include? A useful proposal separates the banking service, the connection to your website and the work involved in managing payments. All three should be clear before you launch.

At AndorPay, we prepare a proposal around your business, your platform and the way you sell. This guide explains what to look for, what information helps us define the work and how to avoid a setup that makes daily operations harder than they need to be.

What are you arranging when you request an online payment service?

In Andorra, you will often see a bank's online card payment service described as a “TPV virtual”. Your bank sets the terms of that service and enables the payment capabilities available to your business. Connecting it to your website and handling the order after payment are further parts of the project.

Consider an ordinary purchase. A customer adds a product to their basket, enters their details, authorises payment and expects confirmation. Your team needs to identify the order, see its correct status and prepare the shipment. Processing the card payment and updating the order belong to the same sales journey, even when different systems handle them.

A proposal should therefore explain who takes care of each step. “Accept card payments” leaves several questions open: how the service connects to your platform, what happens when a customer closes the window and where your team can investigate a pending payment.

In-store terminals and online payments serve different journeys

If you already take cards at your premises, you have a solution for part of your in-person sales process. Selling through a website requires reviewing the online service and its integration. Having a physical terminal does not establish that your online checkout is ready.

Be specific when you describe the project. “We need to take payments for orders in our WooCommerce store” gives a clearer starting point than a general request for a payment terminal. Mention any subscription plans too: an individual purchase and an automatic renewal involve different steps and requirements.

Three parts a payment proposal should explain

1. The banking service and payment processing

This covers your relationship with the bank and the terms that apply to transactions. You should be able to identify the service you are contracting, the methods enabled for your business and how you will receive transaction and settlement information.

For a business with an existing online payment service, we start by understanding its current configuration. That gives us a concrete basis for reviewing its connection to AndorPay. If you have not arranged the banking service yet, we can review what needs preparing for your intended sales journey.

A bank's public information helps explain its product, while your own account documentation establishes your agreed terms and enabled capabilities. For example, MoraBanc describes its online payment service and payment methods. That is a useful product reference, which needs to be considered alongside the configuration of your account.

2. Integration with your store or application

This part explains how customers reach the payment step and how your business receives the outcome. Depending on your website, the project may use an existing store integration, a hosted checkout or a connection from your application's server.

For WooCommerce, our integration connects the checkout and payment confirmation to the order. Your store remains the source of product information: the plugin sends the order details without requiring you to recreate your catalogue in AndorPay. You can review the flow in our WooCommerce integration documentation.

To define the work, we need to know which platform you use and whether the website is already live. Extensions that change the checkout, custom development and the person responsible for technical changes are also relevant. These details help us specify the connection your actual store needs.

3. Managing payments after checkout

An online store needs to match payments to orders. A subscription service also needs to track sign-ups, service periods and renewals. If you sell through payment links, your immediate priority may be identifying the customer and the piece of work associated with each payment.

AndorPay connects payments with that operational process. The proposal should explain which functions you will use and how they connect to your tools. You can then see what will be ready at the end of setup and which tasks your team will continue to handle.

A description of everyday work is more useful than a feature list alone. Who checks a pending payment? Where can the team identify a failed renewal? How does the service update customer access? Answering those questions helps establish whether the setup fits the business.

What changes with the way you sell?

The following examples describe sales situations. They are not customer case studies or quotations. Use them to identify the steps your own integration needs to cover.

An online store that ships products

Checkout and order handling need to work together. The customer should understand how to complete the purchase, and your team should know when it can prepare the shipment. The flow also needs checking after a decline, an additional authentication step or a confirmation that arrives after the customer has closed the page.

Share your platform, the payment methods you want to offer and the way you handle orders. If you are considering moving the store to another platform, explain the problem you are trying to solve before making that decision. The payment integration should fit the tools and working practices your business needs.

A professional selling services after a quotation

You may agree the work by email, phone or in a meeting, then need a straightforward way for the customer to pay. That journey should identify the job, provide the appropriate payment link and let you confirm the result before starting or delivering the service.

Explain when payment is due: when the customer accepts the proposal, before an appointment or at the end of a project stage. Identify who will check incoming payments too. This lets us define a proportionate setup without assuming that your business needs an online shop with a shopping basket.

A business selling subscriptions

Sign-up is the beginning of this journey. After the first payment come renewals, possible payment problems and cancellation requests. Your systems need to connect those changes with the service the customer receives.

We need to understand the billing schedule, where customer access is managed and whether you already have active subscriptions. Recurring payments depend on the capabilities enabled for your banking setup. Our guide to subscriptions with an existing payment service explains this journey in more detail.

What we need to prepare a proposal

You do not need a lengthy technical specification to start the conversation. A clear description of how you sell is usually more useful. The following information helps us understand the project and avoid unnecessary rounds of questions:

Information Why it helps
Business activity and product or service Understand the sales and delivery journey
Website platform and address Review the integration required
Bank and current online payment setup Establish the starting configuration
Individual purchases, links or subscriptions Define the functions you intend to use
Expected volume and customer markets Understand the scale and review requirements
Systems receiving orders or enabling access Plan what happens after payment
Current problem and intended launch date Set implementation priorities

If you have not started selling yet, say so. We can work from your planned launch and distinguish what is necessary to start from connections that can be considered later. For an existing business, explain where staff have to intervene manually or what is preventing you from taking new sales.

There is no need to send passwords, API keys or full card details at this stage. Business information and the state of your current integration are enough to begin. Technical credentials are handled later through the relevant configuration process.

It also helps to describe one typical order in your own words. Tell us where the conversation starts, how the customer agrees to buy and what your team does once payment is confirmed. That short account often reveals dependencies that a list of software names would miss.

How to review the scope before you accept

A clear proposal should let you picture the finished process. You should be able to explain what the customer will do, what your team will see and who will carry out the necessary configuration.

Check that the platform, intended payment methods and included operational work are identified. Any actions required from your bank or developer should be stated too. Agree how the integration will be checked: a successful authorisation alone does not demonstrate that the order status and communication with your systems are correct.

Commercial terms belong in the private proposal. That is where we set out the contracted service, implementation work, ongoing support and the terms relevant to your project. Keep the proposal with your banking documentation so that responsibilities remain easy to distinguish.

Before accepting, walk through a sale with the people who will handle it. Check whether any step has been left without an owner, such as investigating an uncertain payment or passing a confirmed order to the delivery team. This makes the written scope meaningful to the people who will use the system.

Frequently asked questions about payment fees in Andorra

Can I request a proposal if I already have a payment service?

Yes. Tell us which bank and platform you use and how you currently take payments. We will review the configuration and the connection required. An existing service gives us a starting point; the purchase journey and enabled capabilities help define the remaining work.

Will the bank also connect my store?

The banking setup and website integration should have clearly assigned responsibilities in your proposal. Identify who configures the connection, who checks order handling and whom your team should contact if something goes wrong. You will then know what each party is expected to deliver.

Can I add subscriptions after launching individual purchases?

Explain that plan at the start so the dependencies can be reviewed. Subscriptions introduce renewals and ongoing status management; they involve more than repeating a manual purchase. Planning ahead helps distinguish what needs preparing initially from a later implementation phase.

How can I get AndorPay's terms for my business?

We provide them privately after understanding your situation. Your platform, current payment setup and intended sales journeys let us prepare a proposal that explains both the terms and the work included.

Start with a clearly defined payment journey

To prepare payments for your business in Andorra, begin with the sales process you need to support. Our page on online payments and payment management explains how AndorPay connects with the banking infrastructure.

Tell us what you sell, which platform you use and what is holding you back. Request a proposal for your business, and we will review the setup with you.

WhatsApp