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

  1. Create the consent — Call Initiate Payment Consent Signing. The consent starts as INITIATED.
  2. Activate the consent — Use the Mimic API to set the status to ACTIVE.
  3. Initiate a payment — Call Initiate Payment with the consent_id.
  4. (Optional) Revoke — Set the status to REVOKED to simulate cancellation.

Valid Status Transitions

FromTo
INITIATEDPENDING, ACTIVE, DECLINED, EXPIRED, ABORTED, CRASHED
PENDINGACTIVE, DECLINED, EXPIRED, ABORTED, CRASHED
ACTIVEREVOKED
📘

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 INITIATED to REVOKED.