← Back to schema index

`ValidationRequest`

Parameters for validating a SPEI transfer against the Banxico CEP. At least one of `clave_rastreo` or `referencia_numerica` must be provided; if both are omitted the server returns 422.

Properties

Field	Type	Description
`fecha` *	`string (date)`	Transfer date in ISO 8601 format (YYYY-MM-DD). Must match the date registered in the CEP; differences of ±1 day may result in `not_found`.
`monto` *	`number (double)`	Transfer amount in Mexican pesos (MXN), greater than zero and up to two decimal places. Must match exactly the amount registered in the CEP; any difference may result in `not_found`.
`clave_rastreo`	`string`	SPEI tracking key generated by the sending bank: alphanumeric string of 18 to 30 characters. Required if `referencia_numerica` is absent; both can be sent simultaneously for more precise matching.
`referencia_numerica`	`string`	Numeric transfer reference: between 1 and 7 digits. Required if `clave_rastreo` is absent; both can be sent simultaneously.
`emisor`	`string`	Name of the sending bank. Free text; normalized internally against the Banxico catalog. Ignored for CLABE and card numbers, where the sender is derived from the account prefix. For phone/DiMo (10 digits), providing this field improves bank resolution.
`receptor`	`string`	Name of the receiving bank. For CLABE (18 digits) and card (13-19 digits) the bank is derived automatically from the prefix/BIN and this field is ignored. Only relevant when `cuenta_beneficiaria` is 10 digits (phone/DiMo) and cannot be resolved by other means.
`cuenta_beneficiaria`	`string`	SPEI destination account: 18-digit CLABE, 13-19 digit card number, or 10-digit DiMo phone number. The type is auto-detected by length and the appropriate checksum is validated (CLABE: standard check digit; card: Luhn). For phone numbers, the receiving bank is resolved from the user's whitelist then global catalog; if unresolvable, the validation result is `error` with code `bank_code_unresolvable_for_phone`.
`retry_policy`	`object`	Automatic retry policy for this validation. If omitted, the policy configured at `PUT /v1/users/me/retry-policy` is used. Retries do not consume validation quota.
`enabled`	`boolean`	Enables or disables the retry cycle for this validation. If `false`, the other fields are ignored.
`max_retries`	`integer`	Maximum number of automatic retries. Once reached, the cycle enters the `exhausted` terminal state. The upper bound depends on the plan (`retry_max_retries`) or the global default `max_retries_cap` (typically 5–10).
`interval_seconds`	`integer`	Seconds to wait between each retry (300–86400, i.e., 5 minutes to 24 hours).
`outcomes`	`array`	Validation outcomes that trigger a retry. By default the cycle activates on `not_found`, `cep_unavailable` and `error`; clients that do not want to retry Banxico HTTP 5xx errors can send `["not_found", "cep_unavailable"]`.

Variants

`anyOf`

object
object

Used in operations

POST /v1/validate