Skip to main content
cURL
curl -X POST https://api.origoid.com/mex/banking/v1/cep-validations \
  -H "x-api-key: YOUR_API_KEY" \
  -H "content-type: application/json" \
  -d '{"trackingKey": "BNET01002026060140000012345", "operationDate": "2026-06-01", "senderBankCode": "40012", "receiverBankCode": "40014", "beneficiaryAccount": "014180567812345678", "amount": "1500.00"}'
{
  "status": "OK",
  "type": "SUCCESS",
  "message": "CEP validated",
  "data": {
    "valid": true,
    "banxicoStatus": "LIQUIDADO",
    "trackingKey": "BNET01002026060140000098765",
    "referenceNumber": "7654321",
    "operationDate": "2026-06-01",
    "concept": "Pago de servicios",
    "amount": {
      "value": "1500.00",
      "currency": "MXN"
    },
    "sender": {
      "name": "ANA SOFIA MENDEZ CASTRO",
      "bankCode": "40014",
      "bankName": "SANTANDER",
      "account": "014320001234567896",
      "accountType": "CLABE",
      "rfc": "MECA880101QX3"
    },
    "beneficiary": {
      "name": "JUAN CARLOS RAMIREZ SOLIS",
      "bankCode": "40012",
      "bankName": "BBVA BANCOMER",
      "account": "012180001234567893",
      "accountType": "CLABE",
      "rfc": "RASJ900215K46"
    },
    "timeline": {
      "operatedAt": "2026-06-01T14:23:05-06:00",
      "receivedAt": null,
      "settledAt": null,
      "returnReceivedAt": null,
      "returnSettledAt": null
    },
    "spei": {
      "speiKey": "40012",
      "certificateNumber": "00001000000509876543",
      "signature": "MIIEpAIBAAKCAQEA9Wn...TRUNCATED_BASE64...fQjtFfiQ==",
      "cdaChain": "||01|01062026|01062026|142305|40012|SANT...TRUNCATED_BASE64...fQjtFfiQ=="
    },
    "files": [
      {
        "kind": "document",
        "contentType": "application/xml",
        "sizeBytes": 1582,
        "content": "PD94bWwgdmVyc2lvbj0iMS4wI...TRUNCATED_BASE64...JjZXJvPg=="
      }
    ]
  },
  "transactionId": "c1d2e3f4-a5b6-7c8d-9e0f-cepsuccess001",
  "processedAt": "2026-06-01T14:23:06-06:00",
  "billable": true
}

Authorizations

​
x-api-key
string
header
required

Body

application/json

Identify the transfer by its tracking key or its reference number (choose the matching request body below), and provide the beneficiary account, bank code and amount to match. When the account is an 18-digit CLABE the bank code is resolved from it automatically; for a card account, include the bank code.

​
trackingKey
string
required

Clave de rastreo of the SPEI transfer, assigned by the ordering bank.

Example:

"BNET01002026060140000098765"

​
operationDate
string
required

Operation date of the transfer, ISO YYYY-MM-DD.

Example:

"2026-06-01"

​
senderBankCode
string
required

Banxico institution code (5 digits) of the ordering bank. Optional when you send an orderingAccount CLABE; required for a card account.

Example:

"40014"

​
beneficiaryAccount
string
required

Beneficiary account: 18-digit CLABE or 16-digit card number. For a CLABE the bank code is resolved automatically and the control digit is validated.

Example:

"012180001234567893"

​
amount
string
required

Transfer amount to match against the CEP, as a decimal string in MXN.

Example:

"1500.00"

​
referenceNumber
string

Reference number of the transfer. Use this instead of trackingKey.

Example:

"7654321"

​
receiverBankCode
string

Banxico institution code (5 digits) of the beneficiary bank. Optional when you send a beneficiaryAccount CLABE; required for a card account.

Example:

"40012"

​
orderingAccount
string

Ordering (sender) account: 18-digit CLABE or 16-digit card number. Use instead of beneficiaryAccount.

Example:

"014320001234567896"

​
includePdf
boolean
default:false

Include the CEP PDF in files (kind document, application/pdf). The XML is always returned for settled payments; the PDF only when this flag is true.

Response

CEP validation result (Strict Envelope Pattern).

​
status
enum<string>
required

High-level outcome. OK means the request was successfully processed (regardless of business result). ERROR means the request was rejected or could not be processed.

Available options:
OK,
ERROR
​
type
string
required

Stable result type code. Includes generic codes (SUCCESS, INVALID_REQUEST, UNAUTHORIZED, SERVICE_UNAVAILABLE, INTERNAL_ERROR, RATE_LIMIT_EXCEEDED) plus endpoint-specific result codes — see this endpoint's response examples.

​
message
string
required

Human-readable summary of the result. Always in English (per Language Conventions in the API overview).

​
transactionId
string<uuid>
required

Unique identifier of this request, generated by the API Gateway. Propagated end-to-end for traceability.

​
processedAt
string<date-time>
required

ISO 8601 datetime with Mexico City offset (-06:00). Always set by the API Gateway when the response leaves the system.

​
billable
boolean
required

Whether this request will be charged against the client's plan. Typically true for successful business results and false for validation errors or system errors that prevented processing.

​
data
object

Verified SPEI transfer details from the CEP. Null for non-located outcomes (CEP_NOT_FOUND) and error types.

​
errors
object[]

Per-field error details. Present only on INVALID_REQUEST responses.