Cambodia corridor remittance and agent payout orchestration
Cambodia corridor funding, screened route lock, ABA treasury handoff, Wing account or agent payout, and reconciled close within one governed remittance workflow.
Overview
Route coverage
Infrastructure
- Outcome-first Cambodia corridor framing
- ABA treasury handoff plus Wing payout topology
- Originator screening, route approval, and delivery proof
- Reconciliation close instead of payout-only completion
Lifecycle stages
| Stage | Flow steps |
|---|---|
| Funding And Beneficiary | Capture funding posture, originator identity, source-of-funds reference, payout outcome, beneficiary identity, and corridor-origin context before screening, pricing, or payout release are attempted; Keep the intake packet outcome-first while still making delivery method, eligibility, and remittance controls explicit |
| Quote And Route Lock | Run originator and beneficiary screening, confirm remittance-data completeness, and compare eligible payout routes before any release decision is locked; Lock the approved route, quote expiry, and release basis on one control plane without collapsing the Cambodia lane into generic pricing copy |
| Treasury Handoff And Payout Delivery | Release the approved funding instruction to ABA, record treasury credit and FX confirmation where payout currency differs from funding currency, then move the run into Wing payout delivery on the same corridor packet; Re-verify the beneficiary for the selected delivery method, publish the payout instruction, and keep account credit and agent cash-out inside one governed Cambodia lane |
| Reconciliation And Close | Match payout completion, partner callback or statement state, and corridor ledger records before publishing close; Hold any mismatch or expired pickup event inside corridor review and publish the close packet only after the exception is resolved or waived |