Acquirer

An acquirer sits on the merchant side of a card transaction. The issuer sits on the cardholder side. The merchant may see the acquirer's name in its agreement, or may contract with a PSP that provides acquiring access behind one integration. Visa Acceptance Solutions' role guide distinguishes the merchant financial institution from the issuer; the exact merchant relationship depends on the provider model and contract.

What the acquirer does

When a card payment is submitted, the acquiring side sends an authorization request toward the issuer through the card network. The issuer returns an approval or decline. Clearing, settlement and the merchant payout follow separate steps. The card network role does not tell you which company will pay the merchant on a particular date or send the reconciliation file; read the merchant agreement and payout terms.

The acquirer is accountable to the scheme for merchants it accepts. The merchant's own exposure to fraud losses, disputes, reserves and security obligations depends on the agreement and applicable rules. A gateway can transmit transaction data without becoming the acquirer or holding the payout obligation.

A practical contract check

Suppose a merchant uses one PSP API and its payout is delayed. The API provider might be a bundled PSP, while a separate licensed acquirer sits behind it. Ask three questions before escalating: Who is named as the merchant's contracting party? Who issues the payout and settlement report? Which party receives the first dispute or reserve query? Start with the contracted provider unless your agreement assigns a direct escalation path. This is an operator triage example, not a rule that every PSP has the same structure.

For the full contracts, custody, liability and escalation map, see Issuer vs Acquirer vs Gateway vs PSP. For the cost flowing from the acquiring side to the issuer, see interchange.