Acquirer, gateway, payment facilitator: who does what in a card payment

What does a payment gateway do

The gateway is the connection. It takes the transaction from wherever it happens, a card terminal, an online checkout, a booking page, and passes it securely to the acquirer for authorisation.

Its job is transport and formatting. It encrypts the card data, routes the transaction, returns the approval or decline, and usually handles tokenisation so that card details can be stored for repeat payments without the business holding them.

A gateway does not hold money. It does not decide whether a payment is approved. It does not settle anything. When a payment fails at the gateway level, it usually means a connectivity or configuration problem rather than a problem with the card.

What does an acquirer do

The acquirer is the regulated institution that processes the transaction and holds membership of the card schemes. It is often called the acquiring bank, though not every acquirer is a bank.

The acquirer routes the authorisation request to the customer's issuing bank, applies fraud checks, and receives the approval or decline. At the end of each trading day it collects the funds from the issuing banks through the schemes.

The acquirer is also where disputes originate. When a cardholder challenges a transaction with their bank, the chargeback comes back through the schemes to the acquirer, which passes it on with a deadline attached.

What does a payment facilitator do

A payment facilitator sits between the acquirer and a large number of businesses. Rather than each business holding its own direct arrangement with an acquirer, the facilitator holds that arrangement and brings businesses in underneath it.

That structure changes who does the work:

• Onboarding and KYB. The facilitator collects and verifies the business details, ownership information and bank verification that an acquirer needs, and passes the verified file across to open the merchant account.
• Settlement. The facilitator receives funds from the acquirer, reconciles them against the transaction records, and pays each business individually.
• Disputes. The facilitator receives chargebacks from the acquirer, passes them on for evidence, and submits the response.
• Compliance. The facilitator carries the regulatory authorisation, the safeguarding obligations, and the card scheme compliance requirements.

A payment facilitator is not a processor. The acquirer processes. The facilitator handles the start and the end of the cycle and everything administrative in between.

The division of labour

• Carries the transaction: gateway only.
• Authorises the payment: neither the gateway nor the facilitator. The acquirer routes it to the issuing bank, which decides.
• Holds card scheme membership: the acquirer. The facilitator operates under the acquirer's membership.
• Onboards the business: the facilitator, or the acquirer where the merchant is direct.
• Pays the business: the facilitator, or the acquirer where the merchant is direct.
• Receives the chargeback: the acquirer first, then the facilitator.
• Holds the regulatory authorisation: the acquirer and the facilitator. It varies for gateways.
• Holds the customer relationship: usually the software platform, sometimes the acquirer.

Why the distinction matters to a software platform

Three practical reasons.

It determines what the platform has to build. A gateway integration is a technical piece of work. A facilitator arrangement involves onboarding flows, merchant status, settlement reporting and dispute handling appearing inside the product. The second is a larger commitment and a different kind of commitment.

It determines where liability sits. Under a facilitator model, the facilitator is the regulated party and carries the safeguarding and compliance obligations. A platform that goes direct to an acquirer, or takes on its own authorisation, is taking on those obligations itself. That is a legitimate choice and some platforms make it deliberately. It is a poor choice to make by accident.

It determines who the merchant calls. This is the one platforms tend to underestimate. When a merchant cannot reconcile a settlement, or a payment has not arrived, or a chargeback needs evidence, they call whoever sold them the software. Understanding which of these three parties can actually resolve each type of problem is the difference between a support queue that works and one that does not.

Who to call when something goes wrong

• Terminal or checkout will not connect: the gateway, or connectivity.
• Individual card declined: the issuing bank, via the acquirer.
• Repeated declines across many cards: the acquirer, or configuration.
• Merchant account not opening: onboarding, with the facilitator.
• Settlement has not arrived: the facilitator.
• Settlement does not match the till: reconciliation, using the facilitator's reporting.
• Chargeback received: the facilitator, with evidence from the merchant.
• Question about the business's own figures: the software platform that holds the relationship.

Frequently asked questions

Is a payment facilitator the same as a payment processor? No. Processing is what the acquirer does: routing transactions, applying fraud checks, communicating with the card schemes. A facilitator handles onboarding, settlement, disputes and compliance around that processing.

Can a business be both a gateway and a facilitator? Some companies offer both. That does not merge the functions, it means one supplier is providing two of them. The distinction still matters when diagnosing a problem.

Does a merchant need its own acquirer relationship? Not under a facilitator model. The facilitator holds the acquiring arrangement and the merchant operates under it, with its own merchant account identifier so that its transactions and settlements remain separate.

Who is responsible if a chargeback is lost? The financial liability sits with the merchant, because the merchant took the transaction. The facilitator manages the process and the deadlines. The evidence has to come from the merchant, because only the merchant has it.

What is a tri-party agreement? An arrangement signed between the merchant, the payment facilitator and the acquirer, setting out the responsibilities of each. It is what allows the merchant to trade under the facilitator's acquiring arrangement while remaining an identifiable party in its own right.

Understanding which party does what is usually the difference between a payments partnership that runs quietly and one that generates support load nobody planned for.

VestaOne works as the payment facilitator behind software platforms across education, hospitality, retail, catering and sport, handling onboarding, settlement, disputes and compliance so the platform keeps the merchant relationship and the product roadmap.

VestaOne is a trading brand of Vesta Merchant Services Limited, registered in England and Wales, company number 07108015. Vesta Merchant Services Limited is authorised by the Financial Conduct Authority as a payment institution, firm reference number 784165. Part of Vesta Software Group.

This article is provided for general information only. It is not financial, legal or regulatory advice, and it does not take account of any particular business's circumstances.