1. Follow a payment beyond the screen
A customer sees a successful-payment message. The merchant sees a pending order. The bank has debited the customer, while the beneficiary's bank has not yet confirmed credit. These statements can coexist because a payment passes through several records and organisations. A useful legal and operational analysis begins by identifying the stage reached and the evidence supporting it, rather than treating every screen message as settlement.
The Payment and Settlement Systems Act provides the regulatory framework for payment systems in India and designates RBI as the relevant authority. It also supports settlement and netting. The Act, regulations, authorisation conditions and system-specific directions must be read together. Permission to operate a system is different from permission to participate in it, and both are different from the customer's authority for a particular payment.
For this chapter, draw a simple map containing payer, payer's bank, system arrangements, beneficiary's bank and beneficiary. Some actual arrangements contain additional service providers. For every disputed event, ask which participant generated the record, what the record establishes and what remains unresolved. This habit turns an apparently technical complaint into a sequence of manageable questions about instruction, processing, settlement and customer service.
2. System, provider and participant
A payment system enables payment between payer and beneficiary through the relevant clearing, payment or settlement services. A system provider operates the authorised system; a participant takes part in it and can have obligations under its arrangements. These roles should not be inferred solely from a brand name on an app. The visible interface may be supplied by an entity whose role differs from the system operator's role.
Imagine a shopping app integrating a payment option. The merchant, app developer, payment service entity and bank may be separate legal persons. A contract describing the developer as a technology vendor does not by itself determine every regulatory question. Examine what each entity actually does, whether it handles funds, whose records it maintains and which applicable framework governs that role.
The statutory perimeter has exclusions and special provisions, including those concerning stock exchanges and their clearing corporations. Do not extend a definition beyond its scope merely because a transaction involves securities or electronic messages. In a case answer, identify the system under discussion and its applicable legal framework before drawing conclusions about authorisation, oversight or dispute resolution.
3. Authorisation and continuing conditions
An application is not the same as an authorisation. An authorisation is not an unrestricted approval for every future product. The PSS framework addresses application, inquiry, grant or refusal, revocation and appeal. A sound operating file should identify the legal entity, permitted activity, conditions and current status. The RBI's 2026 Master Directions on Authorisation to operate a Payment System are a current source requiring consideration alongside the Act.
Suppose a company presents its incorporation certificate, a funding announcement and an acknowledgement of an application. Those documents establish different facts. Incorporation establishes a legal entity; funding may support resources; acknowledgement establishes receipt of an application. None alone proves that the proposed payment system may commence operation. A reviewer should ask for the actual authorisation and the conditions relevant to the intended business.
Continuing compliance matters after launch. A change in ownership, technology, product scope or operating arrangement may require review under the applicable instrument. Do not assume that a certificate issued years earlier answers a materially changed proposal. Equally, do not invent a requirement to obtain a completely new licence for every software update. Identify the relevant condition and the nature of the change before selecting the required process.
4. Regulation and oversight
The statutory framework provides powers concerning standards, information, inspection, audit and directions. These powers support confidence in payment arrangements that connect many participants. A weakness at one participant can affect others, particularly when obligations depend on timely settlement. Regulation therefore concerns more than the appearance of an app or the speed of an individual customer transaction.
For a practical example, a system introduces a new message format without adequately testing participants' ability to read it. Some instructions fail while others process twice. The problem involves change control, standards, reconciliation and customer outcomes. A direction to correct the system would need to be read according to its addressees, scope and effective requirements. A general statement that RBI regulates payments is not enough to establish a particular deadline or technical specification.
An officer reviewing a regulatory communication should record the source, affected service, required action, accountable owner and evidence of completion. An email saying the issue was discussed is not proof that duplicate processing stopped. Verification should use transaction evidence and controlled testing. Regulatory compliance becomes credible when the institution can demonstrate the resulting behaviour rather than merely produce a policy paragraph.
5. Clearing, gross settlement and netting
Clearing identifies and processes obligations; settlement discharges them through the relevant arrangements. In gross settlement, obligations are settled individually. Netting reduces multiple obligations to a net position under the applicable system rules. These descriptions explain the mechanics but do not mean that gross systems have no liquidity risk or that net systems eliminate credit risk.
Consider three fictional banks. Aster owes Birch INR 80, Birch owes Cedar INR 50, and Cedar owes Aster INR 30. Across the group, Aster's net position is to pay INR 50, Birch's is to receive INR 30 and Cedar's is to receive INR 20. The net positions sum to zero. The gross payment obligations total INR 160, while total net pay-ins are INR 50 in this simplified multilateral example.
The arithmetic shows potential liquidity economy. It does not show whether a particular system permits that netting, when it becomes effective, what collateral applies or what happens if Aster cannot pay. Those questions require the system's rules and statutory framework. Never describe a spreadsheet net amount as automatically enforceable netting. Legal recognition and operational mechanics must match the transaction being analysed.
6. Finality and irrevocability
Settlement finality identifies a legally significant point after which settlement has the protection provided by the applicable framework. Section 23 is a central anchor. The relevant system rules and statutory conditions matter; the customer's animation saying success is not the legal definition of that point. Finality supports certainty when participants rely on settled obligations to make other payments.
Suppose Bank A receives funds and immediately uses the resulting liquidity to meet an obligation to Bank C. If the first settlement could always be unwound without regard to the applicable rules, uncertainty would spread along the chain. This is why finality is a system-stability concept. It does not mean that a customer can never raise a complaint or that a separate compensating transaction can never be made.
Distinguish reversal, refund, chargeback and legal unwinding of settlement. A refund may create a new payment in the opposite direction. A customer remedy may operate through a scheme process. An accounting correction may address a duplicate record. The terminology matters because a statement about one mechanism should not be used to justify a conclusion about every other mechanism.
7. Liquidity, credit and operational risk
Liquidity risk is the risk of being unable to meet an obligation when due, even where resources may eventually be available. Credit risk concerns loss from a counterparty failing to meet its obligation. Operational risk can arise from people, processes, systems or external events. A participant's outage can create liquidity pressure for others, so these categories interact rather than remain isolated boxes.
Suppose a participant has enough assets but cannot access its settlement account during a system incident. Calling it solvent does not resolve the immediate payment problem. Alternatively, a participant may have functioning technology but insufficient resources because of a genuine loss. The first scenario highlights operational and liquidity arrangements; the second can involve credit exposure. Accurate classification helps select contingency actions and communication.
Controls can include access restrictions, collateral, liquidity arrangements, transaction limits, monitoring, reconciliation and tested continuity plans, according to the relevant system. No single control guarantees safety. A collateral valuation can be stale, a backup can fail or an escalation contact can be unavailable. A useful risk review asks what the control is intended to prevent and what evidence demonstrates that it can operate under stress.
8. Customer authority and failed transactions
System authorisation does not establish customer consent for an individual debit. Authentication records, mandate terms and transaction evidence matter when a customer disputes a payment. Likewise, a failed customer transaction should be classified according to its actual stage and applicable framework. Do not automatically apply a remembered compensation period from one product to every electronic payment.
Imagine the payer is debited, the merchant receives no confirmation and the customer tries again. The second attempt succeeds. A careful investigation distinguishes two separate instructions and checks whether the first ultimately failed, remained pending or also completed. Refunding one entry without tracing both references can create a further error. Preserve identifiers, timestamps, debit and credit records, reconciliation results and customer communications.
Customer service should state what is known, what is being checked and the applicable next step. Avoid promising that every pending transaction will be reversed instantly. Avoid asking the customer to share passwords or authentication secrets. Relevant turnaround times, compensation and dispute routes need their current source and product scope. This edition uses process cases rather than an unverified universal refund calculator.
9. Confidentiality, records and disputes
Payment records can expose account details, counterparties and behaviour. Access should follow role and purpose, with evidence preserved for legitimate review. Confidentiality duties do not mean that records may be hidden from a competent authority acting under the applicable power. Nor does a customer complaint justify circulating complete transaction data to every employee who might be interested.
For an internal investigation, provide the minimum records required for each reviewer and maintain a controlled evidence set. If a screenshot is used, record its source and preserve the underlying transaction reference. A screenshot can be edited or incomplete, while a system log can also contain errors. Reconcile independent records rather than treating either format as inherently conclusive.
The Act contains a dispute framework involving relevant system parties. Customer grievances can follow other applicable routes. Identify who is disputing with whom, the issue and the governing arrangement. A disagreement between participants about settlement obligations is not automatically the same as a customer's complaint about an unauthorised debit. Correct routing reduces delay and prevents the loss of material evidence.
10. Worked netting and stress case
Use the three-bank example again: Aster pays INR 50 net; Birch receives INR 30; Cedar receives INR 20. Assume, solely for the exercise, that the system permits these positions and requires funding before a stated settlement event. Aster has INR 35 available. Its immediate funding gap is INR 15. This gap is a liquidity calculation under supplied assumptions, not proof of insolvency or a legal default finding.
Now assume a collateral arrangement can supply INR 20 of usable liquidity after applying the relevant haircut. If available in time and valid for the system, that would cover the INR 15 gap and leave INR 5 headroom. If it becomes available only after settlement is due, the same amount may fail to solve the timing problem. Timing is therefore as important as the nominal amount.
Change the facts again: the collateral is subject to an unresolved prior interest. The arithmetic remains unchanged but the assumption of usability becomes doubtful. A good answer separates the calculation from the legal and operational conditions supporting it. The learning lab lets students change gross obligations and see net positions; it deliberately does not claim to model an actual payment system's default waterfall or legal finality.
11. Worked incident and control response
A fictional payment service deploys an update at noon. At 12:10 the monitoring team detects duplicate outbound messages. Customer screens show mixed statuses, and some merchants ask for a second payment. The first response should establish incident scope, preserve evidence and use authorised containment arrangements. Deleting duplicate-looking records before reconciliation can destroy the information needed to identify actual duplicate value transfers.
The investigation should separate instruction creation, message transmission, acceptance, settlement and customer posting. One instruction transmitted twice is different from two instructions authorised by the customer. A duplicate message rejected by the receiving system is different from a duplicate completed transfer. Each distinction affects the corrective action. The incident timeline should record decisions and the evidence available at each stage, including uncertainty.
After correction, test the cause and the outcome. Confirm that the faulty process has stopped, affected transactions are reconciled, customer remedies follow the applicable framework and prevention controls are improved. A successful software deployment is not by itself evidence that every customer account is correct. Closure requires both technical recovery and an evidenced resolution of the financial records affected by the incident.
12. Revision method and source discipline
Revise the chapter through four maps. The role map identifies provider, participant, customer and regulator. The event map separates instruction, clearing, settlement and posting. The risk map separates credit, liquidity and operational causes. The authority map separates statutory framework, authorisation, conditions, directions and system rules. Link every case conclusion to one of these maps before selecting an answer.
For a quick self-test, explain why netting can reduce required pay-ins without eliminating default risk. Explain why a customer refund need not contradict finality. Explain why incorporation is insufficient evidence of permission to operate a payment system. Finally, explain why a successful customer message cannot replace a reconciliation of participant records. Each answer should name the missing condition rather than rely on a slogan.
The official sources checked for this review include the PSS Act, RBI's payment-system FAQs and the 2026 authorisation directions. Detailed product-specific timelines, penalties, appeal requirements and implementation conditions remain subject to provision-level reconciliation and academic review. The review package includes the source register so the eventual publisher can verify these items against the relevant examination cutoff before releasing the lessons to students.
13. Reconcile the five records
For a payment investigation, compare the customer instruction, payer-account entry, system reference, beneficiary-bank response and beneficiary-account entry. Each record answers a different question. The instruction supports what was requested. The debit supports what happened in the payer's ledger. The system reference supports tracing. The response supports a processing event. The credit supports the beneficiary's ledger outcome. None should silently be substituted for the entire chain.
Create a small fictional incident file with two instructions for INR 500 each. One instruction has a debit and confirmed beneficiary credit; the other has a debit and no final response yet. The first appears completed on the supplied evidence. The second requires tracing and reconciliation. The total debited amount is INR 1,000, but that total does not establish that the merchant received INR 1,000. If a later credit arrives, update the status with the new evidence rather than rewriting the earlier observation.
A useful closure note states the original issue, affected references, reconciled outcomes, corrective entries and remaining follow-up. It also identifies who checked the correction. An incident can have a resolved software cause while individual transactions remain unresolved. Conversely, one customer can receive a remedy while the wider defect remains. Distinguishing those outcomes helps a bank avoid premature closure and helps students understand why settlement, posting and service recovery are related but separate. A final check asks whether every affected instruction has a documented outcome, whether the customer was told that outcome accurately and whether any remaining systemic issue has an accountable owner. Recording those answers makes closure reviewable even when several organisations participated in the original payment.
Apply the chapter
Worked reasoning
Trace instruction, system event and beneficiary records before resolving status. Different records establish different stages. Reconciliation is needed before a refund, duplicate-payment or finality conclusion.
Practice: 25 explained questions
Answers can be saved in this browser.
Choose answers, then check.
Sources and review
- PMLA statutory explanation and sections · checked 2026-11-08
- Maintenance of Records Rules · checked 2026-11-08
- Commercial Banks KYC Directions, 2025 · checked 2026-11-08
- FIU-IND institutional role · checked 2026-11-08
- Negotiable Instruments Act, 1881 · checked 2026-11-08
- CAIIB Rules and Syllabus 2026 · checked 2026-11-08
- Miscellaneous forex facilities FAQ · checked 2026-11-08
- Foreign Currency Accounts by Resident Individuals · checked 2026-11-08
- Foreign Exchange Management (Authorised Persons) Regulations, 2026 · checked 2026-11-08
- Payment and Settlement Systems Act, 2007 · checked 2026-11-08
- Payment and Settlement Systems Act FAQ · checked 2026-11-08
- Master Directions on Authorisation to operate a Payment System · checked 2026-11-08
- Transfer of Property Act, 1882 · checked 2026-11-08
- Indian Contract Act, 1872 · checked 2026-11-08
- Companies Act, 2013 · checked 2026-11-08
Original examples; independent academic review and website UAT pending.