Cross-border QR merchant acceptance + local-currency settlement ops
Run Malaysia-exact cross-border QR merchant settlement with Thai payer-side PromptPay routing, MYR batch reporting, refund resolution, and evidence publication on one public operator lane.
Overview
Malaysia-exact cross-border QR merchant settlement keeps Thai payer routing, MYR batch reporting, and refund-aware close on one public lane.
Use when Malaysia is the exact merchant-settlement profile, Thailand is the live payer-side corridor, and Singapore remains a supporting public reference while QR acceptance, bank posting, batch reporting, refund resolution, and evidence publication stay on one operator lane.
Route coverage
- 6-stage QR merchant-settlement lifecycle
- Malaysia exact merchant profile, Thai payer corridor, and supporting Singapore reference posture
- Merchant-side scheme binding, payer-side routing, and callback-monitor control
- QR posting, batch reporting, gross-fee-net settlement detail, and close-window evidence
- Refund resolution, reconciliation bridge, and evidence publication
Infrastructure
- Merchant-side DuitNow acceptance, payer-side PromptPay routing, acquirer, and settlement bank stay separated
- MYR local close, FX quote reference, batch cutoff, and bank acknowledgment stay explicit
- Merchant settlement reporting, fee and net breakdown, and refund-resolution controls stay visible
- Malaysia stays the exact mounted profile while Thailand is the live payer corridor and Singapore remains supporting public context
Lifecycle stages
| Stage | Flow steps | Notes |
|---|---|---|
| Merchant Acceptance Scope | Opens the QR corridor run, resolves the exact merchant market profile, live payer corridor, and local-currency settlement boundary before any scheme call is armed; Public setup stays explicit about Malaysia as the exact mounted merchant profile, Thailand as the live payer corridor, Singapore as supporting public context, and the merchant-acquirer posture while deeper operator mappings remain request-access | |
| Scheme Linkage And Acquirer Controls | Resolve payer-side PromptPay routing, merchant-side DuitNow acceptance, acquirer posture, and route-policy controls before any QR submission is attempted; Malaysia is the exact mounted merchant profile; Thailand is the live inbound payer corridor; Singapore stays publicly visible only as a supporting reference market on the same case | MY is the exact mounted merchant profile. TH is the live inbound payer corridor on this run. SG remains supporting public reference context while deeper operator detail remains request-access. |
| Settlement Authorization And Callback Policy | Resolve the settlement actor, signed-callback posture, poll fallback, and local-currency close policy before QR movement is released; Callback delivery, authorization trace, and settlement-bank acknowledgment timing stay explicit so merchant-settlement close does not collapse into a hidden post-payment handoff | |
| Qr Submission And Movement Status | Submit the QR movement on the shared interop rail, capture payer-side confirmation, FX quote linkage, bank posting, and movement status before settlement reporting begins; Public movement evidence stays on the QR merchant lane rather than disappearing into scheme-switch operator tooling, and the downstream settlement batch identifiers stay visible | |
| Merchant Settlement Reporting | Publish the posted merchant settlement batch, capture gross-fee-net results, close-window state, and bank-acknowledgment evidence before refund or dispute review begins; Merchant settlement reporting stays visible as part of the public case instead of being hidden as a private acquirer export, and the batch structure remains explicit | |
| Refunds Reconciliation And Evidence Close | Track refund or dispute state, clear the reconciliation bridge after financial breaks are resolved, and publish the public evidence pack only after the corridor run closes with matched final-state records; The public lane stays evidence-first while request access unlocks deeper operator review without implying a private geo split, and the resolution bridge remains visible before publication |
Setup reference
| Field | Explanation | Related terms |
|---|---|---|
| Settlement amount | Sets the local-currency settlement amount carried through merchant acceptance, QR submission, settlement reporting, and reconciled close. | |
| Market profile | Sets which public market profile the workflow uses. Controls the corridor posture, route copy, and partner helper text. | |
| Settlement currency | Sets which local currency the merchant settlement closes in. Determines the closeout and settlement-report posture. | |
| Settlement path | Sets which shared QR settlement path the workflow uses. Controls the route shown for scheme status, merchant reporting, and close. | Predictable settlement |
| Corridor | Keeps the workflow tied to one corridor description so merchant acceptance, reporting, and evidence stay aligned. | |
| Callback mode | Sets whether status stays poll-only or uses signed callbacks as part of the settlement-confirmation path. | |
| Merchant scheme | Names the merchant-side QR scheme on the exact mounted profile. For this public run that is DuitNow QR on the Malaysia merchant side. | |
| Inbound payer scheme | Names the payer-side scheme on the live inbound corridor. For this mounted run that is PromptPay in Thailand. | |
| Merchant acquirer | Fixed for this case. Keeps the workflow tied to one merchant-acquirer posture so settlement reports and refund handling stay consistent. | |
| Settlement actor | Fixed for this case. Keeps the local-currency close tied to one settlement actor reference for reporting and reconciliation. |