A buyer clicks “Pay”, sees confirmation and assumes the money has reached the seller. In practice, transaction confirmation, interbank settlementSettlement is the transfer of funds from a PSP, acquirer, EMI or payment processor to the operator’s settlement account. and revenue becoming available in a company’s account can be different events. The company displaying the payment form is not necessarily a bank or the organisation directly holding the money.
To understand payment acceptance costs and risks, separate five layers: contracts between buyer, seller and payment suppliers; the checkout interface; payment messaging; accounts and obligations; final inter-institution settlement and the separate payout of sales proceeds to the seller. Different companies, or one company with several functions, may serve these layers. “Payment service providerPSP means Payment Service Provider. A PSP helps an operator accept deposits, process payments, settle funds, manage refund logic, chargebacks and reserves and, in some models, handle payout flows.” (PSP) covers a broad range of suppliers in commercial usage; there is no single worldwide “PSP licence”. [2][3][4]
From bank cards to gateways and instant transfers
Cashless settlement predates modern mobile apps. Individual merchants issued cards before international bank networks developed. Bank of America launched BankAmericard in 1958; licensing to other banks began in 1966, the card organisation was separated in 1970 and adopted the Visa name in 1976. Mastercard’s predecessor, the Interbank consortium, was founded in 1966. A different cashless route developed alongside cards: the US Federal Reserve began operating automated clearing house infrastructure, ACH, in 1972. [1]
As merchants accepted cards from different banks, messaging and interbank settlement became necessary. E-commerce later increased demand for secure payment forms, gateways, remote acquiring and platforms connecting several payment methods through one software integration. There is no single date when the “PSP was invented”: banking services, processing and technology intermediaries developed separately.
During the 2010–2020s, massSingapore’s monetary and financial regulator, including for the relevant payment institutions.-market mobile wallets, QR payments and national instant account-transfer systems joined cards. The modern market is therefore not a pyramid of “Visa → bank → PSP → seller”. Cards and bank transfers are different, sometimes overlapping routes. [1][11][13][14][15][16]
Who participates and whom they serve
The buyer contracts with a bank, payment-instrument issuer or wallet providerA wallet provider supplies a wallet or a service for holding and processing funds, particularly in crypto-casino and Web3 structures.. The seller, also called the merchantA business or entrepreneur accepting payment for its goods or services., has a sales contract with the buyer and a separate payment-acceptance agreement. The payment brand at checkout does not necessarily identify the seller’s legal entity or the payment-processing contracting party.
An issuer issues the card or services the buyer’s relevant payment instrument. An acquirerAn acquirer is the bank or payment institution that enables a merchant to accept card payments. arranges the seller’s acceptance of card transactions under the card scheme’s rules. In a typical four-party model, Visa and Mastercard provide the rules and infrastructure for issuer–acquirer interaction; they are not themselves the buyer’s bank and need not maintain the seller’s bank account. These distinct roles are described, for example, in Article 2 of EU Regulation 2015/751. [2]
A processing platform processes and routes messages, while a payment gatewayTechnology that carries payment requests and connects providers. The gateway label alone does not determine the company’s regulated functions. provides the technical interface carrying requests from a website or app. An acquirer, merchant or another PSP may purchase these services. Handling payment data does not automatically confer the right to hold customer funds or provide a regulated payment service. [4][19]
A payment facilitatorA provider arranging merchant service through a sponsoring acquirer. It is an infrastructure role, not a universal state authorisation., or PayFac, onboards merchants called submerchants under a model agreed with the acquirer and the relevant card scheme. Mastercard describes registration of such intermediaries through the acquirer. An aggregatorAn aggregator is a B2B supplier that combines games, payments, data feeds, KYC tools or other services from multiple providers into a single integration. may combine methods and customers; an orchestrator may technically select routes between providers. These labels do not replace checking the company’s actual functions and the authorisation required in the country concerned. [10]
Banks maintain accounts and obligations to account holders. Central banks may provide settlement infrastructure and accounts for payment-system participants; commercial banks may settle directly or through correspondent relationships. A clearing system determines mutual obligations; a settlement system executes them under its rules. SWIFT is often used internationally for standardised messages between financial institutions: it is not one global bank holding all the money being transferred. [3][8][18]
Payment institutions and electronic moneyMonetary value issued electronically in exchange for funds and used for payments under the relevant regime. It is not synonymous with a bank deposit or crypto-asset. institutions form another category. European law, for example, regulates them as organisation types with defined service permissions; not every mobile “wallet” is automatically a bank or EMIEMI means Electronic Money Institution. An EMI may open accounts, issue electronic money and provide payment services within the scope of its authorisation.. One legal entity may combine functions only within applicable rules. [4][5]
A card payment: messages, settlement and the seller’s money
Consider an illustrative online purchase. The buyer enters a card or confirms with a stored payment instrument. The shop sends a request through a gateway or processor to the acquirer, then through the card network to the issuer. The issuer checks the transaction and returns a decision. Not every route uses separate gateway and processing companies: this is a functional model. [2][19]
Message flow:
Buyer → website checkout or PSP-hosted form → gateway/processing, if separate → acquirer → relevant card network → issuer; the authorisation response returns through the agreed route.
Flow of monetary obligations and payout:
Card-transaction obligations → clearing and participants’ settlement positions → discharge of those positions under system rules → recognition of the amount owed to the seller → contractual payout. This is a simplified functional model; fund availability and inter-institution settlement depend on the arrangement.
Distinguish the stages. Authorisation is the required approval decision, not proof that sales proceeds have arrived. Capture at the seller’s request, subsequent submission for clearing, clearing, settlement between participants and payout to the seller are related stages, not one event. Their sequence and technical combination depend on the payment model. Interface confirmation does not equal money available in the company’s bank account. [3][9][19]
Square’s US model illustrates this. Under its US Payment Terms effective for sellers from 30 July 2026, the payment-services parties are Block, Inc. and Square Capital, LLC. Section 1 identifies Square as a payment facilitator working with card networks, processors and acquiring banks for these services, rather than acting as a bank. Section 2 appoints Square the seller’s agent for receiving, holding and transferring funds and defines how receipt affects the buyer’s obligation to the seller. Sections 10–15 address access to proceeds, payout initiation, restrictions, transaction records, reserves and pooled bank accounts for seller balances. Initiating a payout does not mean simultaneous credit to the seller’s bank account. This concerns specific US seller payment services, not the entire group or other countries. Section 3 treats betting, including the listed gambling activities, as unsupported. Square illustrates a contract model here; it is not proposed for accepting gambling payments. [9]
Three fundamentally different actions may follow payment. A refund is initiated by the seller or made under applicable rules. A chargebackA chargeback is a card transaction disputed by the player through the player’s bank or card issuer. follows card-network procedures and participants’ rights. Recalling or requesting the reversal of an executed bank transfer depends on that system and does not automatically become a card chargeback. Look for loss-allocation rules in the instrument’s rules and signed contract, not the “payment successful” label. [9][16]
Bank transfers, QR codes and wallets: another route
In an account-to-account transfer (A2A), the payer instructs their bank or another permitted payment account. The recipient may be identified by account number, telephone, special address or QR code. A QR code communicates payment details or initiates a request; it does not independently prove who holds the money.
Message flow:
Mobile app → servicing bank or PSP → national payment infrastructure and participants → recipient’s bank/PSP → result notification.
Funds flow:
Payer’s account → settlement of obligations between participating institutions under system rules → recipient’s account. A merchant aggregator may introduce additional internal accounting and a separate merchant payout. This is functional: crediting, notification and final settlement follow the particular system’s rules.
Visa or Mastercard need not participate in this model. Notification speed, final interbank settlement and end-merchant availability still require separate checks. A bank may credit the account directly; an intermediary may first display an internal balance and later pay the merchant. [3][14][15][16]
Person-to-person transfers (P2P) are a normal permitted use case in many systems. A company paying for goods or services through A2A does not thereby make it P2P. “P2C” is sometimes used for an individual paying a company, but is not a uniform worldwide licensing category. Nor does every QR payment use an individual’s personal account. Thailand’s PromptPay supports commercial use cases, while Argentina’s Transferencias 3.0 specifically describes QR payments for goods and services at merchants. [11][16]
Differences across Europe, Asia and Latin America
The common principles are identifying the participant, account, contract and settlement system. Actual schemes and access regimes differ significantly. None of these examples represents an entire region.
EU and European Economic Area. PSD2 is established by Directive (EU) 2015/2366 and national implementation; the directive is also incorporated into the EEA Agreement. Regulated payment services and particular technical functions differ; Article 3(j)’s purely technical service exclusion is not a universal exemption for every business with an API. Payment institutions and EMIsEMI means Electronic Money Institution. An EMI may open accounts, issue electronic money and provide payment services within the scope of its authorisation. have different permitted operations. The national regulator and actual authorisation scope matter more than the PSP label. Euro transfers under Single Euro Payments Area (SEPA) schemes, including instant transfers, coexist with cards. Regulation (EU) 2024/886 introduces EU instant euro credit-transfer obligations in stages, with different deadlines for euro-area countries, other EU states and some provider categories. [4][5][6]
United Kingdom. FCAThe UK financial-conduct regulator, which considers relevant payment and e-money institution applications. payment-institution and e-money rules form a separate regime; UK authorisation does not automatically equal EEA authorisation, or vice versa. The Bank of England describes distinct interbank payment and settlement infrastructure, including CHAPS. [7][8]
India. UPI supports transfers and merchant purchases through connected apps and participants. NPCI’s official material describes merchant QR payments and participating banks and payment partners; certain use cases support payments from a credit account. Do not mechanically equate the servicing bank, app and recipient with card acquiring. Aggregator categories and access conditions need assessment under current RBI and UPI rules; a QR code or app does not determine a participant’s licensing status. [20]
Thailand. The Bank of Thailand states that PromptPay has operated since 2016, including recipient identifiers instead of manually entered account details. It supports commercial use cases; Thai QR enables QR payment methods. The Payment Systems Act separately regulates specified payment services, including e-money and accepting electronic payments for others. [11][12]
Singapore. FAST provides fast Singapore-dollar transfers between participants. PayNow uses identifiers including telephone numbers and organisations’ Unique Entity Numbers (UEN). The Payment Services Act 2019 takes a functional, risk-based approach: the way a wallet is displayed does not establish its operator’s licence. [13]
Brazil. Pix is for purchases of goods and services as well as transfers between people. The Central Bank of Brazil describes different Pix participant types, while its Instant Payment System (SPI) provides inter-institution settlement under its own rules. Companies displaying Pix do not all share direct settlement-participant status. [14]
Mexico. Banco de México operates the SPEI interbank electronic payment system, which settles between participants, including customer instructions. SPEI’s existence does not explain who contracted with a particular merchant or which activities a bank will accept. [15]
Argentina. Transferencias 3.0 describes specific “payments by transfer” for goods and services through QR, involving an organisation enabling merchant acceptance. The official PSP register distinguishes payment-account provision, acceptance, QR administration, acquiring and aggregation. This illustrates why A2A shopping payments cannot be reduced to “transfers to an individual”. [16][17]
A local transfer system does not establish that a foreign business may sell any product to residents. In particular, gambling authorisation, the lawfulness of offering services in a target market and a bank’s or PSP’s agreement to serve the business are three separate questions.
What a business buys from a PSP and how pricing works
A provider may sell more than payment acceptance. Depending on the model, services include merchant and ownership verification (KYBKYC means Know Your Customer: the verification of a customer or player. KYB means Know Your Business: the verification of a legal entity, such as a B2B partner, PSP, platform supplier or affiliate network.), website onboarding and integration, checkout, cards and local transfers, secure data processing, fraud controls, acquirer routing, refunds and disputes, reconciliation, reporting, payouts, currency conversion and technical support. A PSP need not perform everything itself: a bank, processor or other partner may provide some services. [9][19]
The seller’s total price can also have several components. For cards, distinguish interchange, scheme fees, and acquirer and technical-service remuneration. A blended transaction fee may already include some of them, or the tariff may be itemised. Setup, failed attempts, refunds, disputes, bank payouts, cross-border transactions and foreign exchange (FX) may incur separate fees. Adding component names together does not produce a universal rate. [2][9]
Three contractual terms deserve attention. First, “T+0” or “T+1” is meaningful only after defining T, time zone, cutoff and business days: an intermediary initiating a payout is not necessarily the seller’s bank receiving it. Second, “0% withdrawal fee” says nothing about exchange spreads and other charges. Third, a rolling reserveA rolling reserve is a percentage of turnover temporarily retained by a PSP as protection against chargebacks, refunds, fraud and regulatory risk. is an agreed temporary withholding of proceeds to cover risk; it is not the same as a security deposit, total merchant balance, legally required safeguardingMeasures required under the applicable regime to protect relevant customer money. This is separate from institutional capital and operating expenses. or a bank reserve. [9]
In a dispute or payout suspension, establish who controls the account, the legal basis of withholding, release conditions and timing, and who bears the particular loss. Neither “P2P” or “P2C” nor the currency used to settle with the merchant determines by itself who bears a loss or must compensate for a hold.
Checking the payment model before connection
Even if one interface promises “all payments through one API”, the assessment remains contractual and financial. Request six specific answers:
- Which legal entity contracts with you, where does it operate, does it need authorisation and which services does that cover?
- Who is the acquirer, local-system participant or partner bank? Which countries and activities are permitted by contract, scheme and law, and which methods are available to this merchant?
- Where does the seller’s money arise and get recorded: directly in its account, a payment balance, an intermediary’s pooled account or another permitted arrangement? How are funds protected on a participant’s insolvency?
- What do “paid”, “settled” and “available for withdrawal” mean in the interface and agreement? How are payout schedules, refunds and exceptions defined?
- How is the total price calculated, including scheme charges, technical services, FX, disputed transactions and possible reserves?
- On what grounds can rejection, withholding, freezing or termination occur; who receives notices, documents and challenge rights; how are losses allocated?
A mismatch between the actual seller, represented business and the person whose accounts collect payment is a red flag. A registered, disclosed submerchant model is fundamentally different from hiding a merchant behind other people’s personal accounts or an incorrect activity category. Lawful ordinary P2P transfers do not make it acceptable to disguise trading proceeds through them.
Practical takeaway: assess the service by contracts, permitted functions, funds flow and payout rules, not Visa, QR or a familiar brand logo. To discuss cross-border payment structures and regulatory restrictions, contact Discuss your project.
This material explains typical payment arrangements. Specific service permissions, fund-protection assurances, refund rules, territories and permitted merchant categories are determined by applicable law, system rules and contract. Country examples should not be generalised to entire regions; technical payment availability does not establish that every commercial activity is lawful.
Sources
- Federal Reserve History. Electronic Point-of-Sale Payments, 25.09.2024
- Regulation (EU) 2015/751, Article 2 (definitions of acquirer, issuer and card schemes)
- BIS Committee on Payment and Market Infrastructures. Glossary
- Directive (EU) 2015/2366 (PSD2), Article 3(j), Article 4 and Annex I PSD2 application: EFTA, Factsheet 32015L2366 (incorporation into the EEA Agreement); Central Bank of Ireland, Payment Institutions (national implementation). EFTA — EEA-Lex, Directive (EU) 2015/2366 ; Central Bank of Ireland — Payment Institutions
- European Banking Authority. Register of payment and electronic money institutions
- European Central Bank. Instant Payments Regulation, implementation timetable
- Financial Conduct Authority. Apply to become an electronic money or a payment institution, updated 16.06.2026
- Bank of England. Payment and settlement
- Square, U.S. Square Payment Terms, version dated 30.07.2026, §§1–2, 10–15
- Mastercard. Find a payment facilitator
- Bank of Thailand. PromptPay
- Bank of Thailand. Oversight according to Payment Systems Act
- Monetary Authority of Singapore. E-Payments (FAST, PayNow and Payment Services Act)
- Banco Central do Brasil. Instant Payment System (SPI); Pix participants ; Banco Central do Brasil — Pix participants
- Banco de México. SPEI characteristics
- Banco Central de la República Argentina. Transferencias 3.0
- Banco Central de la República Argentina. Registro de proveedores de servicios de pago
- Swift. What is Swift?
- Visa Acceptance Solutions. Payments Also: VisaNet Connect — Acceptance, Authorization API and Capture API sections. VisaNet Connect — Acceptance API documentation
- National Payments Corporation of India. BHIM UPI Brand Guidelines. UPI QR and BHIM UPI Merchant QR sections (PDF: pp. 48, 53–61); description of banks, payment partners, merchants and QR payments
