Payments Academy
Payment scheme PAYMENT OPERATIONS STARTED LIVE 01 Payment scheme - set of rules, standards and operating ACTIVE 02 Why schemes - because no single bank can pay every other QUEUED 03 Users of a scheme - its members. In a card scheme the members QUEUED 04 Four-party card model - Take a card payment. The four parties QUEUED 05 Card payment - Walk a card payment through with real QUEUED 06 SEPA credit transfer - same logic applies to a domestic scheme QUEUED 07 ISO 8583 and pacs.008 messages - scheme defines the messages and the QUEUED 08 Chargebacks and scheme enforcement - When a payment fails QUEUED 09 Effects on customer bank and operations - scheme is what makes a payment QUEUED 10 BA practice - scheme is the first document to read on any QUEUED 11 Key takeaway and further reading - simple: a scheme is the rulebook that QUEUED A payment scheme is a set of rules, standards and operating procedures that govern how a particular type of payment is made, and the body that writes and enforces those rules. A scheme is not a system and not a network. Step 1 of 11 Payment scheme STARTED Payment scheme set of rules, standards and operating ACTIVE Why schemes because no single bank can pay every other QUEUED Users of a scheme its members. In a card scheme the members QUEUED Four-party card model Take a card payment. The four parties QUEUED Card payment Walk a card payment through with real QUEUED SEPA credit transfer same logic applies to a domestic scheme QUEUED ISO 8583 and pacs.008 messages scheme defines the messages and the data. QUEUED Chargebacks and scheme enforcement When a payment fails QUEUED Effects on customer bank and operations scheme is what makes a payment safe to QUEUED BA practice scheme is the first document to read on any QUEUED Key takeaway and further reading simple: a scheme is the rulebook that makes QUEUED A payment scheme is a set of rules, standards and operating procedures that govern how a particular type of payment is made, and the body that writes and enforces those rules. A scheme is not a system and not a network.
Why schemes exist: interoperability PAYMENT OPERATIONS IN PROGRESS LIVE 01 Payment scheme - set of rules, standards and operating DONE 02 Why schemes - because no single bank can pay every other ACTIVE 03 Users of a scheme - its members. In a card scheme the members QUEUED 04 Four-party card model - Take a card payment. The four parties QUEUED 05 Card payment - Walk a card payment through with real QUEUED 06 SEPA credit transfer - same logic applies to a domestic scheme QUEUED 07 ISO 8583 and pacs.008 messages - scheme defines the messages and the QUEUED 08 Chargebacks and scheme enforcement - When a payment fails QUEUED 09 Effects on customer bank and operations - scheme is what makes a payment QUEUED 10 BA practice - scheme is the first document to read on any QUEUED 11 Key takeaway and further reading - simple: a scheme is the rulebook that QUEUED Schemes exist because no single bank can pay every other bank on its own terms. Without a common rulebook, each pair of banks would need a bilateral agreement on message formats, value dates, return codes and liability, Step 2 of 11 Why schemes exist: interoperability IN PROGRESS Payment scheme set of rules, standards and operating DONE Why schemes because no single bank can pay every other ACTIVE Users of a scheme its members. In a card scheme the members QUEUED Four-party card model Take a card payment. The four parties QUEUED Card payment Walk a card payment through with real QUEUED SEPA credit transfer same logic applies to a domestic scheme QUEUED ISO 8583 and pacs.008 messages scheme defines the messages and the data. QUEUED Chargebacks and scheme enforcement When a payment fails QUEUED Effects on customer bank and operations scheme is what makes a payment safe to QUEUED BA practice scheme is the first document to read on any QUEUED Key takeaway and further reading simple: a scheme is the rulebook that makes QUEUED Schemes exist because no single bank can pay every other bank on its own terms. Without a common rulebook, each pair of banks would need a bilateral agreement on message formats, value dates, return codes and liability,
Users of a scheme PAYMENT OPERATIONS IN PROGRESS LIVE 01 Payment scheme - set of rules, standards and operating DONE 02 Why schemes - because no single bank can pay every other DONE 03 Users of a scheme - its members. In a card scheme the members ACTIVE 04 Four-party card model - Take a card payment. The four parties QUEUED 05 Card payment - Walk a card payment through with real QUEUED 06 SEPA credit transfer - same logic applies to a domestic scheme QUEUED 07 ISO 8583 and pacs.008 messages - scheme defines the messages and the QUEUED 08 Chargebacks and scheme enforcement - When a payment fails QUEUED 09 Effects on customer bank and operations - scheme is what makes a payment QUEUED 10 BA practice - scheme is the first document to read on any QUEUED 11 Key takeaway and further reading - simple: a scheme is the rulebook that QUEUED The users of a scheme are its members. In a card scheme the members are issuers, the bank that issued the cardholder card, and acquirers, the bank or PSP that serves the merchant. In SEPA the members are payment service Step 3 of 11 Users of a scheme IN PROGRESS Payment scheme set of rules, standards and operating DONE Why schemes because no single bank can pay every other DONE Users of a scheme its members. In a card scheme the members ACTIVE Four-party card model Take a card payment. The four parties QUEUED Card payment Walk a card payment through with real QUEUED SEPA credit transfer same logic applies to a domestic scheme QUEUED ISO 8583 and pacs.008 messages scheme defines the messages and the data. QUEUED Chargebacks and scheme enforcement When a payment fails QUEUED Effects on customer bank and operations scheme is what makes a payment safe to QUEUED BA practice scheme is the first document to read on any QUEUED Key takeaway and further reading simple: a scheme is the rulebook that makes QUEUED The users of a scheme are its members. In a card scheme the members are issuers, the bank that issued the cardholder card, and acquirers, the bank or PSP that serves the merchant. In SEPA the members are payment service
Four-party card model PAYMENT OPERATIONS IN PROGRESS LIVE 01 Payment scheme - set of rules, standards and operating DONE 02 Why schemes - because no single bank can pay every other DONE 03 Users of a scheme - its members. In a card scheme the members DONE 04 Four-party card model - Take a card payment. The four parties ACTIVE 05 Card payment - Walk a card payment through with real QUEUED 06 SEPA credit transfer - same logic applies to a domestic scheme QUEUED 07 ISO 8583 and pacs.008 messages - scheme defines the messages and the QUEUED 08 Chargebacks and scheme enforcement - When a payment fails QUEUED 09 Effects on customer bank and operations - scheme is what makes a payment QUEUED 10 BA practice - scheme is the first document to read on any QUEUED 11 Key takeaway and further reading - simple: a scheme is the rulebook that QUEUED Take a card payment. The four parties are the cardholder, the merchant, the issuer and the acquirer. The cardholder buys from the merchant. The merchant acquirer takes the card details and asks the issuer, through the sc Step 4 of 11 Four-party card model IN PROGRESS Payment scheme set of rules, standards and operating DONE Why schemes because no single bank can pay every other DONE Users of a scheme its members. In a card scheme the members DONE Four-party card model Take a card payment. The four parties ACTIVE Card payment Walk a card payment through with real QUEUED SEPA credit transfer same logic applies to a domestic scheme QUEUED ISO 8583 and pacs.008 messages scheme defines the messages and the data. QUEUED Chargebacks and scheme enforcement When a payment fails QUEUED Effects on customer bank and operations scheme is what makes a payment safe to QUEUED BA practice scheme is the first document to read on any QUEUED Key takeaway and further reading simple: a scheme is the rulebook that makes QUEUED Take a card payment. The four parties are the cardholder, the merchant, the issuer and the acquirer. The cardholder buys from the merchant. The merchant acquirer takes the card details and asks the issuer, through the sc
Card payment: authorisation to settlement PAYMENT OPERATIONS IN PROGRESS LIVE 01 Payment scheme - set of rules, standards and operating DONE 02 Why schemes - because no single bank can pay every other DONE 03 Users of a scheme - its members. In a card scheme the members DONE 04 Four-party card model - Take a card payment. The four parties DONE 05 Card payment - Walk a card payment through with real ACTIVE 06 SEPA credit transfer - same logic applies to a domestic scheme QUEUED 07 ISO 8583 and pacs.008 messages - scheme defines the messages and the QUEUED 08 Chargebacks and scheme enforcement - When a payment fails QUEUED 09 Effects on customer bank and operations - scheme is what makes a payment QUEUED 10 BA practice - scheme is the first document to read on any QUEUED 11 Key takeaway and further reading - simple: a scheme is the rulebook that QUEUED Walk a card payment through with real numbers. A customer buys a jacket for 120 pounds from an online merchant using a Visa debit card. The merchant PSP sends an authorisation request for 120 pounds through the Visa swit Step 5 of 11 Card payment: authorisation to settlement IN PROGRESS Payment scheme set of rules, standards and operating DONE Why schemes because no single bank can pay every other DONE Users of a scheme its members. In a card scheme the members DONE Four-party card model Take a card payment. The four parties DONE Card payment Walk a card payment through with real ACTIVE SEPA credit transfer same logic applies to a domestic scheme QUEUED ISO 8583 and pacs.008 messages scheme defines the messages and the data. QUEUED Chargebacks and scheme enforcement When a payment fails QUEUED Effects on customer bank and operations scheme is what makes a payment safe to QUEUED BA practice scheme is the first document to read on any QUEUED Key takeaway and further reading simple: a scheme is the rulebook that makes QUEUED Walk a card payment through with real numbers. A customer buys a jacket for 120 pounds from an online merchant using a Visa debit card. The merchant PSP sends an authorisation request for 120 pounds through the Visa swit
SEPA credit transfer end to end PAYMENT OPERATIONS IN PROGRESS LIVE 01 Payment scheme - set of rules, standards and operating DONE 02 Why schemes - because no single bank can pay every other DONE 03 Users of a scheme - its members. In a card scheme the members DONE 04 Four-party card model - Take a card payment. The four parties DONE 05 Card payment - Walk a card payment through with real DONE 06 SEPA credit transfer - same logic applies to a domestic scheme ACTIVE 07 ISO 8583 and pacs.008 messages - scheme defines the messages and the QUEUED 08 Chargebacks and scheme enforcement - When a payment fails QUEUED 09 Effects on customer bank and operations - scheme is what makes a payment QUEUED 10 BA practice - scheme is the first document to read on any QUEUED 11 Key takeaway and further reading - simple: a scheme is the rulebook that QUEUED The same logic applies to a domestic scheme payment. A company in Munich pays a supplier in Lyon 25,000 euro by SEPA Credit Transfer. The company sends a pain.001 to its bank. The bank validates it, debits the company ac Step 6 of 11 SEPA credit transfer end to end IN PROGRESS Payment scheme set of rules, standards and operating DONE Why schemes because no single bank can pay every other DONE Users of a scheme its members. In a card scheme the members DONE Four-party card model Take a card payment. The four parties DONE Card payment Walk a card payment through with real DONE SEPA credit transfer same logic applies to a domestic scheme ACTIVE ISO 8583 and pacs.008 messages scheme defines the messages and the data. QUEUED Chargebacks and scheme enforcement When a payment fails QUEUED Effects on customer bank and operations scheme is what makes a payment safe to QUEUED BA practice scheme is the first document to read on any QUEUED Key takeaway and further reading simple: a scheme is the rulebook that makes QUEUED The same logic applies to a domestic scheme payment. A company in Munich pays a supplier in Lyon 25,000 euro by SEPA Credit Transfer. The company sends a pain.001 to its bank. The bank validates it, debits the company ac
ISO 8583 and pacs.008 messages PAYMENT OPERATIONS IN PROGRESS LIVE 01 Payment scheme - set of rules, standards and operating DONE 02 Why schemes - because no single bank can pay every other DONE 03 Users of a scheme - its members. In a card scheme the members DONE 04 Four-party card model - Take a card payment. The four parties DONE 05 Card payment - Walk a card payment through with real DONE 06 SEPA credit transfer - same logic applies to a domestic scheme DONE 07 ISO 8583 and pacs.008 messages - scheme defines the messages and the ACTIVE 08 Chargebacks and scheme enforcement - When a payment fails QUEUED 09 Effects on customer bank and operations - scheme is what makes a payment QUEUED 10 BA practice - scheme is the first document to read on any QUEUED 11 Key takeaway and further reading - simple: a scheme is the rulebook that QUEUED The scheme defines the messages and the data. For a card payment the authorisation travels as an ISO 8583 message, with a message type indicator (for example 0100 for an authorisation request) and data elements for the c Step 7 of 11 ISO 8583 and pacs.008 messages IN PROGRESS Payment scheme set of rules, standards and operating DONE Why schemes because no single bank can pay every other DONE Users of a scheme its members. In a card scheme the members DONE Four-party card model Take a card payment. The four parties DONE Card payment Walk a card payment through with real DONE SEPA credit transfer same logic applies to a domestic scheme DONE ISO 8583 and pacs.008 messages scheme defines the messages and the data. ACTIVE Chargebacks and scheme enforcement When a payment fails QUEUED Effects on customer bank and operations scheme is what makes a payment safe to QUEUED BA practice scheme is the first document to read on any QUEUED Key takeaway and further reading simple: a scheme is the rulebook that makes QUEUED The scheme defines the messages and the data. For a card payment the authorisation travels as an ISO 8583 message, with a message type indicator (for example 0100 for an authorisation request) and data elements for the c
Chargebacks and scheme enforcement PAYMENT OPERATIONS IN PROGRESS LIVE 01 Payment scheme - set of rules, standards and operating DONE 02 Why schemes - because no single bank can pay every other DONE 03 Users of a scheme - its members. In a card scheme the members DONE 04 Four-party card model - Take a card payment. The four parties DONE 05 Card payment - Walk a card payment through with real DONE 06 SEPA credit transfer - same logic applies to a domestic scheme DONE 07 ISO 8583 and pacs.008 messages - scheme defines the messages and the DONE 08 Chargebacks and scheme enforcement - When a payment fails ACTIVE 09 Effects on customer bank and operations - scheme is what makes a payment QUEUED 10 BA practice - scheme is the first document to read on any QUEUED 11 Key takeaway and further reading - simple: a scheme is the rulebook that QUEUED When a payment fails, the scheme defines the remedy. A cardholder who paid 120 pounds for a jacket that never arrived raises a dispute with the issuer. The issuer opens a chargeback through the scheme, and the 120 pounds Step 8 of 11 Chargebacks and scheme enforcement IN PROGRESS Payment scheme set of rules, standards and operating DONE Why schemes because no single bank can pay every other DONE Users of a scheme its members. In a card scheme the members DONE Four-party card model Take a card payment. The four parties DONE Card payment Walk a card payment through with real DONE SEPA credit transfer same logic applies to a domestic scheme DONE ISO 8583 and pacs.008 messages scheme defines the messages and the data. DONE Chargebacks and scheme enforcement When a payment fails ACTIVE Effects on customer bank and operations scheme is what makes a payment safe to QUEUED BA practice scheme is the first document to read on any QUEUED Key takeaway and further reading simple: a scheme is the rulebook that makes QUEUED When a payment fails, the scheme defines the remedy. A cardholder who paid 120 pounds for a jacket that never arrived raises a dispute with the issuer. The issuer opens a chargeback through the scheme, and the 120 pounds
Effects on customer, bank and operations PAYMENT OPERATIONS IN PROGRESS LIVE 01 Payment scheme - set of rules, standards and operating DONE 02 Why schemes - because no single bank can pay every other DONE 03 Users of a scheme - its members. In a card scheme the members DONE 04 Four-party card model - Take a card payment. The four parties DONE 05 Card payment - Walk a card payment through with real DONE 06 SEPA credit transfer - same logic applies to a domestic scheme DONE 07 ISO 8583 and pacs.008 messages - scheme defines the messages and the DONE 08 Chargebacks and scheme enforcement - When a payment fails DONE 09 Effects on customer bank and operations - scheme is what makes a payment ACTIVE 10 BA practice - scheme is the first document to read on any QUEUED 11 Key takeaway and further reading - simple: a scheme is the rulebook that QUEUED For the customer, the scheme is what makes a payment safe to make: the money arrives in a known time, the full amount is credited for a SEPA payment, and there is a defined route to get the money back when something goes Step 9 of 11 Effects on customer, bank and operations IN PROGRESS Payment scheme set of rules, standards and operating DONE Why schemes because no single bank can pay every other DONE Users of a scheme its members. In a card scheme the members DONE Four-party card model Take a card payment. The four parties DONE Card payment Walk a card payment through with real DONE SEPA credit transfer same logic applies to a domestic scheme DONE ISO 8583 and pacs.008 messages scheme defines the messages and the data. DONE Chargebacks and scheme enforcement When a payment fails DONE Effects on customer bank and operations scheme is what makes a payment safe to ACTIVE BA practice scheme is the first document to read on any QUEUED Key takeaway and further reading simple: a scheme is the rulebook that makes QUEUED For the customer, the scheme is what makes a payment safe to make: the money arrives in a known time, the full amount is credited for a SEPA payment, and there is a defined route to get the money back when something goes
BA practice: rulebook artefacts PAYMENT OPERATIONS IN PROGRESS LIVE 01 Payment scheme - set of rules, standards and operating DONE 02 Why schemes - because no single bank can pay every other DONE 03 Users of a scheme - its members. In a card scheme the members DONE 04 Four-party card model - Take a card payment. The four parties DONE 05 Card payment - Walk a card payment through with real DONE 06 SEPA credit transfer - same logic applies to a domestic scheme DONE 07 ISO 8583 and pacs.008 messages - scheme defines the messages and the DONE 08 Chargebacks and scheme enforcement - When a payment fails DONE 09 Effects on customer bank and operations - scheme is what makes a payment DONE 10 BA practice - scheme is the first document to read on any ACTIVE 11 Key takeaway and further reading - simple: a scheme is the rulebook that QUEUED For a BA, the scheme is the first document to read on any new payment feature. The artefacts are the scheme rulebook extract that governs the feature, a scheme compliance checklist that maps each rule to a requirement, a Step 10 of 11 BA practice: rulebook artefacts IN PROGRESS Payment scheme set of rules, standards and operating DONE Why schemes because no single bank can pay every other DONE Users of a scheme its members. In a card scheme the members DONE Four-party card model Take a card payment. The four parties DONE Card payment Walk a card payment through with real DONE SEPA credit transfer same logic applies to a domestic scheme DONE ISO 8583 and pacs.008 messages scheme defines the messages and the data. DONE Chargebacks and scheme enforcement When a payment fails DONE Effects on customer bank and operations scheme is what makes a payment safe to DONE BA practice scheme is the first document to read on any ACTIVE Key takeaway and further reading simple: a scheme is the rulebook that makes QUEUED For a BA, the scheme is the first document to read on any new payment feature. The artefacts are the scheme rulebook extract that governs the feature, a scheme compliance checklist that maps each rule to a requirement, a
Key takeaway and further reading PAYMENT OPERATIONS COMPLETE LIVE 01 Payment scheme - set of rules, standards and operating DONE 02 Why schemes - because no single bank can pay every other DONE 03 Users of a scheme - its members. In a card scheme the members DONE 04 Four-party card model - Take a card payment. The four parties DONE 05 Card payment - Walk a card payment through with real DONE 06 SEPA credit transfer - same logic applies to a domestic scheme DONE 07 ISO 8583 and pacs.008 messages - scheme defines the messages and the DONE 08 Chargebacks and scheme enforcement - When a payment fails DONE 09 Effects on customer bank and operations - scheme is what makes a payment DONE 10 BA practice - scheme is the first document to read on any DONE 11 Key takeaway and further reading - simple: a scheme is the rulebook that ACTIVE The takeaway is simple: a scheme is the rulebook that makes payments interoperable, and every payment you build must be traceable to a rule in that book. Know the scheme for the payment you are working on, know its ruleb Step 11 of 11 Key takeaway and further reading COMPLETE Payment scheme set of rules, standards and operating DONE Why schemes because no single bank can pay every other DONE Users of a scheme its members. In a card scheme the members DONE Four-party card model Take a card payment. The four parties DONE Card payment Walk a card payment through with real DONE SEPA credit transfer same logic applies to a domestic scheme DONE ISO 8583 and pacs.008 messages scheme defines the messages and the data. DONE Chargebacks and scheme enforcement When a payment fails DONE Effects on customer bank and operations scheme is what makes a payment safe to DONE BA practice scheme is the first document to read on any DONE Key takeaway and further reading simple: a scheme is the rulebook that makes ACTIVE The takeaway is simple: a scheme is the rulebook that makes payments interoperable, and every payment you build must be traceable to a rule in that book. Know the scheme for the payment you are working on, know its ruleb

Key points of this lesson, in order.

0:00 / 11:06 Step 1 of 11

Payment schemes and payment service providers

The Payment Ecosystem, Lesson 5 of 7, Narration 11:06, D01 Foundations of money and payments

SettlementAcquirerScheme

What you will learn

Your objective. By the end of this lesson, you will be able to name the scheme for a given payment, read a rulebook extract, map the parties in the four-party card model, trace the money and the fees through authorisation, clearing and settlement, and write a requirement that cites a scheme rule.

Why it matters. A scheme is the rulebook that makes payments interoperable. Every payment you build must be traceable to a rule in that book, and a feature that violates scheme rules will be rejected in testing or lead to fines after launch.

Chapter objective: Learner maps the payment ecosystem, naming the roles of payer, payee, issuing bank, acquiring bank, clearing house, central bank, and network, and traces how value moves between them. Learner practises this skill on realistic banking cases, explaining the reasoning clearly and using correct terminology throughout the work.

Key learning points

  • Payment scheme
  • Why schemes exist: interoperability
  • Users of a scheme
  • Four-party card model
  • Card payment: authorisation to settlement
  • SEPA credit transfer end to end
  • ISO 8583 and pacs.008 messages
  • Chargebacks and scheme enforcement
  • Effects on customer, bank and operations
  • BA practice: rulebook artefacts
  • Key takeaway and further reading

Key terms

Settlement: The final movement of funds between banks to discharge obligations created by cleared payments. Settlement is usually made in central bank money or through correspondent accounts.

Acquirer: A bank or licensed institution that processes card payments for merchants and receives transaction funds from card schemes on their behalf.

Scheme: A card or payment network that sets the rules, standards and fees for transactions between issuers and acquirers.

Payment flow diagram showing Payment schemes and payment service providers.

Practise this lesson

Exercise

Trace the 120 pound card payment in this lesson through authorisation, clearing and settlement, and trace the 25,000 euro SEPA payment the same way.

Use the four-party model for the card payment and the pain.001 to pacs.008 to STEP2 to T2 chain for the SEPA payment. The amounts, fees and rulebook version are all in the lesson.

  1. What to do. For each payment, state what happens at each stage, which message carries it, who pays whom, and when the merchant or supplier is actually credited.

Correct result. Card: authorisation holds 120 pounds via ISO 8583 message type 0100; clearing sends the transaction in the acquirer batch file to Visa; settlement moves the net amount between issuer and acquirer settlement accounts; the merchant is credited 119.28 pounds on the next business day after 0.24 pounds interchange, 0.12 pounds scheme fee and 0.36 pounds acquirer margin. SEPA: pain.001 from the company, bank debits 25,000 euro, pacs.008 through STEP2, net positions settle in T2, supplier credited 25,000 euro in full under EPC SCT Rulebook 2025 version 1.1.

Why. A card payment is not one event. The customer sees it at once, the merchant gets it the next business day, and the difference is the clearing and settlement cycle plus the fees the scheme defines.

Check your understanding

Practice question

A merchant receives 119.28 pounds for a 120 pound Visa debit sale. Which component is capped by law in the EU and UK?

Takeaway and next step

What to remember

A scheme is the rulebook that makes payments interoperable. Know the scheme for the payment you are working on, know its rulebook version, know its parties and its messages, and know what happens when it fails.

Follow a card payment through authorisation, clearing and settlement, and note where the scheme rules bite at each stage.

Open the Payment Lifecycle Simulator →

Builds on debtor, creditor, debtor agent and creditor agent from ch3s1 to ch3s4, and feeds every scheme-specific chapter that follows.

Transcript and full text

Show transcript

A payment scheme is a set of rules, standards and operating procedures that govern how a particular type of payment is made, and the body that writes and enforces those rules. A scheme is not a system and not a network. The system is the infrastructure that moves the money, for example the Faster Payments central infrastructure or the T2 real-time gross settlement service. The network is the connectivity, for example the SWIFT network. The scheme is the rulebook and the membership: it says who may participate, what messages they must send, what fields are mandatory, how long each step may take, what happens when a payment fails, and who bears the loss. Card schemes (Visa, Mastercard), domestic credit transfer and direct debit schemes (SEPA SCT, SDD, BACS, Faster Payments), and instant payment schemes (SCT Inst) are the main families, and each is run by a scheme operator: Visa Inc and Mastercard for the card schemes, the European Payments Council (EPC) for the SEPA schemes, and Pay.UK for Faster Payments and BACS. Schemes exist because no single bank can pay every other bank on its own terms. Without a common rulebook, each pair of banks would need a bilateral agreement on message formats, value dates, return codes and liability, which would be thousands of agreements and no interoperability. A scheme gives every member the same standard, so a bank in Madrid can pay a bank in Lyon without negotiating anything. The scheme also creates trust: it sets the dispute and chargeback process, it allocates risk and liability when something goes wrong, and it gives the customer recourse. Without a scheme, a cardholder who never received the goods would have no defined route to get the money back, and a merchant would have no certainty about when the money is final. The users of a scheme are its members. In a card scheme the members are issuers, the bank that issued the cardholder card, and acquirers, the bank or PSP that serves the merchant. In SEPA the members are payment service providers that have adhered to the scheme by signing the EPC adherence agreement; adherence is public and a PSP that has not adhered cannot send SEPA payments. Some members participate directly, holding a settlement account and connecting to the clearing system; others participate indirectly through a direct member that sponsors them. A PSP that is not a direct scheme member reaches the scheme through its sponsor bank. The scheme operator also sets certification: a new member must pass scheme testing and certification before it may go live, and it must re-certify when the scheme changes its rules. Take a card payment. The four parties are the cardholder, the merchant, the issuer and the acquirer. The cardholder buys from the merchant. The merchant acquirer takes the card details and asks the issuer, through the scheme switch, whether the cardholder may pay. The issuer approves or declines. The scheme sits between issuer and acquirer: it routes the authorisation, it clears the transactions, it nets the amounts, and it settles the net positions between issuers and acquirers. A PSP can play several roles: a merchant acquirer that underwrites the merchant and settles the funds, a payment gateway that only passes the card details and never touches the money, an aggregator that signs the merchant under its own merchant account, a payment initiator that starts a payment from a bank account under PSD2, and an account information provider that only reads account data. Each type has a different licence: an electronic money institution may hold customer funds, a payment institution may execute payments but not hold funds long term, and an agent of a bank acts under the bank licence. In the UK the Financial Conduct Authority authorises PSPs; in the EU the national competent authority does. Walk a card payment through with real numbers. A customer buys a jacket for 120 pounds from an online merchant using a Visa debit card. The merchant PSP sends an authorisation request for 120 pounds through the Visa switch to the issuing bank. The issuer checks the balance, checks for fraud, and approves; the 120 pounds is held on the cardholder account. At the end of the day the merchant acquirer sends the clearing file to Visa with the 120 pound transaction. Visa nets it against all other transactions between that issuer and acquirer, and the net amount moves between their settlement accounts. The merchant is credited 120 pounds less the merchant discount rate: suppose interchange is 0.2 percent (0.24 pounds, capped for debit cards in the EU and UK under Regulation (EU) 2015/751), the scheme fee is 0.1 percent (0.12 pounds), and the acquirer margin is 0.3 percent (0.36 pounds), so the merchant receives 119.28 pounds, usually on the next business day. The cardholder sees the 120 pound debit when the clearing completes. The same logic applies to a domestic scheme payment. A company in Munich pays a supplier in Lyon 25,000 euro by SEPA Credit Transfer. The company sends a pain.001 to its bank. The bank validates it, debits the company account 25,000 euro, and sends a pacs.008 to the supplier bank through the STEP2 clearing system. STEP2 nets the day payments and the net positions settle in T2, the Eurosystem real-time gross settlement service. The supplier bank credits the supplier 25,000 euro in full, because the SCT rulebook requires the full amount to be credited. The rulebook that governs every step is the EPC SEPA Credit Transfer Rulebook, 2025 version 1.1, effective 5 October 2025. The messages, the one-business-day execution time, and the return codes all come from that rulebook and its implementation guidelines. The scheme defines the messages and the data. For a card payment the authorisation travels as an ISO 8583 message, with a message type indicator (for example 0100 for an authorisation request) and data elements for the card number, amount, merchant category and the EMV cryptogram. For a SEPA payment the messages are pain.001, pacs.008, pacs.002 for status, and pacs.004 for returns, all in ISO 20022 XML. The scheme also defines the return and reason codes: in SEPA a return for a closed account carries reason code AC04, and a return for an insufficient balance carries AM04. The systems are the scheme switch (VisaNet, the Mastercard network), the clearing system (STEP2, the Faster Payments central infrastructure), and the settlement account at the central bank (T2 for euro, the Bank of England for CHAPS and Faster Payments settlement). A BA must know which message carries each step, because a defect is usually a wrong field in one of these messages. When a payment fails, the scheme defines the remedy. A cardholder who paid 120 pounds for a jacket that never arrived raises a dispute with the issuer. The issuer opens a chargeback through the scheme, and the 120 pounds is pulled back from the acquirer and credited to the cardholder while the dispute is investigated. The merchant must provide proof of delivery within the scheme deadline, usually 30 to 45 days depending on the scheme and the reason code. If the merchant cannot prove delivery, the chargeback stands and the merchant loses the 120 pounds plus a chargeback fee. If the merchant proves delivery, the chargeback is reversed. The scheme also runs pre-arbitration and arbitration when issuer and acquirer disagree. A scheme rule breach is different: if a member sends payments that break the rulebook, for example by omitting a mandatory field, the scheme can fine the member, suspend it, or in the extreme case remove it from the scheme. For the customer, the scheme is what makes a payment safe to make: the money arrives in a known time, the full amount is credited for a SEPA payment, and there is a defined route to get the money back when something goes wrong. For the bank, the scheme is a cost and a constraint: interchange and scheme fees on every card transaction, certification and testing for every scheme change, and fines for non-compliance. For operations, the scheme drives the daily work: reconciling the scheme clearing files against the ledger, funding the settlement account before the settlement window, working the exception queue for returns and chargebacks, and applying scheme change notices to the build and test plan. A scheme change notice that raises a limit or adds a mandatory field is a project, not a configuration tweak. For a BA, the scheme is the first document to read on any new payment feature. The artefacts are the scheme rulebook extract that governs the feature, a scheme compliance checklist that maps each rule to a requirement, a certification test pack that proves the build meets the scheme, and a scheme change impact note when the operator publishes a new version. The common mistakes are confusing scheme rules with bank policy (the scheme says what must happen, the bank decides how), hard coding a limit that the scheme later changes (the SCT Inst 100,000 euro cap was removed by the 2025 rulebook, and any bank that had hard coded it had to rebuild), and missing a scheme-mandated field (a pacs.008 without a mandatory debtor agent will be rejected by the clearing system). When you write a requirement, cite the rulebook name, version and section: the payment must carry the debtor agent BIC, mandatory under EPC SCT Rulebook 2025 version 1.1, section 4.3. That citation is what makes the requirement testable. The takeaway is simple: a scheme is the rulebook that makes payments interoperable, and every payment you build must be traceable to a rule in that book. Know the scheme for the payment you are working on, know its rulebook version, know its parties and its messages, and know what happens when it fails. Further reading: EPC SEPA Credit Transfer Rulebook 2025 version 1.1 (effective 5 October 2025); EPC SCT Inst Rulebook 2025; Pay.UK Faster Payments scheme rules; Visa Core Rules; Mastercard rules; Regulation (EU) 2015/751 on interchange fees; SWIFT gpi service description. Last reviewed 7 November 2026.

A payment scheme is a set of rules, standards and operating procedures that govern how a particular type of payment is made, and the body that writes and enforces those rules. A scheme is not a system and not a network. The system is the infrastructure that moves the money, for example the Faster Payments central infrastructure or the T2 real-time gross settlement service. The network is the connectivity, for example the SWIFT network. The scheme is the rulebook and the membership: it says who may participate, what messages they must send, what fields are mandatory, how long each step may take, what happens when a payment fails, and who bears the loss. Card schemes (Visa, Mastercard), domestic credit transfer and direct debit schemes (SEPA SCT, SDD, BACS, Faster Payments), and instant payment schemes (SCT Inst) are the main families, and each is run by a scheme operator: Visa Inc and Mastercard for the card schemes, the European Payments Council (EPC) for the SEPA schemes, and Pay.UK for Faster Payments and BACS.

Schemes exist because no single bank can pay every other bank on its own terms. Without a common rulebook, each pair of banks would need a bilateral agreement on message formats, value dates, return codes and liability, which would be thousands of agreements and no interoperability. A scheme gives every member the same standard, so a bank in Madrid can pay a bank in Lyon without negotiating anything. The scheme also creates trust: it sets the dispute and chargeback process, it allocates risk and liability when something goes wrong, and it gives the customer recourse. Without a scheme, a cardholder who never received the goods would have no defined route to get the money back, and a merchant would have no certainty about when the money is final.

The users of a scheme are its members. In a card scheme the members are issuers, the bank that issued the cardholder card, and acquirers, the bank or PSP that serves the merchant. In SEPA the members are payment service providers that have adhered to the scheme by signing the EPC adherence agreement; adherence is public and a PSP that has not adhered cannot send SEPA payments. Some members participate directly, holding a settlement account and connecting to the clearing system; others participate indirectly through a direct member that sponsors them. A PSP that is not a direct scheme member reaches the scheme through its sponsor bank. The scheme operator also sets certification: a new member must pass scheme testing and certification before it may go live, and it must re-certify when the scheme changes its rules.

Take a card payment. The four parties are the cardholder, the merchant, the issuer and the acquirer. The cardholder buys from the merchant. The merchant acquirer takes the card details and asks the issuer, through the scheme switch, whether the cardholder may pay. The issuer approves or declines. The scheme sits between issuer and acquirer: it routes the authorisation, it clears the transactions, it nets the amounts, and it settles the net positions between issuers and acquirers. A PSP can play several roles: a merchant acquirer that underwrites the merchant and settles the funds, a payment gateway that only passes the card details and never touches the money, an aggregator that signs the merchant under its own merchant account, a payment initiator that starts a payment from a bank account under PSD2, and an account information provider that only reads account data. Each type has a different licence: an electronic money institution may hold customer funds, a payment institution may execute payments but not hold funds long term, and an agent of a bank acts under the bank licence. In the UK the Financial Conduct Authority authorises PSPs; in the EU the national competent authority does.

Walk a card payment through with real numbers. A customer buys a jacket for 120 pounds from an online merchant using a Visa debit card. The merchant PSP sends an authorisation request for 120 pounds through the Visa switch to the issuing bank. The issuer checks the balance, checks for fraud, and approves; the 120 pounds is held on the cardholder account. At the end of the day the merchant acquirer sends the clearing file to Visa with the 120 pound transaction. Visa nets it against all other transactions between that issuer and acquirer, and the net amount moves between their settlement accounts. The merchant is credited 120 pounds less the merchant discount rate: suppose interchange is 0.2 percent (0.24 pounds, capped for debit cards in the EU and UK under Regulation (EU) 2015/751), the scheme fee is 0.1 percent (0.12 pounds), and the acquirer margin is 0.3 percent (0.36 pounds), so the merchant receives 119.28 pounds, usually on the next business day. The cardholder sees the 120 pound debit when the clearing completes.

The same logic applies to a domestic scheme payment. A company in Munich pays a supplier in Lyon 25,000 euro by SEPA Credit Transfer. The company sends a pain.001 to its bank. The bank validates it, debits the company account 25,000 euro, and sends a pacs.008 to the supplier bank through the STEP2 clearing system. STEP2 nets the day payments and the net positions settle in T2, the Eurosystem real-time gross settlement service. The supplier bank credits the supplier 25,000 euro in full, because the SCT rulebook requires the full amount to be credited. The rulebook that governs every step is the EPC SEPA Credit Transfer Rulebook, 2025 version 1.1, effective 5 October 2025. The messages, the one-business-day execution time, and the return codes all come from that rulebook and its implementation guidelines.

The scheme defines the messages and the data. For a card payment the authorisation travels as an ISO 8583 message, with a message type indicator (for example 0100 for an authorisation request) and data elements for the card number, amount, merchant category and the EMV cryptogram. For a SEPA payment the messages are pain.001, pacs.008, pacs.002 for status, and pacs.004 for returns, all in ISO 20022 XML. The scheme also defines the return and reason codes: in SEPA a return for a closed account carries reason code AC04, and a return for an insufficient balance carries AM04. The systems are the scheme switch (VisaNet, the Mastercard network), the clearing system (STEP2, the Faster Payments central infrastructure), and the settlement account at the central bank (T2 for euro, the Bank of England for CHAPS and Faster Payments settlement). A BA must know which message carries each step, because a defect is usually a wrong field in one of these messages.

When a payment fails, the scheme defines the remedy. A cardholder who paid 120 pounds for a jacket that never arrived raises a dispute with the issuer. The issuer opens a chargeback through the scheme, and the 120 pounds is pulled back from the acquirer and credited to the cardholder while the dispute is investigated. The merchant must provide proof of delivery within the scheme deadline, usually 30 to 45 days depending on the scheme and the reason code. If the merchant cannot prove delivery, the chargeback stands and the merchant loses the 120 pounds plus a chargeback fee. If the merchant proves delivery, the chargeback is reversed. The scheme also runs pre-arbitration and arbitration when issuer and acquirer disagree. A scheme rule breach is different: if a member sends payments that break the rulebook, for example by omitting a mandatory field, the scheme can fine the member, suspend it, or in the extreme case remove it from the scheme.

For the customer, the scheme is what makes a payment safe to make: the money arrives in a known time, the full amount is credited for a SEPA payment, and there is a defined route to get the money back when something goes wrong. For the bank, the scheme is a cost and a constraint: interchange and scheme fees on every card transaction, certification and testing for every scheme change, and fines for non-compliance. For operations, the scheme drives the daily work: reconciling the scheme clearing files against the ledger, funding the settlement account before the settlement window, working the exception queue for returns and chargebacks, and applying scheme change notices to the build and test plan. A scheme change notice that raises a limit or adds a mandatory field is a project, not a configuration tweak.

For a BA, the scheme is the first document to read on any new payment feature. The artefacts are the scheme rulebook extract that governs the feature, a scheme compliance checklist that maps each rule to a requirement, a certification test pack that proves the build meets the scheme, and a scheme change impact note when the operator publishes a new version. The common mistakes are confusing scheme rules with bank policy (the scheme says what must happen, the bank decides how), hard coding a limit that the scheme later changes (the SCT Inst 100,000 euro cap was removed by the 2025 rulebook, and any bank that had hard coded it had to rebuild), and missing a scheme-mandated field (a pacs.008 without a mandatory debtor agent will be rejected by the clearing system). When you write a requirement, cite the rulebook name, version and section: the payment must carry the debtor agent BIC, mandatory under EPC SCT Rulebook 2025 version 1.1, section 4.3. That citation is what makes the requirement testable.

The takeaway is simple: a scheme is the rulebook that makes payments interoperable, and every payment you build must be traceable to a rule in that book. Know the scheme for the payment you are working on, know its rulebook version, know its parties and its messages, and know what happens when it fails. Further reading: EPC SEPA Credit Transfer Rulebook 2025 version 1.1 (effective 5 October 2025); EPC SCT Inst Rulebook 2025; Pay.UK Faster Payments scheme rules; Visa Core Rules; Mastercard rules; Regulation (EU) 2015/751 on interchange fees; SWIFT gpi service description. Last reviewed 7 November 2026.

Full lesson text (all scenes)

Completing a lesson updates your progress dashboard on the homepage.

Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.