Cross-Border QR Merchant Acceptance
A role-based map of the payment plane, from merchant-presented QR through settlement and closeout.
Operating plane
Merchant-presentedCross-border QRLocal-currency settlement
- Payment model
- Merchant-presented QR acceptance
- Funding outcome
- Merchant receives local-currency settlement
- Close condition
- Payment result, settlement evidence, and closeout evidence
What the plane covers
The cross-border QR plane connects a payer wallet or banking app, a merchant-presented QR surface, a host scheme or switch, a settlement participant, and a reconciliation service.
StableNexus normalizes the outputs from those roles so operators can treat payment result, funding progress, refunds, and closeout as one lifecycle instead of a set of disconnected handoffs.
Role model
| Role | Responsibility | Boundary |
|---|---|---|
| Merchant | Presents the QR context and needs a clear payment and closeout outcome. | Does not own inter-participant routing or evidence normalization. |
| Acceptance participant | Accepts the payment request, publishes the immediate result, and supplies post-payment updates. | Does not own final merchant funding or closeout assembly. |
| Host scheme or switch | Routes the payment through the host market and applies network-level rules. | Does not own merchant reporting inside StableNexus. |
| Settlement participant | Confirms merchant funding, timing, and settlement-facing evidence. | Does not own the merchant-presented QR experience. |
| Reconciliation service | Provides closeout evidence, batch completeness, and exception visibility. | Does not originate the payment request. |
How the payment lane fits together
A quick view of the roles that take a payment from QR presentation to settlement and closeout.
Loading diagram…