Bachelors Program in Banking Finance and Insurance
FinTech & Digital Banking
•
Bachelor
Payment Systems and Digital Money
Introduction
Payment systems are the institutional and technological arrangements through which monetary claims are transferred. They connect households, businesses, banks, payment service providers (PSPs), clearing houses, central banks and digital platforms. Their reliability is therefore central to commerce, financial inclusion and financial stability.
A payment appears simple to the customer—tap a card, scan a QR code or press Send—but the underlying process may involve authentication, authorization, message routing, fraud screening, clearing, foreign exchange, settlement and account posting. These stages must be distinguished because they create different legal obligations, costs and risks.
Digital money further complicates the landscape. Commercial-bank deposits, electronic money, stablecoins and central bank digital currencies may all be represented electronically, but they differ in issuer, redemption rights, settlement asset, governance and credit risk.
Learning Objectives
After studying this chapter, students should be able to:
Distinguish payment instruments, channels, schemes and settlement systems.
Explain authorization, clearing, settlement, finality and customer posting.
Analyse card networks, instant payments, QR payments and remittances.
Correctly apply nostro and vostro terminology in correspondent banking.
Evaluate payment pricing, liquidity needs and operational economics.
Identify fraud, cyber, credit, liquidity and operational risks.
Compare electronic money, stablecoins and central bank digital currencies.
Recommend controls and governance arrangements for payment services.
1. The Architecture of a Payment System
1.1 Instruments, channels, schemes and rails
A payment instrument is the means by which a payer initiates a transfer of monetary value. Examples include cash, cards, credit transfers, direct debits and cheques.
A channel is the interface through which an instrument is used, such as a mobile application, point-of-sale terminal, browser, ATM or QR code.
A payment scheme establishes participation rules, message standards, liability allocation and operating procedures. A card scheme, for example, governs transactions among issuers, acquirers and merchants.
A payment rail is the infrastructure that carries payment instructions and, depending on its design, supports clearing or settlement. A mobile banking application is not itself necessarily a payment rail; it may initiate transactions over an automated clearing house or real-time payment system.
Category
Examples
Principal function
Instrument
Card, credit transfer, direct debit, cheque
Initiates payment
Channel
Mobile app, POS terminal, ATM, browser
Provides customer access
Scheme
Card scheme, direct-debit scheme
Defines rules and responsibilities
Clearing infrastructure
ACH, instant-payment switch
Exchanges and calculates obligations
Settlement infrastructure
RTGS system, settlement bank
Transfers settlement assets
1.2 Payment instruments
Cash is generally a direct central-bank liability and permits face-to-face settlement without an intermediary. Its disadvantages include handling expense, theft risk and limited suitability for remote commerce.
A credit transfer is initiated by the payer, who instructs a PSP to transfer funds to a payee. Payroll and instant account-to-account payments commonly use this model.
A direct debit is initiated by the payee under authority previously granted by the payer. It is useful for recurring obligations but requires mandate controls and refund rules.
A payment card provides credentials linked to a deposit, credit or stored-value arrangement. The physical card is not money; it provides access to an underlying monetary claim or credit facility.
A cheque is a written instruction ordering a bank to pay a specified amount. Many markets have reduced cheque usage because electronic methods clear more rapidly and are easier to automate.
Electronic money, or e-money, is electronically stored monetary value issued upon receipt of funds and normally redeemable at par. The precise legal definition differs by jurisdiction.
1.3 The payment lifecycle
A typical electronic payment contains several distinct stages:
Initiation: The payer or authorized payee submits an instruction.
Authentication: The PSP verifies the claimed identity or authority of the user.
Authorization: The relevant PSP decides whether the transaction should proceed, considering funds, limits, credentials and risk rules.
Transmission and validation: Messages are formatted, routed and checked.
Clearing: Participating institutions exchange instructions and establish obligations. Clearing may occur transaction by transaction or through netting.
Settlement: Settlement assets are transferred between participating institutions to discharge interinstitutional obligations.
Customer posting: The payer’s and payee’s PSPs debit or credit customer accounts.
Reconciliation and exception handling: Institutions compare records and investigate discrepancies, returns or disputes.
Settlement must not be confused with customer posting. A payee may receive a provisional account credit before interinstitutional settlement, or an institution may settle before updating the customer-facing balance. The legal significance of each event depends on system rules and applicable law.
Payment flow showing customers, both payment service providers, clearing and interinstitutional settlement
Figure: Payment flow showing customers, both payment service providers, clearing and interinstitutional settlement
Figure: A payment message passes through both PSPs, while settlement assets move between the PSPs through settlement infrastructure—not directly to the payee.
1.4 Finality and settlement assets
Settlement finality is the point at which a transfer becomes irrevocable and unconditional under the governing rules and law. Operational completion displayed on a mobile screen does not necessarily establish legal finality.
Settlement may use:
central-bank money held in reserve or settlement accounts;
commercial-bank money at a designated settlement bank; or
another asset accepted under system rules.
Central-bank money generally minimizes settlement-asset credit risk because the settlement liability is issued by the monetary authority. It does not eliminate operational, cyber or participant-default risk.
2. Clearing and Settlement Models
2.1 Gross and net settlement
In real-time gross settlement (RTGS), payments are settled individually, usually continuously, without offsetting them against other payments. RTGS reduces the accumulation of interbank credit exposure but may require substantial intraday liquidity.
In deferred net settlement (DNS), obligations are accumulated and netted before settlement at designated times. Netting economizes on liquidity but creates exposure until settlement and may transmit a participant default through the system.
For a group of participants, institution i has net debit position:
Ni = ∑j ≠ i Pij − ∑j ≠ i Pji
where:
Pij is the value sent by institution i to institution j, measured in currency units;
the first term is total outgoing value;
the second term is total incoming value;
Ni > 0 indicates a net debtor, while Ni < 0 indicates a net creditor.
For a closed set of obligations in one currency, with every payment recorded once as outgoing and once as incoming:
∑i Ni = 0
This accounting identity does not imply that settlement is risk-free. It assumes consistent records and does not account for defaults, liquidity haircuts or foreign-exchange conversion.
Worked Example: Multilateral Netting
Bank A sends 12 million currency units to B. B sends 4 million to A and 3 million to C. C sends 2 million to A.
A: NA = 12 − (4 + 2) = 6 million, a net debtor.
B: NB = (4 + 3) − 12 = −5 million, a net creditor.
C: NC = 2 − 3 = −1 million, a net creditor.
The positions sum to zero: 6 − 5 − 1 = 0. Instead of settling gross payments worth 21 million, the system can settle a net transfer of 6 million from A, with 5 million received by B and 1 million by C, subject to system rules and successful settlement.
2.2 Liquidity and queue management
RTGS participants maintain balances or obtain intraday credit. When liquidity is insufficient, payments may queue. Advanced systems use prioritization, offsetting and liquidity-saving mechanisms. Poor liquidity management can delay time-critical payments even when an institution remains solvent.
Key management measures include payment scheduling, intraday balance monitoring, collateral planning, throughput rules and contingency funding. Liquidity optimization must not undermine prompt settlement or regulatory requirements.
3. Card Networks
3.1 Participants and transaction flow
A four-party card model typically involves:
the cardholder;
the merchant;
the issuer, which provides the card or associated account;
the acquirer, which provides merchant acceptance services; and
a card network that connects issuers and acquirers and defines scheme rules.
During authorization, the merchant sends transaction data through its acquirer and the network to the issuer. The issuer approves or declines the request. Clearing later presents transaction records and calculates obligations. Settlement transfers value among participating institutions. The acquirer then funds the merchant according to their contract.
A three-party model combines network and issuing/acquiring roles more extensively, although third-party processors may still participate.
3.2 Card economics
Merchant pricing may include a percentage fee, a fixed per-transaction charge and periodic service charges. A simplified merchant cost model is:
C = rV + fQ + F + L
where:
C = total merchant payment cost in currency units;
r = ad valorem fee rate expressed as a decimal;
V = transaction value in currency units;
f = fixed fee per transaction in currency units;
Q = number of transactions;
F = fixed periodic charges in currency units;
L = fraud, chargeback or related losses borne by the merchant.
This is a managerial cost model, not a universal scheme-pricing formula. Taxes, tiered pricing, refunds and cross-border surcharges must be added where applicable.
The effective cost rate is:
reff = C ÷ V
The ratio is dimensionless and may be expressed as a percentage, provided V > 0.
Worked Example: Merchant Acceptance Cost
A retailer processes 10,000 monthly card transactions with an average value of 32 currency units. Its contract charges 1.2% of value, 0.08 per transaction and 180 per month. Merchant-borne fraud and chargeback losses are estimated at 192.
Transaction value is V = 10,000 × 32 = 320,000. Therefore:
The calculation shows why merchants should evaluate total economic cost rather than only the advertised percentage rate.
3.3 Interchange and two-sided markets
Card networks are two-sided platforms: consumer participation increases value for merchants, while merchant acceptance increases value for consumers. An interchange fee is commonly transferred between the acquirer and issuer under network rules. Its direction and amount depend on jurisdiction, transaction type and scheme rules.
Interchange may support issuing costs, fraud protection and rewards, but high fees can increase merchant costs and retail prices. Regulation in some jurisdictions caps interchange or requires routing choice and fee transparency. Economic evaluation should consider innovation and network effects alongside market power, cross-subsidies and competitive access.
4. Real-Time and QR Payments
4.1 Real-time payments
A real-time or instant payment system generally provides near-immediate message processing, rapid confirmation and continuous or extended availability. Some systems settle each payment immediately in central-bank money; others use prefunding, periodic settlement or hybrid arrangements. Consequently, instant customer experience does not by itself prove real-time final settlement.
Benefits include rapid funds availability, improved cash management and support for digital commerce. Challenges include continuous liquidity needs, 24-hour operations and reduced time to detect or recall fraudulent payments. Credit transfers authorized by a deceived customer may be operationally valid even though induced by fraud.
Useful service measures include availability, end-to-end latency, failure rate, fraud losses per unit of value and false-positive rate. Average speed alone can conceal extreme delays, so percentile measures such as the 95th percentile are also important.
4.2 QR payments
A QR code encodes information that a device can read. It may contain a merchant identifier, account alias, payment address, amount, currency and transaction reference.
A static QR code normally contains reusable merchant information; the payer may enter the amount.
A dynamic QR code is generated for a particular transaction and can include the amount and unique reference.
In merchant-presented mode, the customer scans the merchant’s code.
In consumer-presented mode, the merchant scans a code generated by the customer’s wallet or banking application.
QR codes are interfaces, not money and not necessarily payment rails. They can initiate account transfers, card payments or wallet transactions.
Principal risks include replacement of a merchant’s static code, malicious redirection, amount manipulation, counterfeit applications and social engineering. Controls include signed payloads, verified merchant names, transaction-specific references, confirmation screens, tamper-resistant displays and reconciliation alerts.
5. Cross-Border Payments, Remittances and Correspondent Banking
5.1 Why cross-border payments are complex
A cross-border payment may require currency conversion, sanctions screening, anti-money-laundering controls, multiple message standards, correspondent banks and settlement across different time zones. Costs include explicit fees, foreign-exchange margins, intermediary deductions, compliance expense and the opportunity cost of delayed funds.
The total customer cost of a remittance should therefore include both explicit fees and the difference between the provider’s exchange rate and an appropriate benchmark rate.
Worked Example: Remittance Cost
A customer sends USD 500 and pays a USD 6 transfer fee. The benchmark exchange rate is 100 local-currency units per USD, but the provider gives 97.5.
The recipient obtains:
500 × 97.5 = 48,750 local-currency units
At the benchmark rate, the transferred principal would provide 50,000 local-currency units. The exchange-rate shortfall is 1,250 local-currency units, equivalent to:
1,250 ÷ 100 = USD 12.50
Total economic cost is 6 + 12.50 = USD 18.50, or:
18.50 ÷ 500 × 100 = 3.7%
This calculation assumes the benchmark rate is available for the same transaction time and that no additional recipient or intermediary fee applies.
5.2 Correspondent banking
A correspondent bank provides services to another financial institution, called the respondent bank, often in a market or currency where the respondent lacks direct access.
Terminology depends on perspective:
A nostro account is our account with another bank. The respondent bank calls its account maintained at the correspondent its nostro account.
A vostro account is your account with us. The correspondent bank calls that same account—held on behalf of the respondent—a vostro account.
Thus, one account can be the respondent’s nostro and the correspondent’s vostro. Reversing these perspectives creates material accounting and operational confusion.
Suppose Bank R instructs its correspondent, Bank C, to pay a beneficiary’s bank in a foreign currency. Bank C may debit Bank R’s vostro account in Bank C’s books. From Bank R’s perspective, the balance being reduced is its nostro balance at Bank C.
Correspondent chains create risks from fee opacity, delayed processing, inconsistent data, sanctions exposure and dependency on a small number of global banks. SWIFT primarily provides secure standardized financial messaging; a SWIFT message does not itself move settlement assets. Settlement occurs through account relationships or designated payment systems.
5.3 Payment-versus-payment
Foreign-exchange settlement creates principal risk when one currency is paid but the counter-currency is not received. Payment-versus-payment arrangements reduce this risk by making final transfer of one currency conditional on final transfer of the other. Coverage is limited by participating currencies, institutions, operating windows and system design.
6. Payment Risks and Controls
Payment risk is multidimensional.
Risk
Example
Selected controls
Credit risk
Participant fails before discharging an obligation
Exposure limits, collateral, prefunding
Liquidity risk
PSP cannot fund settlement when due
Intraday monitoring, liquidity buffers
Operational risk
Software or process failure
Redundancy, testing, incident management
Cyber risk
Malware or denial-of-service attack
Segmentation, encryption, monitoring
Fraud risk
Stolen credentials or authorized push-payment scam
Unauthorized fraud occurs when a criminal uses credentials or instruments without the customer’s approval. Authorized push-payment fraud occurs when a customer is deceived into authorizing a transfer. Card-not-present fraud exploits remote transactions, while account takeover involves gaining control of a customer account.
Controls should be layered. Strong customer authentication is valuable but cannot prevent every scam, especially when the customer knowingly confirms a payment under deception. Additional controls include device intelligence, transaction limits, payee-name checking, cooling-off periods, behavioural models and rapid inter-PSP information sharing.
6.2 Artificial intelligence in fraud management
Machine-learning systems can detect unusual devices, locations, transaction sequences and beneficiary networks. Their effectiveness depends on representative data, timely labels and disciplined model governance. Excessive false positives exclude legitimate customers and impose operational costs. Models must therefore be monitored for drift, explainability, bias and adversarial adaptation. Human review remains important for high-impact decisions.
6.3 Operational resilience
Resilience requires more than backup servers. PSPs should map critical services, identify dependencies, set impact tolerances, test failover procedures and coordinate incident communication. Reconciliation must continue during degraded operation, because duplicated or missing records can create financial loss even after technical service resumes.
7. Digital Money
7.1 Commercial-bank money and e-money
Most everyday digital payments transfer commercial-bank deposits. Such deposits are liabilities of commercial banks and may be protected by deposit insurance within legal limits.
E-money is generally issued after funds are received and is redeemable at par, subject to applicable law. Safeguarding or segregation rules may protect customer funds, but e-money is not automatically equivalent to an insured bank deposit. Users must assess the issuer, redemption arrangements and insolvency treatment.
7.2 Stablecoins
A stablecoin is a digital token designed to maintain a stable value relative to a reference asset, commonly a sovereign currency. Major models include:
reserve-backed stablecoins holding cash and high-quality liquid assets;
crypto-collateralized stablecoins using overcollateralization;
algorithmic arrangements attempting to stabilize price through incentives or supply adjustments.
Price stability is an objective, not a guarantee. A reserve-backed coin can lose its peg if holders doubt reserve quality, custody, liquidity or redemption capacity. If reserves must be sold rapidly, liquidity mismatches and fire-sale losses may emerge. Algorithmic designs without credible external assets are especially vulnerable to destabilizing feedback loops.
Evaluation should examine reserve composition, asset segregation, attestation or audit, redemption rights, governance, operational resilience and compliance. Public blockchain transfer does not eliminate dependence on issuers, custodians, exchanges, wallet providers and software administrators.
7.3 Central bank digital currency
A central bank digital currency (CBDC) is a digital liability of a central bank. A retail CBDC is intended for public use, whereas a wholesale CBDC is designed mainly for eligible financial institutions.
CBDC design choices include:
account-based versus token-oriented access;
direct central-bank provision versus intermediated distribution;
interest-bearing versus non-interest-bearing balances;
online-only versus limited offline functionality;
holding or transaction limits;
domestic-only versus cross-border access.
Potential benefits include resilient public money, competition, programmable service interfaces and financial inclusion. Risks include privacy intrusion, cyber concentration, operational dependence on the central bank and movement of deposits away from commercial banks during stress. Limits or tiered remuneration may reduce disintermediation but can also reduce convenience.
CBDC does not inherently require a blockchain. Technology should follow policy requirements concerning scale, privacy, resilience, finality and governance.
7.4 Comparison of digital monetary claims
Form
Issuer
Typical claim
Principal risks
Bank deposit
Commercial bank
Claim on bank
Bank credit and operational risk
E-money
Licensed e-money issuer
Redemption claim on issuer
Safeguarding and issuer risk
Reserve-backed stablecoin
Private token issuer
Contractual redemption claim
Reserve, run and governance risk
Retail CBDC
Central bank
Direct central-bank liability
Operational, privacy and policy-design risk
8. Illustrative Case: Meridian Bank’s Instant-Payment Launch
Background
Meridian Bank, a fictional mid-sized retail bank, plans to offer 24-hour instant payments through a national switch. Customers currently use batch credit transfers that settle three times each business day.
Problem
Management initially treats the project as a mobile-application upgrade. Risk staff identify broader requirements: continuous settlement liquidity, real-time sanctions screening, scam detection, customer support outside business hours and reconciliation with the national switch.
Analysis
Historical data indicate an expected 40,000 instant payments per day with an average value of 75 currency units. Expected daily value is therefore:
40,000 × 75 = 3,000,000 currency units
This amount is transaction throughput, not automatically the required liquidity buffer. Actual liquidity depends on incoming flows, timing, prefunding rules, credit facilities and the system’s liquidity-saving features.
Fraud simulation shows that a rule blocking every first payment to a new beneficiary would prevent some scams but reject many legitimate payments. The bank therefore evaluates both fraud capture and false-positive rates.
Approach
Meridian implements:
continuous treasury monitoring and threshold alerts;
dual data centres and tested switch connectivity;
confirmation of payee for eligible transactions;
risk-based limits for new devices and beneficiaries;
behavioural fraud analytics with human escalation;
automated reconciliation among customer records, switch messages and settlement accounts;
a 24-hour incident and customer-response process; and
clear disclosures explaining the finality and scam risks of instant transfers.
Outcome
The service launches with high availability and controlled liquidity usage. Scam losses do not disappear, but rapid beneficiary freezing and interbank communication improve recovery. Management also discovers that customer education is most effective when combined with transaction-specific warnings rather than generic notices.
Learning Points
A real-time payment service is an institution-wide operating model, not merely a faster front end. Speed compresses the time available for compliance, liquidity management and fraud intervention. Successful implementation requires coordinated technology, treasury, operations, legal, compliance and customer-service capabilities.
9. Regulation, Governance and Ethical Issues
Payment regulation commonly addresses licensing, safeguarding, capital, operational resilience, consumer disclosure, data protection, anti-money-laundering controls, sanctions, access and competition. Systemically important infrastructures may be subject to heightened standards because their failure could disrupt the broader financial system.
Governance must allocate responsibility for scheme rules, model risk, outsourcing, complaints, fraud reimbursement and incident reporting. Outsourcing does not transfer accountability: a regulated PSP remains responsible for services performed by processors or cloud providers.
Ethical issues include surveillance, discriminatory fraud models, exclusion of people without smartphones, opaque fees and aggressive use of transaction data. Financial inclusion requires accessible interfaces, affordable pricing, disability support and alternatives for customers with limited connectivity or digital literacy.
Privacy involves trade-offs. Complete anonymity can obstruct lawful financial-crime controls, while unlimited traceability may enable excessive surveillance. Proportionate data collection, purpose limitation, security and due process should guide design.
10. Contemporary Developments and Professional Best Practices
Payment systems increasingly adopt standardized data formats, open application programming interfaces, instant-payment connectivity and richer remittance information. Tokenized deposits and regulated stablecoins are also being explored for programmable and cross-border settlement. Interoperability remains a central challenge: technical connectivity is insufficient without aligned legal rules, identifiers, operating hours and compliance requirements.
Professionals designing or managing payment services should:
distinguish customer experience from legal and settlement finality;
map the complete end-to-end flow, including both PSPs;
maintain accurate nostro reconciliation and recognize the correspondent’s vostro perspective;
calculate total customer and merchant costs, including FX margins;
monitor intraday liquidity and participant exposures;
use layered fraud controls rather than relying on authentication alone;
test resilience across technology and third-party dependencies;
provide transparent fees, exchange rates and dispute procedures;
govern AI models for accuracy, bias and drift; and
evaluate digital money by issuer, claim, reserves, redemption and legal status.
Chapter Summary
Payment systems combine instruments, channels, schemes, clearing arrangements and settlement infrastructure. Authorization determines whether a transaction may proceed; clearing establishes obligations; settlement discharges interinstitutional obligations through settlement assets; and customer posting updates individual accounts. These events may occur at different times.
RTGS settles payments individually and limits accumulated exposure but can consume more intraday liquidity. Deferred net settlement conserves liquidity through offsetting while creating exposure until final settlement. Card systems operate as two-sided networks involving cardholders, merchants, issuers and acquirers. Their economic assessment requires total fees, fixed costs and fraud losses.
Instant and QR payments improve convenience but compress the time available for fraud intervention. Cross-border payments add foreign exchange, intermediaries and regulatory complexity. In correspondent banking, the respondent views its account at the correspondent as a nostro, while the correspondent views the same account as a vostro.
Commercial-bank money, e-money, stablecoins and CBDCs differ in issuer, redemption rights and risk. Stablecoin credibility depends on reserves, governance and redemption. CBDC is a central-bank liability whose benefits and risks depend on design. Across all payment forms, effective governance requires resilience, transparent pricing, consumer protection, liquidity management and layered fraud controls.
Key Terms
Authorization: A PSP’s decision that a transaction may proceed after relevant checks.
Clearing: Exchange and processing of payment instructions to establish obligations between participants.
Settlement: Transfer of settlement assets to discharge interinstitutional obligations.
Settlement finality: The legally defined point at which settlement becomes irrevocable and unconditional.
Payment instrument: A means used to initiate payment, such as a card or credit transfer.
Payment service provider: An institution providing payment accounts, initiation, acquiring or related services.
RTGS: Real-time gross settlement of payments individually without netting.
Deferred net settlement: Settlement of accumulated net obligations at designated times.
Interchange fee: A network-governed fee commonly transferred between acquiring and issuing sides of a card transaction.
Acquirer: A PSP that enables merchants to accept card payments.
Issuer: A PSP that provides a card or associated payment facility to a customer.
QR payment: A payment initiated using data encoded in a quick-response code.
Nostro account: From a bank’s perspective, its account held with another bank.
Vostro account: From a bank’s perspective, an account it holds on behalf of another bank.
Correspondent banking: Provision of banking and payment services by one bank to another bank.
Electronic money: Electronically stored monetary value issued upon receipt of funds and generally redeemable at par.
Stablecoin: A digital token designed to maintain value relative to a reference asset.
CBDC: A digital liability issued by a central bank.
Payment-versus-payment: A mechanism making final transfer of one currency conditional on final transfer of another.
Authorized push-payment fraud: Fraud in which deception causes a customer to authorize a payment to a criminal.
Review Questions
Short Answer Questions
Distinguish a payment instrument from a payment channel.
What is the difference between clearing and settlement?
Why is customer account posting not necessarily the same as interinstitutional settlement?
Define nostro and vostro accounts from the appropriate institutional perspectives.
What is settlement finality?
Long Answer Questions
Explain the complete lifecycle of an electronic payment from initiation to reconciliation.
Compare RTGS and deferred net settlement in terms of liquidity, credit exposure and operational requirements.
Explain the participants, flows and economics of a four-party card network.
Evaluate the benefits and risks of instant and QR payments.
Compare commercial-bank deposits, e-money, stablecoins and retail CBDC.
Analytical / Application Questions
A retailer processes 20,000 monthly transactions worth 900,000 currency units. Calculate its total and effective payment cost if pricing is 1.1% of value, 0.05 per transaction, 250 monthly and 600 in merchant-borne losses.
Map a cross-border payment through two correspondent banks, identifying whose books contain each vostro account and how the respondent describes its corresponding nostro balance.
Design a control framework for an instant-payment provider that balances fraud prevention, customer convenience, liquidity management and financial inclusion.
Multiple Choice Questions with Answers
Question 1
Which statement correctly distinguishes settlement from customer posting?
A. Settlement updates only the payee's customer balance.
B. Settlement transfers assets between participating institutions, while posting updates customer accounts.
C. Settlement is the merchant's request for authorization.
D. Settlement and customer posting must legally occur at the same instant.
Correct Answer: B. Settlement transfers assets between participating institutions, while posting updates customer accounts.
Question 2
Bank R holds an account at correspondent Bank C. Which terminology is correct?
A. Bank R calls it a vostro, and Bank C calls it a nostro.
B. Both banks call it a nostro.
C. Bank R calls it a nostro, and Bank C calls it a vostro.
D. Both banks call it a vostro.
Correct Answer: C. Bank R calls it a nostro, and Bank C calls it a vostro.
Question 3
What is the principal liquidity characteristic of RTGS compared with deferred net settlement?
A. RTGS can require more intraday liquidity because payments are settled individually.
B. RTGS eliminates every need for settlement balances.
C. RTGS settles only one net obligation at the end of each month.
D. RTGS necessarily uses private stablecoins as settlement assets.
Correct Answer: A. RTGS can require more intraday liquidity because payments are settled individually.
Question 4
In a four-party card model, which institution primarily provides card acceptance services to the merchant?
A. Issuer
B. Central bank
C. Acquirer
D. Cardholder
Correct Answer: C. Acquirer
Question 5
A merchant processes value of 200,000 currency units in 5,000 transactions. Pricing is 1% of value, 0.10 per transaction and 100 fixed. Excluding losses and taxes, what is total cost?
A. 2,100
B. 2,500
C. 2,600
D. 3,000
Correct Answer: C. 2,600
Question 6
Which statement about QR payments is correct?
A. A QR code is always a central-bank settlement rail.
B. A QR code can initiate payments over different underlying instruments or rails.
C. Static QR codes cannot be replaced by criminals.
D. Every QR payment is settled using a stablecoin.
Correct Answer: B. A QR code can initiate payments over different underlying instruments or rails.
Question 7
A remitter transfers USD 500 at a provider rate of 97.5 local units per USD. How much does the recipient obtain before any recipient-side fee?
A. 47,500 local units
B. 48,250 local units
C. 48,750 local units
D. 50,000 local units
Correct Answer: C. 48,750 local units
Question 8
Which statement best describes SWIFT in correspondent banking?
A. It is primarily a secure financial messaging network; its message does not itself transfer settlement assets.
B. It is a retail CBDC issued by multiple central banks.
C. It guarantees that every correspondent payment settles instantly.
D. It is the legal owner of all nostro account balances.
Correct Answer: A. It is primarily a secure financial messaging network; its message does not itself transfer settlement assets.
Question 9
Which feature most directly differentiates a CBDC from a privately issued stablecoin?
A. A CBDC must use a public blockchain.
B. A CBDC is a direct liability of the central bank.
C. A CBDC cannot be represented digitally.
D. A CBDC always pays interest.
Correct Answer: B. A CBDC is a direct liability of the central bank.
Question 10
Which control is particularly relevant to authorized push-payment scams?
A. Relying solely on password length
B. Removing all transaction monitoring
C. Payee-name checking combined with behavioural monitoring and targeted warnings
D. Delaying reconciliation until year-end
Correct Answer: C. Payee-name checking combined with behavioural monitoring and targeted warnings