Case 4 — Offshore HKD Payroll (Documentary)
This case is not demonstrated live in the MVP. It is included in the documentation as a real-economy narrative for HKMA and licensed issuers: a concrete, non-speculative illustration of why compliant HKD stablecoin rails matter.
Scenario
A Hong Kong-incorporated company (Startup X) employs remote workers in Southeast Asia. Historically, monthly payroll runs via SWIFT wire transfers, incurring US$25–40 per transfer, with 1–3 business day delays. Startup X wants to switch to HKD stablecoin payroll on Hkchain.
Actors
| Actor | Role |
|---|---|
| Startup X HR team | Payroll originator |
| Employees (50 people, across Vietnam, Philippines, Indonesia) | Payroll recipients |
| HSBC | Licensed issuer of hkd.hsbc; Startup X's bank |
| Local cash-out partner (e.g., licensed remittance service) | Converts recipient's HKD stablecoin back to local currency |
Flow (abbreviated)
- Setup: Each employee completes KYC with HSBC (or a contracted KYC provider), reaching L3. Their chain address is registered.
- Month-end mint (if needed): Startup X requests HSBC to mint HKD against Startup X's fiat deposit. Standard mint flow.
- Batch transfer: Startup X sends HKD to all 50 employee addresses in a single batch. Each transfer carries Travel Rule metadata. Some transfers (larger salaries) trigger threshold flags; HSBC's compliance team reviews and approves (common pattern once the employee relationship is known).
- Employee receives: HKD lands in each employee's Hkchain address within one block.
- Employee cashes out (optional, on their schedule): Employee sends HKD to a partner remittance service, which converts to local currency and pays to the employee's local bank. Or, the employee holds HKD as a store of value.
What Hkchain makes possible
- Cost: Per-transfer cost on Hkchain is negligible (gas-only). Compared to $25–40 SWIFT, savings of 99%+.
- Latency: One block (sub-second on single-node; low single-digit seconds in multi-validator production) versus 1–3 business days.
- Transparency: Every payroll transfer is audit-recorded. Startup X's accounting system can query on-chain records directly.
- Compliance: Every transfer carries Travel Rule metadata. The employee's KYC is on chain. No ad-hoc vendor-specific compliance regime.
- Flexibility: Employees choose when to cash out; their HKD holding is not stuck in a corporate bank for days.
Why this is not in MVP demo
- The compliance narrative is already well-demonstrated by Case 1 (B2B settlement) and Case 3 (public verification)
- A live payroll demo requires a plausible fake employer identity and 50 fake employees — staging cost high, demo value marginal
- The case is better communicated as a slide / document for the real-economy panel of the HKMA conversation
Forward-looking variants
- Multi-currency payroll (post-MVP): employees in different jurisdictions receive stablecoin in their local currency, not HKD. Requires a multi-currency Hkchain deployment or interop with other jurisdiction-specific compliant chains.
- Performance-based payroll: smart-contract-logic payouts tied to KPIs or milestones. Not a Hkchain native feature, but could be supported via the EVM layer with compliance enforced the same way.