Engagement Scenarios
How integration work against Cambodia's digital public infrastructure would be scoped — the architecture, the sequencing, and the boundary between what we build, what the client operates, and what stays with the licensed parties.
Scoping a Multi-Channel KHQR Acceptance Build
An illustrative engagement scenario: how a multi-site Cambodian retailer accepting payments across POS, e-commerce and a mobile app would consolidate onto Bakong and KHQR — the architecture, the scope boundary between the merchant, its sponsor bank and CamFinTech, and the failure modes to design against.
7 min readScoping an ERP-to-CamInvoice Connector
An illustrative engagement scenario: how a Cambodian business would connect its existing accounting or POS system to CamInvoice — the document mapping, the submission lifecycle, idempotency and retry design, and why the connector belongs inside the client's estate rather than behind a vendor's service.
8 min readScoping Cross-Border KHQR Acceptance
An illustrative engagement scenario: how a Cambodian merchant would accept payments from visitors using their home payment apps over Bakong's bilateral corridors — what the integration covers, why foreign exchange and routing are the bank's job and not an integrator's, and how to tell a real capability from a claim.
7 min readScoping Digital Origination Adapters for a Lender
An illustrative engagement scenario: how a licensed Cambodian lender would wire CamDigiKey identity verification and consented CamInvoice data into its own origination system — what an integrator builds, why the credit decision and the borrower data stay with the lender, and where the boundary is not negotiable.
8 min read