Cross-Border QR Merchant Acceptance
Governed merchant-close workflow from QR presentation through settlement posting, batch admission, merchant reporting, and evidence close.
Cross-border QR merchant acceptance
The full lane from payer action to merchant-close certainty, with immediate result, settlement posting, batch admission, merchant reporting, adjustment handling, reconciliation, and evidence publication as distinct governed steps.
StableNexus normalizes outputs from the acceptance participant, the settlement participant, and the reconciliation service into one operating record so merchant-presented QR close stays readable end to end.
Actor-lane operating map
Seven actors on one normalized lane.
Canonical chapters
| Chapter | Outcome | Lifecycle states |
|---|---|---|
| Corridor scope and readiness | Corridor participants, scope, and readiness controls are defined. | corridor_ready |
| Scheme linkage and settlement policy | Scheme linkage, merchant acceptance controls, and settlement policy are established. | route_bound |
| Payment submission and immediate result | The QR payment is submitted and an immediate result is returned. | payment_submitted, payment_accepted, payment_rejected |
| Settlement posting and batch admission | Settlement posting is recorded and batch admission status is visible. | settlement_posting_pending, settlement_posted, batch_admission_pending, batch_admitted, adjustment_required |
| Merchant reporting and close window | Merchant reporting is published and close-window state is available. | report_published, close_window_open |
| Refund, reconciliation, and evidence close | Refund handling, reconciliation, and evidence close are completed. | refund_open, reconciliation_signed, evidence_published |
Phase map
How the six chapters sequence.
Lifecycle states
Settlement posting, batch admission, reporting, and evidence close stay distinct.
Artifact and evidence matrix
| Chapter | Runtime artifacts | Docs-derived surfaces |
|---|---|---|
| Corridor scope and readiness | participant_readiness_snapshot | readiness_packet |
| Scheme linkage and settlement policy | merchant_acceptance_profile, scheme_linkage_snapshot | settlement_policy_state |
| Payment submission and immediate result | qr_transaction_trace | payment_trace |
| Settlement posting and batch admission | settlement_posting_snapshot | posting_reference, batch_admission_state | Evidence: settlement_posting_reference, batch_admission_snapshot |
| Merchant reporting and close window | merchant_settlement_report | merchant_report_packet, close_window_state |
| Refund, reconciliation, and evidence close | refund_or_dispute_log, reconciliation_close_pack | refund_case_state, reconciliation_signoff_state |
Control overlay matrix
| Overlay | Active in chapters | Purpose |
|---|---|---|
| Callback policy | Scheme linkage and settlement policy; Payment submission and immediate result; Settlement posting and batch admission | Control overlay across active chapters |
| Signed acknowledgment | Scheme linkage and settlement policy; Payment submission and immediate result; Settlement posting and batch admission | Control overlay across active chapters |
| Poll fallback | Scheme linkage and settlement policy; Payment submission and immediate result; Settlement posting and batch admission | Control overlay across active chapters |
| Status inquiry | Scheme linkage and settlement policy; Payment submission and immediate result; Settlement posting and batch admission | Control overlay across active chapters |
| Idempotent recovery | Scheme linkage and settlement policy; Payment submission and immediate result; Settlement posting and batch admission | Control overlay across active chapters |
Technical closeout sequence
From immediate result through posting, batch, reporting, refund, and evidence close.
Support docs
- QR connection model: How each participant role connects to StableNexus.
- QR settlement and closeout: Closeout artifacts and readiness checks.
- Partner control plane: Callback automation, evidence, and routing.
- Callback automation: Signed delivery, replay, and poll fallback.
- Evidence and replay: Reserve, settlement, and servicing evidence.
Boundary
This page is the specification surface. Interactive cases and the projector are the proof surfaces. The operator workspace is the execution surface.