PA-12: Cross-border payments

PA-12: Cross-border payments: Paragraph-level professional implementation page for Payment Aggregators.

RBI Payment Aggregator DirectionsSource date: 15 September 2025Payment Operations

Finin2min Summary

PA-12: Cross-border payments is rebuilt as a practitioner page for payment operations under RBI Payment Aggregator Directions.
For Cross Border Payments, the official source is the RBI page for Payment aggregators, with the source date shown as 15 September 2025. The page uses that source family instead of copying unrelated banking directions across the hub.
For implementation, read the source with the route-specific focus on Cross Border Payments, then preserve the evidence set: authorisation file, merchant KYC, escrow reconciliation, settlement register, chargeback records, cyber audit and compliance returns.

Bare Law and Source Map

Page focus	Cross Border Payments
Controlling source family	Payment aggregators
Legal authority	RBI Payment Aggregator Directions
Audience	payment aggregators, merchants, escrow banks, information security, operations, finance, customer support and compliance
Payment aggregators	https://www.rbi.org.in/Scripts/BS_ViewMasDirections.aspx?id=12896 primary RBI source; date: 15 September 2025
https://www.rbi.org.in/Scripts/BS_ViewMasDirections.aspx?id=13502	https://www.rbi.org.in/Scripts/BS_ViewMasDirections.aspx?id=13502 linked RBI source
https://www.rbi.org.in/Scripts/BS_ViewMasDirections.aspx?id=12715	https://www.rbi.org.in/Scripts/BS_ViewMasDirections.aspx?id=12715 linked RBI source
Payment and Settlement Systems Act, 2007	https://financialservices.gov.in/payment-and-settlement-systems-act-2007 linked RBI source

Instrument or source for Cross Border Payments: Payment aggregators. It should be opened from RBI before relying on this route in a live filing, audit or client note.
Authority: RBI Payment Aggregator Directions. The page focus is Cross Border Payments, so the relevant bare-law reading starts with that authority and then moves to the specific RBI direction, circular or press release.
Core source anchors for Cross Border Payments are authorisation, scope, governance, net-worth and fit-and-proper controls; merchant onboarding, KYC, monitoring, prohibited activity and cross-border controls; escrow account, permitted flows, settlement timelines and reconciliation. The remaining controls should be checked against the source table of contents and any linked RBI amendment direction.
Evidence posture for Cross Border Payments: RBI-facing compliance is not complete until authorisation file, merchant KYC, escrow reconciliation, settlement register, chargeback records, cyber audit and compliance returns are retained in an auditable file.

Section-wise / Para-wise Decode

Scope decode: Cross Border Payments belongs to the Payment aggregators source family; confirm the regulated entity, product, customer class and transaction date before applying a control.
Applicability decode for Cross Border Payments: authorisation, scope, governance, net-worth and fit-and-proper controls sets the first gate. If the entity, product or customer falls outside that gate, keep the source open and document why the rule does or does not apply.
Operational decode for Cross Border Payments: merchant onboarding, KYC, monitoring, prohibited activity and cross-border controls should be converted into a control owner, system field, maker-checker point, exception path and proof of completion.
Evidence decode for Cross Border Payments: escrow account, permitted flows, settlement timelines and reconciliation needs timestamped support, not only a policy assertion.
Linked-paragraph decode for Cross Border Payments: customer disclosures, refunds, disputes, chargebacks and service-provider oversight is the area most likely to create audit questions for this route, because it ties the legal rule to customer, transaction or reporting evidence.
Closure decode for Cross Border Payments: data security, card credential controls, audit, reporting and change control completes the file by proving that the obligation is monitored after the initial approval or filing.

Linked Rules, Circulars and Notifications

Primary RBI source for Cross Border Payments: Payment aggregators (15 September 2025).
Statutory layer: RBI Payment Aggregator Directions. Use the official statute or RBI source link in the source section before citing a provision externally.
Operational layer for Cross Border Payments: authorisation, scope, governance, net-worth and fit-and-proper controls and merchant onboarding, KYC, monitoring, prohibited activity and cross-border controls should be reconciled with internal policy, board delegation and system configuration.
Reporting and audit layer for Cross Border Payments: source data, exceptions and supervisory returns must be reconciled before sign-off.
Related source: https://www.rbi.org.in/Scripts/BS_ViewMasDirections.aspx?id=13502.
Related source: https://www.rbi.org.in/Scripts/BS_ViewMasDirections.aspx?id=12715.
Related source: Payment and Settlement Systems Act, 2007.

For reliance, check the official RBI source, any RBI amendment direction, press release, master circular, CMS/return portal instruction and the current internal policy mapped to this page.

Workflow / Flow Chart

Step 1Classify the entity, product and transaction for Cross Border Payments.
Step 2Open the official source page and mark the paragraphs that control payment operations.
Step 3Build the evidence file using authorisation file, merchant KYC, escrow reconciliation, settlement register, chargeback records, cyber audit and compliance returns.
Step 4Assign owner, reviewer, due date, exception threshold and escalation path.
Step 5Test the control against one live file or return and record gaps.
Step 6Close with board, committee, compliance or senior management sign-off where the source requires governance oversight.

Practical Examples

A regulated entity prepares a product or process change touching Cross Border Payments. The compliance team first maps the RBI source, then checks whether the existing board policy and system rules already cover the change.
An internal audit sample finds a mismatch between source data and the evidence retained for Cross Border Payments. The file should show the source paragraph, the responsible owner, the exception approval and the remediation date.
A customer, merchant, borrower or counterparty complains about Cross Border Payments. The response file should connect the complaint facts to Payment aggregators and preserve communication, decision and escalation evidence.

Highlighted Points

Do not rely on the route label alone; Cross Border Payments must be matched to the RBI source, entity type and transaction date.
The most audit-sensitive risk on this page is merchant onboarded without diligence, escrow mismatch, late settlement, unsafe card credential handling, unresolved chargeback or unauthorised cross-border flow.
RBI-facing evidence is stronger when it connects policy, system configuration, maker-checker action, exception approval and customer or regulatory communication.
Related pages in this hub should be used only as cross-links; the source listed for Payment aggregators remains the controlling reference for this page.

Exam and Advisory Case Studies

Exam case study for PA-12: Cross-border payments: a fact pattern gives an entity, product, customer and date involving Cross Border Payments. Start with applicability, identify the RBI source, name the control failure and list the evidence that would prove compliance.

Advisory case study for PA-12: Cross-border payments: management wants to sign off Cross Border Payments before launch or filing. The practical answer is to confirm the source paragraph, board approval, data controls, exception handling and customer or regulatory communication pack.

Q&A

What is the first check for Cross Border Payments?

Confirm the regulated entity, product, customer or counterparty, transaction date and the official RBI source: Payment aggregators.

Can this page replace the RBI source?

No. It is a structured Finin2min working guide. The official RBI source and linked statute remain controlling for legal reliance.

What evidence should be kept?

For Cross Border Payments, at minimum keep authorisation file, merchant KYC, escrow reconciliation, settlement register, chargeback records, cyber audit and compliance returns, plus any board or committee approval and regulatory filing acknowledgement that applies to the fact pattern.

When should the page be revisited?

Revisit it after an RBI amendment, inspection finding, product change, outsourcing change, system migration, customer-impact event or supervisory return change.

Working Checklist

Open the official RBI source for Payment aggregators.
Record why Cross Border Payments applies to the entity and transaction.
Map each control to owner, evidence, reviewer and escalation route.
Attach authorisation file, merchant KYC, escrow reconciliation, settlement register, chargeback records, cyber audit and compliance returns to the working file.
Check linked RBI directions, notifications, circulars, supervisory-return pages and CMS/complaint sources where relevant.
Close open exceptions through board, committee, compliance, risk or audit governance before external reliance.

Primary Official Sources

Payment aggregatorsprimary RBI source; date: 15 September 2025
https://www.rbi.org.in/Scripts/BS_ViewMasDirections.aspx?id=13502linked RBI source
https://www.rbi.org.in/Scripts/BS_ViewMasDirections.aspx?id=12715linked RBI source
Payment and Settlement Systems Act, 2007linked RBI source
RBI Master Directions indexofficial RBI index