Simulating Payment Consent Status Updates
In the sandbox environment, you can simulate consent status changes using the Mimic API. This lets you test your integration end-to-end — including status callbacks — without going through a real signing flow.
To simulate a status change, use the Update Consent endpoint. If a status_callback_url was provided when the consent was created, a callback will be sent with the new status.
Sandbox Test Flow
- Create the consent — Call Initiate Payment Consent Signing. The consent starts as
INITIATED. - Activate the consent — Use the Mimic API to set the status to
ACTIVE. - Initiate a payment — Call Initiate Payment with the
consent_id. - (Optional) Revoke — Set the status to
REVOKEDto simulate cancellation.
Valid Status Transitions
| From | To |
|---|---|
INITIATED | PENDING, ACTIVE, DECLINED, EXPIRED, ABORTED, CRASHED |
PENDING | ACTIVE, DECLINED, EXPIRED, ABORTED, CRASHED |
ACTIVE | REVOKED |
Note: Status transitions are validated. You cannot skip to a status that isn't reachable from the current one — for example, you cannot go directly from
INITIATEDtoREVOKED.
Updated 4 days ago