These simulations are available for testing only in the Sandbox Environment.Sandbox simulation rules do not apply in production.
You can simulate different KYC outcomes by using specific prefixes in customerReference. To trigger a scenario, submit a KYC request with a customerReference that starts with one of the value below.
Status: APPROVED
APPROVED| Param | Value |
|---|---|
customerReference | Prefix 5555 followed by any random number, for example 5555123456789 |
The KYC request will immediately result in APPROVED.
Status: REJECTED
REJECTED| Param | Value |
|---|---|
customerReference | Prefix 6666 followed by any random number, for example 6666123456789 |
The KYC request will immediately result in REJECTED.
Status: PENDING
PENDING | Param | Value |
|---|---|
customerReference | Prefix 8888 followed by any random number, for example 8888123456789 |
The KYC request returns PENDING and remains PENDING indefinitely (it does not auto-approve) — use the Get KYC Status API to test your polling and timeout handling.
Status: PENDING → APPROVED
PENDING → APPROVED| Param | Value |
|---|---|
customerReference | any random number without prefix 5555 , 6666 or 8888 |
Any customerReference that does not have prefix 5555 , 6666 or 8888 will initially result in PENDING. Please use the Get KYC Status API to change the status from PENDING to APPROVED by submitting the same customerReference.
Transaction Gating Simulation
After simulating a KYC status, test how Create Pay In and Create Pay Out API respond before approval:
customerReferencewith no submitted KYC → Create Pay In and Create Pay Out API will returnKYC_REQUIREDcustomerReferencewith prefix8888→ Create Pay In and Create Pay Out API will returnKYC_PENDINGcustomerReferencewith prefix6666→ Create Pay In and Create Pay Out API will returnKYC_REJECTED
Please refer to the Error page for details.