Use the test CLABEs below in the testing environment to get every terminal state of an account validation on demand. Each one returns a fixed result, so you can check how your integration handles COMPLETED, each error.code in Failed validations, and a validation that stays in PROCESSING.

📘

Testing environment only

These CLABEs work only in the testing environment. They are not real accounts. Do not use them in production.

How It Works

A test CLABE goes through the same flow as any other account:

1. Call Create account validation with type: MX_SPEI, mx_spei.account.type: CLABE, and a test CLABE as mx_spei.account.clabe.number. Any expected_owner.name is accepted.
2. The response is 202 Accepted with status: PROCESSING.
3. A few seconds later, the validation reaches the result listed for that CLABE. Bitso sends the account_validation webhook described in Webhook Notifications, and Get account validation returns the same result.

No penny validation is sent for a test CLABE, so nothing is withdrawn from your balance. Any other CLABE in the testing environment follows the regular flow.

Test CLABEs

810000000000000012 returns this verified_owner:

{
  "name": "Stage Mock Account Owner",
  "identification_type": "RFC",
  "identification_number": "BOJ6307173V5"
}

810000000000000083 never reaches a terminal state and never sends a webhook. Use it to test the timeout or pending state you keep on your side for a long PROCESSING, as recommended in Response time.

Example

{
  "type": "MX_SPEI",
  "mx_spei": {
    "account": {
      "type": "CLABE",
      "clabe": { "number": "810000000000000054" },
      "expected_owner": { "name": "Expected Owner Full Name" }
    }
  }
}

The webhook payload for that validation, and the response of Get account validation, has status: FAILED and error.code: cep_mismatch. The error.message for each code is defined in the API Reference.