Acquirer and issuer in payments — how the four-party model works, and where BazPay sits.
Every card transaction moves through four parties: the cardholder, the issuer (the cardholder's bank), the card scheme and the acquirer (the merchant's bank or licensed processor). BazPay is a direct regional acquirer for its merchant book — and explicitly not an issuer. This page explains the roles and how they connect on your transactions.
Written for merchants, product teams and finance staff evaluating the acquirer choice and needing to understand where responsibility sits during authorisation, settlement and chargebacks.
Why the acquirer/issuer distinction matters to a merchant
Blurring the acquirer and issuer roles is where most payments confusion starts — it hides where fees come from, who owns which risk, and who to talk to when a dispute lands. Four properties keep the model concrete on BazPay.
-
Clear boundaries between acquirer and issuer
The acquirer sits on the merchant's side of the transaction; the issuer sits on the cardholder's. BazPay is the acquirer for its regional book and never plays the issuer role — that clarity keeps compliance conversations short and integration decisions accurate.
-
One direct regional acquiring contract
You contract with BazPay directly. No reseller sitting between you and the scheme, no aggregated MID borrowed from another entity. The acquirer of record on every authorisation is BazPay under its regional acquiring licence.
-
Chargeback attribution stays with your MID
Dispute events initiated by the cardholder's issuer come back to a named MID belonging to your entity. Attribution is clean; ratios do not get diluted across a shared MID pool.
-
The scheme handles issuer routing, not you
Once the acquirer posts an authorisation to the scheme, the scheme routes it to the correct issuer worldwide. You never have to know which issuer authorised a specific charge — the network handles that, and BazPay surfaces the response.
The four roles in every card payment
The classic \"four-party model\" underpins every scheme-based card transaction. Below is who does what — and where BazPay sits.
-
Cardholder
Cardholder — the shopper
The person or business paying with a card. Their card was issued by their bank (the issuer). BazPay does not have a direct relationship with the cardholder — the merchant does.
- Payer
- Consumer or B2B buyer
-
Issuer
Issuer — the cardholder's bank
The bank or fintech that issued the card and holds the cardholder's funds or credit line. The issuer authorises or declines each transaction and initiates chargebacks on behalf of the cardholder. BazPay is not an issuer.
- Issues cards
- Authorises payments
- Initiates chargebacks
-
Scheme
Scheme — the card network
Visa, Mastercard, American Express or Cartes Bancaires. The scheme owns the rulebooks, routes authorisation requests between acquirer and issuer, and defines the clearing and settlement calendar.
- Visa
- Mastercard
- Cartes Bancaires
- eftpos
-
Acquirer + Merchant
Acquirer and merchant — BazPay and you
The acquirer holds scheme membership on the merchant's side and settles the merchant. BazPay is that direct regional acquirer for your business. You are the merchant of record for every charge processed under your MID.
- BazPay = acquirer
- Your entity = merchant
BazPay's acquirer role in depth on merchant acquiring. The processor angle on payment processors. The scheme layer on payment network gateway.
How an issuer and acquirer transaction flows
Six stages describe the round-trip from the shopper hitting pay to the merchant receiving settlement. The acquirer talks only to the scheme; the scheme talks to the issuer.
-
Shopper pays
The cardholder enters or presents card details at your checkout. Data is collected inside our PCI environment via hosted fields.
-
Acquirer posts
BazPay, as the acquirer, formats an authorisation message with authentication result attached and posts it to the card scheme.
-
Scheme routes
The scheme identifies the issuer from the BIN and routes the message to the correct issuing bank anywhere in the world.
-
Issuer decides
The issuer authorises or declines based on the cardholder's account, its own risk models and the 3-D Secure outcome, then sends the response back through the scheme.
-
Acquirer confirms
BazPay receives the response, returns a canonical charge object to your system and fires a signed webhook — authorised or declined.
-
Settle
Once the scheme cycle clears, funds move from the issuer through the scheme to BazPay, which settles into your local settlement account with interchange++ line detail.
Acquirer vs issuer at a glance
The two roles look symmetric from the network's perspective, but they have very different jobs and very different exposures. The comparison below lays out the split so the merchant conversation stays clear.
| Dimension | Acquirer (BazPay for merchants across the EU, UK, Australia, Canada and New Zealand) | Issuer (external cardholder bank) |
|---|---|---|
| Whose side? | Merchant side (BazPay) | Cardholder side (external bank) |
| What they do | Authorise, settle, report to the merchant | Issue cards, authorise on the cardholder's account |
| Chargeback role | Represents the merchant in the dispute | Raises the chargeback on the cardholder's behalf |
| Fees carried | Acquirer margin + scheme fees + interchange | Interchange (paid by the acquirer, passed through) |
| Scheme membership | Direct member on merchant side | Direct member on issuing side |
| Merchant contract | Direct with BazPay | None — no relationship with the merchant |
Rate structure on the pricing page. The bank-rail layer on Single Euro Payments Area processing.
Features on the acquirer side that the merchant actually uses
Every capability below sits on the acquirer's side of the four-party model. The issuer side belongs to the cardholder's bank; the acquirer side belongs to BazPay and, by extension, to your merchant integration.
-
Direct scheme membership
BazPay holds acquiring membership with Visa, Mastercard, Cartes Bancaires and eftpos on its regional licence. No downstream reseller in the acquirer chain.
-
Named MID per merchant
Your merchant identifier at each scheme is issued to your legal entity, so issuer-side chargeback attribution comes back cleanly to you.
-
3-D Secure 2.2 with exemptions
Authentication runs on the shopper's side (with the issuer) via 3DS 2.2; exemption logic keeps most authorisations frictionless.
-
Real-time issuer response
The raw issuer response, decline reason code and scheme normalisation land on the charge object and in real-time analytics within seconds.
-
Signed webhooks
Authorisation, capture, refund and dispute events all fire as HMAC-signed, replay-protected webhooks so acquirer-side events reach your ledger reliably.
-
Interchange++ reporting
Interchange (paid to the issuer), scheme fees and BazPay acquirer margin appear as separate lines on every settled transaction.
-
Dispute defence tooling
Issuer-initiated chargebacks fire a signed webhook; evidence packets pre-assemble the 3-D Secure result, delivery data and metadata for one-click submission.
-
Instant payouts to your settlement account
Settlement from the acquirer to the merchant happens through SEPA Instant (and SEPA Instant on approved corridors) into your named local settlement account.
The acquirer response, from the merchant's API
When BazPay (as the acquirer) receives the issuer's response, it lands on the charge
object and fires a signed webhook. The network field identifies the
scheme; the issuer_country field surfaces where the card was issued;
authorization_code and any decline reason come from the issuer.
{
"id": "ch_5F9k",
"amount": 4990,
"currency": "EUR",
"status": "succeeded",
"network": "visa",
"issuer_country": "DE",
"authorization_code": "023751",
"three_d_secure": { "outcome": "authenticated" }
}The response is the acquirer's canonical view of what the issuer decided. The full schema lives in the API reference; handler samples in the developer docs.
Where the acquirer role earns its keep for the merchant
The four merchant profiles below already operate under BazPay's direct acquirer relationship. Each depends on clean issuer-side attribution for chargebacks and issuer-response transparency for approval quality.
-
E-commerce sellers
DTC brands whose shoppers hold cards issued by dozens of banks. The acquirer handles the whole scheme + issuer round-trip; the storefront just calls the API.
-
Subscription software
SaaS teams whose renewals depend on issuer decisioning. Network tokens keep card-on-file charges alive across issuer-side card reissues.
-
Professional services
Consultancies invoicing higher-ticket buyers with clean per-MID reporting for finance — no shared-MID ambiguity when the issuer's dispute lands.
-
Digital publishers
Membership and paywall businesses accepting issuer-scored subscriptions with 3-D Secure exemption logic and dunning-aware retries after issuer declines.
Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. BazPay is not a merchant of record, not a marketplace of third-party PSPs and not a card-issuing bank.
Security and compliance on the acquirer side
The acquirer environment runs inside a PCI DSS Level 1 assessment renewed each year. Hosted fields and gateway-side vaulting keep your annual return at merchant SAQ A. Authentication is a shared responsibility with the issuer, coordinated via 3-D Secure 2.2 and automatic exemption logic on the acquirer side.
- PCI DSS Level 1
- Annual assessment on the acquiring and gateway environment
- Merchant SAQ A
- Hosted fields and gateway vault keep card data out of your stack
- Authentication
- 3-D Secure 2.2 with automatic exemption logic between acquirer and issuer
- GDPR
- In-region data residency; DPA on request
- Scheme registrations
- Visa VIRP and Mastercard SPoC/PCI-CP where required
Questions about acquirer and issuer in payments
What is the difference between an acquirer and an issuer in payments?
The acquirer sits on the merchant side of a card transaction — it holds scheme membership on behalf of the merchant, formats the authorisation, and settles the merchant. The issuer sits on the cardholder side — it issued the card, holds the cardholder's funds or credit line, and authorises or declines each transaction. The two never talk directly; the card scheme routes the messages between them.
Is BazPay an acquirer, an issuer, or both?
BazPay is a direct regional acquirer for its merchant book. BazPay is not an issuer — it does not issue cards to consumers or businesses, does not operate a consumer wallet and does not hold cardholder deposits. Every reference on this site to "acquirer" refers to BazPay; issuers are always external banks or fintechs.
How does an issuer and acquirer transaction actually work step by step?
A shopper enters card details at the merchant's checkout. The acquirer (BazPay) formats the authorisation with the authentication result attached and posts it to the card scheme. The scheme identifies the issuer from the BIN and routes the request to that issuing bank. The issuer authorises or declines based on the cardholder's account, its own risk models and the 3-D Secure outcome, then returns a response through the scheme back to the acquirer. The acquirer confirms to the merchant. Later, settlement flows from the issuer through the scheme to the acquirer, and the acquirer settles the merchant.
Who holds the chargeback risk between the acquirer and issuer?
The issuer initiates a chargeback on the cardholder's behalf, but the acquirer represents the merchant during the dispute. The merchant's funds are provisionally debited when the chargeback lands; the merchant (through the acquirer) can submit evidence to defend the case. If the acquirer or merchant loses, the loss stays with the merchant. That is why BazPay attaches 3-D Secure results, delivery data and charge metadata to the case packet automatically.
Does BazPay work with any specific issuer or issuer bank?
No — an acquirer does not choose or partner with individual issuers. Once BazPay posts an authorisation to the scheme, the scheme routes it to whichever bank issued that particular card, anywhere in the world. The acquirer's job is to reach every issuer via the scheme; the issuer relationships belong to the cardholders, not the merchant.
What does "acquirer issuer merchant" refer to, and where does the scheme fit?
"Acquirer issuer merchant" is a shorthand for the three commercial roles that touch a card transaction on the money side. The full model is actually four-party: cardholder, issuer, scheme and acquirer (with the merchant on the acquirer side). The scheme (Visa, Mastercard, Cartes Bancaires, eftpos) is the routing and rulebook layer that makes the acquirer and issuer able to transact without a direct contract.
How do acquirer and issuer processing fees end up on my statement?
Interchange is set by the scheme and paid to the issuer; scheme fees are charged by Visa or Mastercard on both sides of the transaction; the acquirer's margin is what BazPay charges for its own service. On BazPay's interchange++ statement all three components appear as separate lines on every settled transaction, so you can see exactly how much reached the issuer, the scheme and the acquirer.
Can BazPay board merchants that need issuer-side services or embedded finance?
No. BazPay's underwriting is scoped to merchants across the EU, UK, Australia, Canada and New Zealand that need acquiring, gateway, fraud, recurring billing and payouts. Issuer-side services — issuing branded cards, running a consumer wallet, holding customer funds — are outside scope. BazPay is also not a merchant of record and not a marketplace of third-party PSPs.
Sign with a direct regional acquirer for your merchant traffic
Share your business model and monthly volume. A named engineer will confirm boarding fit and map the acquirer-side integration inside one working day. See also merchant acquiring, payment processors, payment fraud prevention and about NEWERA PAYMENT TECHNOLOGIES LTD.