Andorpay
Back to the blog

Published on · Updated on

MoraBanc, Creand and Andbank: online payment setup

Prepare online payments for your Andorran business: bank requirements, virtual terminal configuration, store integration and launch with AndorPay.

Three bank models accompanied by comparison sheets.

If your business uses MoraBanc, Creand or Andbank and wants to take online payments, start with the sales journey you need: a store with orders, sales through payment links or a recurring service. Your virtual payment terminal needs to support that journey and connect to your website. A bank account or card machine at the counter does not complete the online setup.

At AndorPay, we review the infrastructure arranged with your bank, prepare the connection and check how the result reaches your store or application. This guide helps you prepare that conversation and understand each system’s role before arranging or changing your virtual terminal.

To distinguish the roles of the bank, processor and store, read how Redsys fits into online payments.

What each bank publishes about online payments

Public information helps identify services and contact routes. Your agreement needs to be defined for your company, activity and sales process. These official references provide a useful starting point.

Bank Publicly described service Starting point
MoraBanc Virtual terminal for websites or applications Review activation and subsequent integration
Creand Virtual terminal and ecommerce with MONEI Identify the contracted connection route
Andbank Virtual terminal and PayGold Separate store integration from payment requests

MoraBanc

MoraBanc describes a virtual terminal for websites and applications. Its page explains that activation is followed by ecommerce integration. Establish which methods and configuration will be enabled for your particular project.

Creand

Creand documents an ecommerce service connected to MONEI. That route has its own activation and integration steps. When assessing AndorPay, we review your infrastructure before proposing a different connection.

If you are considering that connection, the guide to MONEI in Andorra covers onboarding, subscriptions and integration checks.

Andbank

Andbank publishes information about its virtual terminal and PayGold payment requests. The relevant journey depends on whether customers buy within a store or receive a request for an agreed sale.

International customers and payments in other currencies

An international customer does not necessarily mean a payment in a foreign currency. A buyer in another country might see a price in euros; that alone establishes neither which cards your terminal accepts nor what conversion their bank may apply.

Before choosing a bank, separate three questions: which cards and countries the service supports, the currency of the charge, and the currency in which you receive settlement. If you need to display or charge in several currencies, ask the bank to confirm support for your merchant agreement and integration. A virtual terminal does not automatically include that capability.

Your private proposal should also explain who handles any conversion, the applicable terms and how refunds are treated. With those details, we can review your store connection without promising a multicurrency feature that has not been enabled.

How to choose between bank proposals

Give each bank the same sales example. “I want to sell online” leaves too much open. “I use WooCommerce, ship products and need each payment to update its order” gives you something concrete to check against the offer.

For services sold by quotation, ask who creates the payment link, how it identifies the job and where you can see that it has been paid. For a monthly membership, get explicit confirmation of recurring payment support and the connection to your application. A product page about one-off purchases does not answer that question.

Compare these four answers alongside the commercial terms you receive privately:

  • Platform fit: which connection is included, and who installs it?
  • Required payment methods: which will actually be enabled for your business?
  • Daily work: where will you check payments, settlements and refunds?
  • Support: who will help if an order remains unconfirmed?

If your existing bank covers these needs, build on that. If an essential function is missing, get a specific answer before switching. The right choice depends on how you sell and who manages it, rather than a bank being universally best.

What to arrange with your bank

A virtual terminal for your actual activity

Identify the company making the sales, its business activity and the website or channel planned. Describe what customers buy and how you deliver it. This turns a general request for a virtual terminal into a defined project.

If you already have one, gather its current configuration: available environment, connection type and contact person. Do not send secret keys through a general commercial enquiry form. An initial review can use setup information; credentials are handled later through the agreed channel.

The methods and operations you need

Cards, wallets and recurring payments require the relevant preparation. Identify which journeys are part of the business from the start. A method appearing on a bank’s website does not establish that it is enabled for your specific terminal.

With our WooCommerce plugin, cards require Redsys inSite, while Apple Pay and Google Pay require X-PAY and the corresponding setup. The plugin guide lists the requirements. This information needs to line up between the bank and the integration being prepared.

Settlement and transaction records

Purchase authorisation and the movement your team later sees at the bank are different stages of payment management. Establish where transactions can be inspected, how they relate to orders and what information will be available to the person reconciling sales.

Request the terms applicable to your agreement and retain the proposal. If there is a question about a settlement, your team needs to find the payment reference and associated order. A list of amounts without shared references makes it harder to understand what happened.

What AndorPay prepares

We connect the payment journey to your business using the infrastructure appropriate to the project. In WooCommerce, our plugin uses order lines and references. For a custom application, checkout sessions and events connect payment to its processes.

The payment lifecycle guide explains how the confirmed result relates to an order and other relevant states. A browser return guides the customer; the server-confirmed result determines what your system should apply to the purchase.

Our setup work includes reviewing that journey and its requirements. The scope is defined in a private proposal covering configuration, integration and assistance. Our virtual terminal page for Andorra explains how we approach the project.

Three common starting situations

You have a bank and a store, but need online payment

Begin with your platform and current checkout. Gather the final domain, delivery options and customisations that affect orders. Then identify with your bank what the virtual terminal needs to connect to that process.

For WooCommerce, the catalogue can remain in the store when using our plugin. The test needs to finish with a consistent order in the store’s administration. There is no reason to assume a platform migration before reviewing the setup you already have.

You have a virtual terminal and want subscriptions

Describe the payment frequency, service start and expected outcome of the first purchase. Recurrence requires specific preparation. A successful one-off transaction does not demonstrate that future renewals will work.

Define how your application responds to cancellation or failed collection as well. Our guide to subscriptions with an existing terminal develops those steps. Clear rules make it possible to prepare the integration without leaving each renewal dependent on manual administration.

You have not chosen a platform yet

Explain how you will sell and who will manage daily operations. A business selling through proposals and a store with many product references may need different starting points. First identify the simplest complete journey that supports purchase and delivery.

That lets you coordinate the platform choice with the bank connection. Building the whole website and leaving payment until the end can force earlier decisions to be revisited. Our payment methods guide helps organise journeys by type of sale.

If you are considering another bank or connection

Write down the concrete issue you want to solve. It might be a missing payment journey, excessive integration maintenance or a change in how the business operates. That requirement makes it possible to evaluate the project and its effect on existing collections.

Review outstanding orders, refunds and active subscriptions. Do not assume saved payment methods automatically transfer to another connection. Establish the process before scheduling a transition, especially where renewal dates are approaching.

Keep a record of which system owns each operation. If two connections run during the transition, assign when the old one stops being used and when the new one takes over. Sales continuity depends on that division as well as a working new payment page.

Include the team that reconciles payments

The person checking the bank account needs to recognise the references generated by the store and payment connection. Include a sample order in preparation and follow its identifiers through the records the team will use. This can expose a missing link before there are many live transactions to reconcile.

Also decide where the team records its findings when a customer asks about a payment. A shared order reference and a clear payment status are more useful than separate screenshots with no relationship between them. The process should be practical for the person doing the work each day.

Check the journey before making it public

Start in the appropriate test environment. Inspect the amount, reference, authorisation, confirmation and order status. Include the details your team needs to ship the product or deliver the service. A test should use the type of purchase your customers will actually make.

Next check a cancellation, a decline and a delayed response. The store needs to distinguish these from a confirmed payment. If the shopper closes the page, you should be able to match the result to the existing operation before asking them to try again.

Production verification is prepared according to the agreed launch scope. Credentials and enabled methods must match the published environment. Saving settings or seeing a payment button does not prove that the full purchase journey is ready for customers.

Decide who handles each type of issue

A settlement question needs banking information. An order that does not reflect a confirmed payment needs investigation of store communication. Identifying the stage where the problem appears helps gather useful details and direct the enquiry to the appropriate team.

Retain order and payment references, the date and the observed outcome. The person assisting the buyer can explain the state without asking for sensitive card details. If the screen is slow to update, inspect the existing operation before deciding the next action.

Establish the refund process too. Our documentation states that the current Redsys adapter does not support refunds through the API. The operational route needs to be agreed before it is offered to customers, rather than assuming every connection supports the same operations.

Frequently asked questions

Must I change banks to use AndorPay?

We start with your current situation. We identify the infrastructure and capabilities required by your journey before considering changes. The bank’s name alone does not define the full compatibility of a connection.

Does a physical card terminal let me sell online?

The online channel needs preparation. Explain whether customers will pay in a store checkout, through a link or by subscription so the corresponding journey can be configured.

What information should I provide first?

Your website or platform, bank, virtual terminal situation and a description of what you sell. If some decisions are still open, say so. The sales journey helps determine the next steps without requiring you to choose every technical component beforehand.

Prepare your virtual terminal around the whole sale

Tell us which bank you use and how you want to collect payment. We will review the connection, store and follow-up process to prepare a proposal with a clear scope.

Request a proposal for your virtual terminal with AndorPay. You will receive the terms privately, together with the steps needed to get the payment journey running.

WhatsApp