Lakala
Channel Overview
Lakala is a leading domestic third-party payment institution providing aggregated acquiring. DaxPay integrates Lakala's V3 API in ISV mode (product lakala_pay); once a merchant is onboarded to Lakala, WeChat, Alipay, and QuickPass collection are all available.
Lakala is a commercial-edition extended channel; after purchasing the flagship edition the official team assists with onboarding and integration. See the channel overview.
Supported Payment Methods
| Underlying rail | Supported methods |
|---|---|
| Barcode, QR code, JSAPI (Official Account), mini-program, APP | |
| Alipay | Barcode, QR code, JSAPI |
| UnionPay (QuickPass) | Barcode, QR code, JSAPI |
WeChat JSAPI and mini-program payments require a bound WeChat app (AppId) in the channel configuration.
Configuration Structure
Lakala configuration has two layers: the product-level ISV key set (one set for all Lakala merchants) and the channel-merchant-level terminal binding:
- Configure the ISV keys (Lakala product → Key Configuration, one global set):
| Group | Field | Notes |
|---|---|---|
| Basic | Lakala app ID | Assigned by the Lakala service-provider portal |
| Institution code | Service-provider institution code | |
| Keys | Merchant certificate serial number | Matches the certificate uploaded to Lakala |
| Lakala public key | PEM format, for verification | |
| App private key | PEM format (PKCS#8), for signing | |
| Advanced | SM4 key | Optional; encrypts sensitive onboarding fields |
- Create the channel merchant: Merchant Workbench → Channel Merchants → Create, pick the Lakala product and fill in merchant name + Lakala merchant number (obtained after onboarding);
- Bind the terminal: configure the terminal number (termNo) in the channel merchant detail.
Signature & Callback
- Request signing: RSA2 (SHA256withRSA) — merchant private key signs, Lakala public key verifies; certificates are PEM format;
- Async notifications are verified by the platform and acknowledged; callback URLs are generated by the platform.
Notes
- Switch the environment before creating merchants: sandbox and production use different gateways; keep one set per environment;
- Ensure the server egress IP is whitelisted by Lakala;
- Collection rights per rail (WeChat/Alipay/UnionPay) follow what was activated during Lakala onboarding.