Payment Gateway Integration
How third-party payment gateways plug into the Bluecom eSIM platform.
This section is for payment providers who want to plug their gateway into the Bluecom eSIM platform so end-users can pay through it inside the Bluecom WebView / iframe checkout.
If you are a partner app embedding Bluecom and only need to be notified when a payment completes, you want Integration → Payment Return instead.
Who this is for
- Domestic VN gateways (QR-by-bank, card, wallet) — same class as our current reference integration Neox / NeoPay.
- International PSPs (card / APM) that expose either a hosted payment page (redirect/iframe) or a server-to-server create-payment API with a returned redirect URL.
What Bluecom expects from your gateway
At minimum:
- A create-payment API that accepts an order reference + amount + currency and returns either a redirect URL or QR payload.
- A server-to-server IPN / webhook that fires on terminal payment states (
SUCCESS,FAILED,EXPIRED, optionallyREFUNDED). - A deterministic signature scheme (HMAC-SHA256 or RSA) over a documented field set, so Bluecom can verify both outgoing requests and incoming IPNs.
- A sandbox environment with test credentials and test cards / test bank QR.
How to read the rest of this section
| Page | Read if you want to know… |
|---|---|
| Architecture | Where your gateway sits in the Bluecom stack, request/IPN flow, WebView/iframe constraints. |
| Checklist | The concrete deliverables and what Bluecom will build on its side. |
| Webhook Contract | Field-level spec for create-payment, IPN, and signature. (Draft — finalised per partner.) |
| Testing & Go-Live | Sandbox flow, certification cases, production cutover. |
| Timeline | Expected duration for an end-to-end integration. |