Simulations

Generate test enrolment states and test alerts for TEST mode organisations.

Base URL: https://api.chargebackstop.com/v1/simulate/

Authentication: Bearer token via API key.

Required abilities:

  • simulations:enrollments for PATCH /v1/simulate/enrolments/{enrolment_id}

  • simulations:alerts for POST /v1/simulate/alerts

Access scope model:

  • Organisation-level keys can simulate data for their own organisation only.

  • Admin partner-group keys can simulate data across all organisations for their partner.

  • Non-admin partner-group keys can simulate data only for organisations assigned to their group.

Typical simulation flow:

1

Create an enrolment

Create an enrolment with /v2/enrolments.

2

Enable the enrolment for simulation

Set that enrolment to ENABLED with:

PATCH /v1/simulate/enrolments/{enrolment_id}

3

Generate a simulated alert

Generate a simulated alert with POST /v1/simulate/alerts.


PATCH /v1/simulate/enrolments/{enrolment_id} - update enrolment simulation status

Updates an enrolment status for simulation use.

API level: Organisation-level and partner-level Authentication: simulations:enrollments

URL parameters

Parameter
Type
Description

enrolment_id

string

Enrolment ID to update

Request body

Field
Type
Required
Description

status

string

Yes

New enrolment status: ENABLED or UNENROLLED

Important behaviour

  • This endpoint is only available for TEST mode organisations.

  • The enrolment must be accessible to the authenticated API key.

  • For ETHOCA_ALERT enrolments, setting status to ENABLED activates configured descriptors for simulation matching.

Example request

Example response


POST /v1/simulate/alerts - create simulated alert

Creates a simulated network alert.

API level: Organisation-level and partner-level Authentication: simulations:alerts

Request body

Field
Type
Required
Description

organisation_id

string

Yes

Organisation ID. Must be in TEST mode and accessible to the key

enrolment_id

string

Yes

Enrolment ID that belongs to organisation_id

status

string

No

Alert status: ACTION_REQUIRED, RESOLVED, INVALID. Verifi RDR only supports RESOLVED or INVALID

transaction_refund_outcome

string

No

Refund outcome: REFUNDED or NOT_REFUNDED. Only valid with status=RESOLVED

card_scheme

string

No

Card scheme. Use any supported scheme value, for example VISA, MASTERCARD, AMEX

amount_in_cents

integer

No

Transaction amount in cents. Must be a positive integer

currency_code

string

No

ISO 4217 currency code, for example USD, EUR, GBP

transaction_acquirer_reference_number

string

No

ARN. Must be exactly 23 characters

transaction_authorisation_code

string

No

Authorisation code. Must be exactly 6 characters

Important behaviour

  • This endpoint is only available for TEST mode organisations.

  • If status is omitted, the simulator chooses a valid status.

  • If transaction_refund_outcome is provided without status, the created alert is set to RESOLVED.

  • Simulated alerts trigger the same alert.created event flow as non-simulated alerts.

Example request

Example response


Common error responses

Error responses use this shape:

Example: 401 Unauthorised

Example: 403 Forbidden

Example: 404 Not found

Example: 422 Unprocessable Entity (simulation not allowed)

Example: 422 Unprocessable Entity (simulation validation error)

Example: 422 Unprocessable Entity (invalid enum value)

Additional reference: 500 Server error

Was this helpful?