Sandbox testing and simulation labels - Bastion

Bastion has introduced simulation labels that your team can use to simulate specific product flows in sandbox. We recommend using simulation labels during your testing efforts and UAT integration.

Onboarding and KYC/KYB simulation

For sandbox KYC and KYB, you can use the label field when calling POST /v2/identities to simulate KYC outcomes and submit dummy KYC/KYB information. Once POST /v2/identities/{identity_id}/compliance is completed, the identity will transition to the state indicated by the simulation label.

Scenario	Simulation Label
Simulate an approved onboarding with identity_status = `ACTIVE`	`sim-onboarding-result:approved`
Simulate a rejected onboarding with identity_status = `REJECTED`	`sim-onboarding-result:rejected`
Simulate a pending onboarding that requires IDV checks, with identity_substatus = `IDV_REQUIRED`	`sim-onboarding-result:idv-required`

Example:POST /v2/identities

{
  "label": "sim-onboarding-result:approved",
  "identityType": "IDENTITY_TYPE_INDIVIDUAL"
}

Identity verification (IDV) simulation

For sandbox IDV checks, you can use the labels field when calling POST /v2/identities/{identityId}/id_verification to simulate IDV outcomes. Note that labels is an array.

Scenario	Simulation Label
The IDV check is created and subsequently transitions to `APPROVED` status.	`sim-idv-check-result:approved`
The IDV check is created and subsequently transitions to `REJECTED` status.	`sim-idv-check-result:rejected`

Example:POST /v2/identities/{identityId}/id_verification

{
  "redirect_url": "https://www.google.com",
  "reason": "ONBOARDING",
  "request_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "labels": ["sim-idv-check-result:approved"]
}

Related topics

Onboard a business customer Onboard an individual customer Simulate Fiat Deposit Sandbox vs. production environments Sandbox access and test API keys

⌘I