Digital Payments and Money Movement

Introduction

Digital payments are the mechanisms through which value is initiated, authorized, cleared, settled, reconciled, and recorded electronically. They are not a single technology. A card purchase, a mobile-wallet transfer, a bank credit transfer, and a cross-border remittance may appear similar to a customer, yet they rely on different legal claims, messaging standards, risk controls, intermediaries, and settlement arrangements.

For financial managers, the central issue is therefore not merely whether a payment is fast or convenient. It is whether the payment infrastructure delivers reliable finality, acceptable risk, transparent economics, regulatory compliance, and scalable connectivity. Payment design affects liquidity, working capital, fraud losses, customer experience, treasury operations, and the competitive position of banks and fintech firms.

This chapter examines cards, account-to-account transfers, real-time payments, wallets, merchant acquiring, payment gateways, cross-border payments, and ISO 20022. It then integrates these components through payment-flow analysis, fee economics, settlement risk, chargebacks, and payment orchestration.

Learning Objectives

By the end of this chapter, students should be able to:

1. Distinguish major payment instruments, schemes, participants, and settlement models.
2. Map the authorization, clearing, settlement, and reconciliation stages of a payment.
3. Explain the economics of issuing, acquiring, gateways, wallets, and account-to-account transfers.
4. Assess fraud, credit, liquidity, operational, settlement, and chargeback risks.
5. Analyze cross-border payment constraints and the role of ISO 20022.
6. Evaluate payment orchestration strategies using financial, technical, and governance criteria.

1. The Architecture of a Payment

A payment involves at least two economic parties: a payer and a payee. In practice, additional institutions provide accounts, payment instruments, authentication, messaging, risk management, clearing, and settlement.

A useful distinction is between four stages:

• Initiation: the payer gives an instruction through a card, bank application, wallet, terminal, web checkout, or other channel.
• Authorization: the relevant institution decides whether the transaction may proceed, often using authentication, balance checks, limits, and fraud controls.
• Clearing: transaction information is exchanged, validated, calculated, and prepared for settlement. Clearing may be immediate or batch-based.
• Settlement: funds are transferred between participating institutions, creating the final inter-institutional discharge of obligations, subject to the rules of the relevant system.

Customer confirmation is not necessarily settlement. A card authorization can be approved while the merchant receives funds later. Similarly, a real-time customer credit may occur before all back-end reconciliation and liquidity processes are complete.

Principal participants

Figure: A simplified payment flow. Actual participants and sequence vary by instrument and jurisdiction.

2. Cards and Merchant Payments

A card payment normally uses a four-party model: cardholder, issuing institution, acquiring institution, and merchant. A card scheme supplies rules, network connectivity, dispute procedures, and pricing arrangements. In a three-party model, one organization may perform both issuing and acquiring functions.

Card transactions commonly pass through these steps:

1. The merchant captures card details or receives a token from a wallet.
2. The acquirer or gateway forwards an authorization request.
3. The issuer authenticates the transaction and evaluates available credit or funds and fraud indicators.
4. An approval or decline is returned.
5. The merchant later submits authorized transactions for clearing.
6. Net obligations are calculated and settled.
7. The merchant receives proceeds, less applicable fees and adjustments.

A transaction may be card-present, such as a contactless terminal payment, or card-not-present, such as an online purchase. Card-not-present transactions generally require stronger controls because the physical card and customer may not be observed directly. Tokenization, device binding, cryptographic authentication, and behavioural analytics reduce exposure of primary account numbers.

Card economics

The merchant discount rate is the total amount deducted from a merchant transaction, although its components vary by market and contract. Conceptually:

The expression is an economic decomposition rather than a universal billing formula. Interchange is commonly transferred between issuer and acquirer, while scheme and processor charges support network and processing services. Pricing may also include fixed per-transaction fees, gateway fees, monthly fees, currency-conversion charges, fraud tools, and chargeback fees.

If transaction value is V and the merchant discount rate is r, with fixed fee f per transaction, the merchant’s net proceeds before taxes and other adjustments are:

Here V and f are in the same currency, and r is expressed as a decimal. The formula applies to a simple percentage-plus-fixed-fee arrangement and excludes refunds, reserves, rolling holds, and later disputes.

For example, on a transaction of 100 currency units with r = 1.8% and f = 0.20, net receipt equals 100(1 − 0.018) − 0.20 = 97. ...

Actually, 100 × 0.982 = 98.20; after the fixed fee, the merchant receives 98.00 currency units.

3. Account-to-Account Transfers and Real-Time Payments

Account-to-account (A2A) payments move funds directly between payment accounts rather than using a card account as the primary payment instrument. They may be initiated by online banking, open-banking interfaces, QR codes, mobile applications, or payment links.

A2A systems differ in speed, settlement model, operating hours, participant access, and customer protection. Some operate in deferred net settlement, in which obligations are accumulated and settled at intervals. Others use real-time gross settlement or a fast-payment arrangement in which the receiving account is credited within seconds.

Real-time payments (RTP) generally provide continuous or near-continuous availability, rapid message processing, and immediate or near-immediate funds availability. Speed creates managerial benefits—lower merchant waiting time, improved cash conversion, and reduced reconciliation delay—but also creates risk. A fraudulent or mistaken payment may be difficult to recall after finality.

Important RTP design questions include:

• Is participation direct, indirect, or sponsored?
• When does legal finality occur?
• Who supplies intraday liquidity?
• Are proxy identifiers, aliases, or confirmation-of-payee services available?
• What liability applies to authorized push-payment fraud?
• How are sanctions screening and fraud monitoring performed without excessive delay?

A payment that is technically instant can still involve delayed accounting, suspense accounts, liquidity adjustments, or post-transaction investigations. Managers must therefore distinguish customer experience from the complete operating lifecycle.

4. Digital Wallets

A wallet is an interface or account structure that enables storage, representation, or use of payment credentials or value. Wallets can be classified as:

• Pass-through wallets, which store tokenized cards or bank-account credentials but do not hold customer funds directly.
• Stored-value wallets, in which customer balances represent claims on the wallet provider or a safeguarding institution.
• Account-linked wallets, which initiate payments from a bank or other underlying account.
• Closed-loop wallets, usable only within a defined merchant or platform ecosystem.

Wallet economics depend on funding costs, interchange or transfer fees, merchant acceptance, float or safeguarding rules, fraud losses, customer acquisition, and platform monetization. A wallet may improve conversion by reducing checkout friction, but it can also create concentration risk and dependence on a dominant platform.

Key controls include customer identification, transaction monitoring, device and credential security, limits, safeguarding of customer funds, segregation of duties, recovery procedures, and transparent terms for refunds and account closure.

5. Gateways, Acquiring, and Payment Orchestration

A payment gateway is a technical connectivity layer between a merchant or platform and payment processors or schemes. It may handle encryption, tokenization, routing, authentication, response formatting, and reporting. A gateway does not necessarily hold funds or assume the full obligations of an acquirer.

An acquirer provides merchant acceptance, underwriting, settlement, transaction submission, and often dispute administration. Acquiring risk is significant because the merchant may fail after receiving funds, deliver defective goods, or generate fraud and chargebacks. Acquirers may therefore impose reserves, delayed settlement, transaction limits, or enhanced due diligence.

Payment orchestration is the coordinated management of multiple payment methods, processors, acquirers, routing rules, fraud controls, retries, reconciliation, and reporting through an integrated decision layer. A robust orchestration platform should support:

• method and currency selection;
• routing by geography, cost, issuer, risk, or availability;
• controlled retries that do not duplicate a payment;
• idempotency and unique transaction references;
• token portability where legally and technically possible;
• centralized reconciliation;
• dispute and refund workflows;
• real-time monitoring and failover;
• audit trails for routing decisions.

Routing solely to the lowest nominal fee can be inefficient. A processor with a lower fee but higher decline rate, slower settlement, or greater outage frequency may produce lower total economic value.

A practical expected-cost model is:

Each component must be estimated consistently per transaction or per unit of payment value. The formula is a management framework, not an accounting standard; it is useful only when costs are defined and measured comparably.

6. Fees, Settlement Risk, and Chargebacks

Payment pricing contains both explicit and implicit elements. Explicit costs include percentage fees, fixed fees, foreign-exchange margins, gateway charges, assessment fees, and dispute fees. Implicit costs include declined sales, delayed settlement, reserve requirements, operational labor, fraud, reconciliation exceptions, and customer-support contacts.

Settlement risk

Settlement risk is the possibility that one party performs its obligation while the counterparty fails to deliver the expected funds or finality. It can arise from participant insolvency, operational disruption, liquidity shortages, time-zone differences, correspondent-bank failure, or legal uncertainty.

Relevant distinctions include:

• Credit risk: a counterparty cannot meet its obligation.
• Liquidity risk: a counterparty may be solvent but unable to pay at the required time.
• Principal risk: the full value of one side may be lost before the other side is received.
• Operational risk: systems, processes, people, or external events disrupt payment execution.
• Herstatt or time-zone risk: one currency is delivered before the corresponding currency is received.

Controls include prefunding, collateral, netting, central-bank settlement, exposure limits, participant monitoring, business continuity, reconciliation, and legally clear finality rules.

Chargebacks and disputes

A chargeback reverses or conditionally reverses a card transaction under scheme rules. Common causes include unauthorized use, duplicate processing, non-receipt, defective goods, processing errors, and fraud claims. A refund is normally initiated by the merchant; a chargeback is initiated through the issuer and scheme dispute process.

A merchant’s chargeback ratio may be expressed as:

The numerator and denominator must follow the applicable scheme’s definitions and observation period. A value-based ratio may instead divide chargeback value by sales value. These measures are not interchangeable.

Effective dispute management requires evidence capture at authorization and fulfillment: customer authentication results, delivery confirmation, device data, terms acceptance, communication records, and refund history. Excessive evidence collection can create privacy and retention risks, so data minimization and lawful purpose are essential.

7. Cross-Border Payments

Cross-border payments are more complex because they combine multiple jurisdictions, currencies, regulatory regimes, clearing systems, and legal relationships. A typical transfer may involve the sending institution, one or more correspondent banks, a messaging network, a foreign exchange provider, and the receiving institution.

The total cost to a customer may include:

The expression is useful for analysis but actual fee allocation may be shared, deducted from principal, or embedded in an exchange rate. The customer may therefore observe a nominally low fee while receiving a less favourable conversion rate.

Cross-border systems face several frictions:

• inconsistent identifiers and data fields;
• different sanctions and anti-money-laundering obligations;
• correspondent-bank concentration;
• limited operating hours and cut-off times;
• foreign-exchange volatility;
• fragmented consumer protection;
• returns, investigations, and data-quality failures.

Managers should compare not only price but also speed, transparency, traceability, rejection probability, beneficiary reach, liquidity requirements, and legal enforceability.

8. ISO 20022 and Payment Data

ISO 20022 is a standard methodology for developing interoperable financial messages. It provides a common business vocabulary and structured message models rather than being merely a file format or a single network. Implementations may use XML or other representations according to scheme and market requirements.

Structured data can improve straight-through processing, sanctions screening, reconciliation, fraud analytics, and regulatory reporting. Examples of useful information include end-to-end transaction identifiers, structured creditor and debtor details, remittance information, purpose codes, and ultimate-party data.

Migration is not automatically beneficial. Institutions must map legacy fields, manage truncation, validate data quality, preserve backward compatibility, and prevent inconsistent interpretations. A message can be syntactically valid but operationally incomplete. Governance must therefore define mandatory fields, exception handling, ownership, and controls over enrichment.

ISO 20022 should be understood as an interoperability and data-governance opportunity. It does not by itself guarantee faster settlement, lower fees, better fraud detection, or universal interoperability.

9. A Worked Payment-Flow Analysis

Consider an online retailer that accepts cards and instant bank payments. A customer purchases goods for 250 currency units.

For a card transaction, the acquirer charges 1.6% plus 0.15 units. The simple merchant receipt is:

If a later refund occurs, the retailer may recover some or none of the original fee depending on its contract. If a chargeback occurs, the retailer may lose the sale value, the goods, a dispute fee, and internal investigation costs.

Suppose an instant bank payment costs 0.30 units, but its conversion rate is 2 percentage points lower than the card channel. If 1,000 customers are presented with each method, the manager must not compare only 0.30 with the card fee. The analysis should include acceptance rate, abandonment, fraud, refunds, settlement timing, customer support, and working-capital effects. A cheaper method that customers distrust may generate less profit than a more expensive method with materially higher completion.

The correct managerial metric is contribution after all relevant channel effects, not the headline transaction fee.

10. Illustrative Case: Meridian Marketplace

Background. Meridian is a fictional regional marketplace operating in three countries. It accepts cards, local instant payments, and two digital wallets. Its payment volume has grown rapidly, but its finance team reports unpredictable settlement dates, rising chargebacks, and difficult monthly reconciliation.

Problem. Meridian uses separate gateways in each country. Transaction identifiers are not consistent across gateways, refunds are processed manually, and the treasury team cannot reliably forecast when funds will arrive. A wallet provider has also experienced a temporary outage, causing abandoned checkouts.

Analysis. The firm maps each payment from initiation through authorization, capture, clearing, settlement, refund, and dispute. It discovers that “successful” customer responses mean authorization only for some card flows, while bank-payment success means credited funds for another flow. It also finds that processor reports use different time zones and that several gateways truncate remittance information.

Approach. Meridian establishes a common internal transaction ID and idempotency key. It introduces an orchestration layer that routes by country, currency, availability, and risk rather than price alone. It adds confirmation-of-payee controls where available, maintains a secondary acquirer, standardizes ISO 20022-compatible internal data fields, and reconciles authorization, capture, settlement, refund, and chargeback events separately. Treasury receives a settlement forecast based on contractual settlement windows and historical exceptions.

Outcome. In this illustrative scenario, reconciliation becomes more timely, outage-related abandonment falls, and management can distinguish technical declines from fraud declines and insufficient funds. The firm does not eliminate risk: routing complexity increases governance requirements, and multiple processors create additional third-party dependencies.

Learning points. First, payment success must be defined at the correct lifecycle stage. Second, data standards are valuable only when identifiers and ownership are governed. Third, resilience requires tested alternatives, not merely contractual promises. Fourth, the optimal payment channel balances cost, conversion, risk, settlement, and customer protection.

11. Governance, Regulation, and Ethics

Payment institutions operate within rules concerning licensing, safeguarding, capital or liquidity, anti-money laundering, sanctions, consumer protection, privacy, cybersecurity, operational resilience, and outsourcing. Requirements differ by jurisdiction, but the control principles are broadly comparable.

Managers should ensure that:

• customer funds are legally protected and reconciled;
• pricing and foreign-exchange conversion are transparent;
• authentication and fraud controls do not unfairly exclude legitimate users;
• automated decisions are explainable enough for complaints and oversight;
• personal data are collected proportionately and retained appropriately;
• third-party providers are subject to due diligence and concentration limits;
• incidents, outages, and material changes are reported under applicable rules;
• records support audit, dispute resolution, and regulatory investigation.

Artificial intelligence can assist fraud detection, merchant risk scoring, routing, and customer-support triage. However, models can generate false positives, discriminate against particular groups, become vulnerable to adversarial behaviour, or obscure accountability. Model governance should include data-quality testing, performance monitoring, human escalation, threshold review, drift detection, and documentation of adverse outcomes.

12. Contemporary Developments and Best Practices

Important developments include account-to-account commerce, open-banking payment initiation, tokenized credentials, digital identity, request-to-pay services, embedded payments, programmable interfaces, central-bank digital-currency research, and increasing use of structured payment data. These developments should be evaluated by function rather than novelty.

Best practices include:

1. Map every payment lifecycle and define the meaning of each status.
2. Separate authorization, capture, settlement, refund, and dispute data.
3. Use idempotency keys and unique identifiers to prevent duplicate payments.
4. Reconcile independently generated records rather than relying on a single report.
5. Measure total cost, approval rate, fraud, chargebacks, liquidity, and outage impact.
6. Design customer authentication and confirmation controls proportionately to risk.
7. Maintain tested failover and incident-response procedures.
8. Govern processors, gateways, wallets, and cloud providers as critical third parties.
9. Use structured data standards with explicit mapping and validation rules.
10. Treat payment orchestration as a controlled financial decision system, not only as software routing.

Chapter Summary

Digital payments are multi-stage institutional processes involving initiation, authorization, clearing, settlement, reconciliation, and exception handling. Cards rely on issuing, acquiring, schemes, and dispute rules; A2A and real-time payments rely on account infrastructure, liquidity, finality, and fraud controls; wallets provide credential, account, or stored-value functionality. Gateways provide technical connectivity, while acquirers assume important merchant and settlement responsibilities.

Payment economics extend beyond headline fees. Declines, fraud, chargebacks, reserves, foreign-exchange spreads, settlement timing, and operational work all affect contribution. Cross-border payments add currency, jurisdiction, correspondent, compliance, and data challenges. ISO 20022 improves the potential quality and interoperability of payment data but requires disciplined migration and governance.

Payment orchestration can improve resilience, conversion, and control when routing, retries, tokenization, reconciliation, and dispute processes are centrally governed. The most effective payment strategy balances cost, speed, finality, risk, customer protection, regulatory obligations, and operational resilience.

Key Terms

Payment authorization: Approval of a payment instruction under specified controls.

Clearing: Exchange and processing of payment information and calculation of obligations.

Settlement: Transfer of funds between institutions to discharge obligations.

Issuer: Institution that provides a payment card or account to the payer.

Acquirer: Institution that provides merchant acceptance and submits transactions for processing.

Payment scheme: Network and rule system governing a payment method.

Payment gateway: Technical connection between merchants and payment processors or networks.

Account-to-account payment: Transfer directly between payment accounts.

Real-time payment: Payment processed with near-immediate messaging and funds availability.

Digital wallet: Interface or account structure holding credentials, value, or access to an account.

Tokenization: Replacement of sensitive payment credentials with a substitute token.

Chargeback: Scheme-based reversal or dispute of a card transaction.

Settlement risk: Risk that expected payment performance or finality will not occur.

Interchange: Transfer or fee commonly associated with card transactions between issuer and acquirer.

Payment orchestration: Coordinated routing and management of payment methods and providers.

ISO 20022: International methodology and message model for structured financial information.

Idempotency: Property that repeated processing of the same request does not create duplicate effects.

Correspondent bank: Bank that provides payment or settlement services for another bank, often cross-border.

Straight-through processing: Automated processing with minimal manual intervention.

Confirmation of payee: Service that checks whether beneficiary details correspond to the intended recipient.

Review Questions

5 Short Answer Questions

1. What is the difference between authorization and settlement?
2. Identify the main participants in a four-party card model.
3. Why can real-time payments increase operational and fraud risk?
4. Distinguish a payment gateway from an acquirer.
5. What problems can structured ISO 20022 data help solve?

5 Long Answer Questions

1. Explain the economics of a card transaction and distinguish explicit fees from implicit costs.
2. Compare cards, A2A transfers, real-time payments, and wallets in terms of speed, risk, settlement, and customer experience.
3. Discuss the principal forms of settlement risk in cross-border payments and the controls available to institutions.
4. Explain how payment orchestration can improve resilience and conversion while creating new governance challenges.
5. Evaluate the benefits and limitations of ISO 20022 migration for a multinational financial institution.

3 Analytical / Application Questions

1. A retailer is considering a card processor with a lower percentage fee but a higher decline rate and slower settlement. Design a decision framework that incorporates conversion, fraud, chargebacks, liquidity, and outage risk.
2. Map the lifecycle of an online card transaction from customer initiation through possible refund and chargeback. Identify at least five control points.
3. A cross-border fintech experiences inconsistent beneficiary data, sanctions-screening delays, and unexplained foreign-exchange costs. Diagnose the likely operational causes and propose a staged remediation plan.

Multiple Choice Questions with Answers

Question 1

Which stage primarily involves the transfer of funds between participating institutions?

A. Initiation

B. Authorization

C. Settlement

D. Authentication

Correct Answer: C. Settlement

Question 2

In a four-party card model, which institution normally provides the merchant with acceptance services?

A. Issuer

B. Acquirer

C. Cardholder

D. Beneficiary bank

Correct Answer: B. Acquirer

Question 3

A transaction has a value of 100 currency units, a percentage fee of 1.8%, and a fixed fee of 0.20. What is the merchant’s receipt before other adjustments?

A. 97.80

B. 98.00

C. 98.20

D. 99.80

Correct Answer: B. 98.00

Question 4

Which statement best describes a payment gateway?

A. It is always the institution that holds customer deposits.

B. It is a technical connectivity layer linking merchants to payment services.

C. It guarantees that every transaction will settle finally.

D. It is the customer’s card-issuing institution.

Correct Answer: B. It is a technical connectivity layer linking merchants to payment services.

Question 5

What is a principal concern with an irrevocable real-time payment?

A. The payment cannot be initiated electronically.

B. The payment may be difficult to recall after fraud or error.

C. The payment always requires a card network.

D. The payment cannot be reconciled.

Correct Answer: B. The payment may be difficult to recall after fraud or error.

Question 6

Which item is an example of settlement risk?

A. A customer forgetting a password

B. A merchant changing its logo

C. A counterparty failing to deliver funds after the other side has performed

D. A customer viewing a payment receipt

Correct Answer: C. A counterparty failing to deliver funds after the other side has performed

Question 7

What is the primary purpose of tokenization in card payments?

A. To replace sensitive payment credentials with a substitute value

B. To eliminate all transaction fees

C. To guarantee exchange-rate stability

D. To convert a card payment into cash

Correct Answer: A. To replace sensitive payment credentials with a substitute value

Question 8

Which statement about ISO 20022 is most accurate?

A. It is only a card authorization protocol.

B. It guarantees lower payment prices.

C. It provides a structured methodology and vocabulary for financial messages.

D. It eliminates the need for data governance.

Correct Answer: C. It provides a structured methodology and vocabulary for financial messages.

Question 9

A chargeback is best distinguished from a normal merchant refund because a chargeback is generally:

A. Initiated through the issuer and scheme dispute process

B. Always voluntary and initiated by the merchant

C. A currency conversion service

D. A settlement message standard

Correct Answer: A. Initiated through the issuer and scheme dispute process

Question 10

Why should payment orchestration not route solely according to the lowest nominal fee?

A. Nominal fees are legally prohibited.

B. A lower fee may be offset by declines, fraud, outages, or slower settlement.

C. Routing rules cannot use cost information.

D. All processors have identical performance.

Correct Answer: B. A lower fee may be offset by declines, fraud, outages, or slower settlement.