Test and live environments
Understand sandbox behavior, limits, and live availability.
Current availability
TEST simulates payments without contacting a bank. LIVE creation requires approved, unexpired KYC and an enabled bank merchant configuration for the requested method. Each request must fit its currency amount range. Bank callback verification, polling and LIVE cancellation remain unavailable pending bank authentication implementation; creation alone does not confirm settlement.
TEST
Use TEST credentials against the same gateway routes. Creation returns environment: "TEST", status: "PENDING", generated identifiers, qrCode: "GATEWAY_TEST:...", a portal deepLink/paymentUrl, and simulationId. Expiry is 15 minutes. A background task checks expired test payments approximately every minute.
The sandbox daily quota is per merchant platform and resets on the Asia/Vientiane calendar day. Read your current allowance in Sandbox; there is no universal fixed quota in this guide. Exhaustion returns HTTP 429 with reset information.
Create webhook endpoints in TEST to receive simulated outcomes. Simulation is permitted only while a payment is pending; repeating the same outcome is a no-op, and changing an already final simulation returns 409. Success cannot be simulated after expiry.
LIVE
LIVE is isolated from TEST by credential and transaction scope. Approved, unexpired KYC and an enabled bank merchant configuration are required; there is no separate LIVE approval or method/currency permission. Both TEST and LIVE enforce inclusive per-request currency ranges. LAK defaults to 1–50,000,000 kip unless the administrator saves a custom range. USD and THB need configured ranges. There is no daily monetary limit; the TEST request-count quota remains.
See Live access for account status and KYC for verification. Never treat a simulated success as a real settlement.
Sandbox payment app
The planned Android APK and PWA will provide a bank-app-like simulation experience. The intended flow is:
Step 1
Your integration creates a TEST payment.
Step 2
Open or scan a supported test payment in the sandbox app (planned).
Step 3
Review the amount and select a simulated payment outcome (planned).
Step 4
Your integration receives the signed TEST callback and updates its test order.
This app is not released yet. App scanning, payment opening, and its authentication contract still need implementation. The current TEST QR payload is GATEWAY_TEST:<simulationId>; it is not a real bank QR and is not evidence of an available app integration. Do not use API secrets inside an APK/PWA.
Download or open the app
Until the app is available, use the portal Sandbox or the deepLink/paymentUrl in the TEST creation response. The portal lets you simulate success, failure, expiry, or cancellation. The current response does not contain APK/PWA app links; the download links above are documentation configuration.