MONEI is available to Andorran businesses through its documented onboarding route with Creand Crèdit Andorrà. It also offers subscription functionality. If you are deciding how to take payments through an Andorran company, the useful comparison concerns your bank connection, your store and the way you manage sales.
At AndorPay, we help prepare that complete journey: the first purchase, order confirmation and subscription management where your business needs it. This guide explains what to examine when researching MONEI in Andorra and how to plan an integration around your operation.
What MONEI availability in Andorra means
MONEI’s country-specific onboarding documentation places the Andorran route with Creand and its virtual payment terminal. If you use another bank, do not assume the same process applies. Establish the relevant connection before building the store around a particular configuration.
Commercial eligibility and technical integration answer different questions. The first establishes whether your actual business can subscribe to the service. The second determines how a payment reaches the tools used to manage sales. Launch requires both parts to line up.
Opening an account does not demonstrate that an order updates correctly after payment. Installing a plugin does not prove that the necessary banking configuration is enabled. Your merchant setup and store connection need to refer to the same working journey.
MONEI also provides subscription functionality
Its subscription documentation covers recurring payments and subscription management. The useful question is how the available functions connect to your service rules and the integration configured for your account.
Your business still needs to decide what customers buy, when a service period starts, how cancellation works and what happens to access after a failed renewal. Software can carry out operations, but the commercial conditions need to be defined by the business providing the service.
Use a concrete sale when evaluating the setup. “We need subscriptions” leaves too much open. “We sell monthly access, activate it after payment and keep an individual renewal date for each customer” gives you something specific to configure and test.
Payment, recurring management and access are different states
A payment records the outcome of an operation. Recurring management organises periods, renewals and changes over time. Access determines what a customer can use inside your service. These states need to be connected, but they describe different parts of the relationship.
An outstanding renewal might trigger a message without immediately removing access. A cancellation might stop future renewals while preserving the period already purchased. Your configuration should follow the conditions you offer, and customer messages should explain what will actually happen.
| Situation | Payment information needed | Business decision |
|---|---|---|
| First purchase | Confirmed, pending or unsuccessful | When to deliver or activate |
| Renewal | Outcome of the new operation | Service continuity and communication |
| Plan change | Status and timing of the change | Features available to the customer |
| Cancellation | Subscription status | Service end and next steps |
This distinction also helps stores without subscriptions. Collecting payment, preparing an order and delivering it are separate stages. Linking them prevents a bank confirmation from being mistaken for completion of the entire sale.
What we prepare with AndorPay
We connect payment to your activity in Andorra and the way you sell. For WooCommerce, our plugin uses order information and presents available payment methods. For a custom application, the API lets you create a checkout session and receive events to continue processing the purchase.
The confirmed result is associated with the order and, where applicable, the subscription. Our payment lifecycle documentation explains that journey and the distinction between a browser return page and the state confirmed by the server.
Recurring payments require the subscription capability and a connection prepared for recurrence. Our API reference documents cancellation and plan-change operations. We define the scope of your proposal using the available capabilities and the requirements of your application.
If you run a WooCommerce store
Your products and order calculations stay in WooCommerce. The plugin sends the lines and references needed to prepare payment. You do not have to recreate that catalogue in AndorPay for this connection.
The check needs to cover the order, delivery information and status used by your team. If you have customised checkout or connected a separate fulfilment system, include those steps. The business outcome is being able to handle the purchase through the tools your team already uses.
If you sell a digital service
Your application needs to associate the payment session with the right customer and product. After receiving a confirmed result, it applies the corresponding access rule. That separates a completed purchase from an attempt still waiting for an outcome.
For subscriptions, add renewals and later changes to the journey. Our guide to subscriptions with your virtual terminal develops those steps. Do not activate a service solely because the customer’s browser arrived at a success address.
Evaluate the fit using a representative sale
Write down a normal sale for your business. It could be a product requiring delivery, an identified professional engagement or signup for a monthly membership. Include the information available to the customer and the details your team needs to provide the service.
Then walk through four stages: preparing the purchase, authorisation, confirmation and delivery or activation. At each stage, identify who supplies information and which system stores it. This exposes what the integration handles and what remains the responsibility of your own application.
Include a relevant exception in the demonstration. A decline needs to be explained without being confused with a confirmed payment. A delayed screen update needs a way to inspect the existing operation. These examples say more about practical fit than a row of payment logos.
Make support part of the example
Ask the person who answers customer queries to follow the same reference through the order and payment records. They should be able to distinguish “still waiting for confirmation” from “paid and awaiting fulfilment” without asking the customer to repeat payment.
For a membership, have them identify the next renewal and the service period already purchased. This simple check reveals whether the integration supplies useful operational information, rather than only producing a successful checkout screen for the developer.
If you already use MONEI and are reviewing your setup
Start by naming the improvement you need: another store, a custom application, a recurring offer or less manual work when incidents happen. That requirement should justify the integration project and explain what will change for the team running it.
List the current components: platform, order references, active subscriptions, notifications and manual tasks. You do not need to share card data for this review. You need to understand which information identifies a customer, a sale and a renewal.
For subscriptions, do not assume saved payment methods can be transferred between connections. Portability depends on the systems and agreements involved. Plan the transition using the confirmed process for your situation, including fresh customer authorisation where necessary.
Prevent two systems collecting the same renewal
Before a transition, assign each subscription to the system responsible for it and define the effective date. The old and new systems must not schedule the same service period independently. A list of transferred customers is not enough if the previous collection jobs remain active.
Keep a mapping between the former reference, the new reference and the next collection date. It helps answer customer questions and verify the calendar. Agree the sequence before changing the live operation so the first renewal does not depend on improvised decisions.
What an integration test should establish
The first successful payment is only part of the check. The purchase reference must remain intact, the final status must reach the store and a repeated notification must not cause another delivery. If the buyer closes the page, the operation should still be traceable by its reference.
For a subscription, include a renewal, a payment problem and a cancellation. Inspect what the team sees and what the customer receives in each case. Your application state should follow the service conditions, rather than an assumption based on the last browser message.
Our testing guide covers validation scenarios, while the webhook documentation explains notification handling. Use the appropriate environment and distinguish those checks from a real operation in production.
Clarify the boundaries before launch
Payment collection and tax services cover different responsibilities. Charging a subscription does not establish that every tax obligation associated with your activity has been handled. Where other services are needed, define their scope within your business process.
Some operations also depend on the connection even when their name appears in an API reference. Our documentation states that the current Redsys adapter does not support refunds through this API. The refund process therefore needs to be agreed before it is promised to shoppers.
Commercial terms are provided through a private proposal. To prepare it, we need your platform, bank, virtual terminal situation and sales journey. Those details let us define a specific connection and the responsibilities belonging to each part of the process.
Frequently asked questions
Can an Andorran business use MONEI?
Yes. Its official documentation describes onboarding in Andorra. Review the route that applies to your banking situation. Connecting the store remains another part of getting the payment journey ready.
Does selling subscriptions mean I need another tool?
Recurrence alone does not establish that need. Define the service lifecycle and check how the selected connection handles it. Additional software should address a specific operational requirement rather than duplicate work already covered.
Can we assess AndorPay before changing our store?
We can start with the platform you already use and the journey you need. The proposal should identify what can be reused, what needs configuration and what requires integration before a migration is considered.
Prepare a connection built around your sales
Tell us what you sell and what needs to happen after payment. We will review your store or application, the banking connection and recurring management if it forms part of the project.
Explore our virtual payment terminal solution for Andorra and request an integration proposal. We will provide the scope and terms privately.
