GridZen · CEP Verify

Integrate one CEP workflow through REST, web and MCP

The interface can change without changing the meaning of a verification. All channels should refer to the same tenant-owned task.

Use one durable request

Create one UUID before submitting an authorized existing payment. Retain the entire payload and UUID for retries. Changing an operation field under the same UUID returns an idempotency conflict. After a timeout, read by the original request UUID before creating anything else.

Amounts use integer MXN cents: 100 means 1 MXN, not 100 MXN. Institution fields use supported five-digit codes. The initial merchant route accepts validated 18-digit CLABEs; historical card support elsewhere is not an announcement of card support in this API.

Keep identity and credentials out of URLs

Authenticate with your merchant API key in the authorization header. Send operation fields in the JSON body. Keep keys and request files in private storage. Use only business data you are authorized to process and obtain the required authorization before invoking an agent tool.

MCP submission queues the same existing-payment task as REST and the web console. It has no hidden payout action and no separate free allowance. Reading its result does not issue another provider request.

Interpret a structured result

Read signature status, each binding field and the name comparison independently. Save the task ID against your business order. Download originals only through the authenticated tenant-owned route; do not expose permanent public links to bank data. The example below requires your own permitted request file and does not contain a live payment sample.

# Submit only an existing, authorized payment. Store the request locally.
# cep-request.json fields:
# idempotency_key (UUID), operation_date (YYYY-MM-DD), tracking_key,
# amount_minor (integer MXN cents), issuer_code, receiver_code (5 digits),
# account (18-digit CLABE), expected_name (optional), business_website,
# authorization_reference (UUID), authorized_to_query: true,
# purpose: "payment_reconciliation", terms_version: "cep-existing-payment-2026-10-22".
curl --fail-with-body https://gridzen.ai/console/api/payment-evidence/mx/cep/checks \
  -H "Authorization: Bearer ${GRIDZEN_API_KEY:?set your merchant key locally}" \
  -H "Content-Type: application/json" --data-binary @cep-request.json
# 202 returns a durable task id. Preserve the UUID after a timeout.
# GET /console/api/payment-evidence/mx/cep/requests/{original_idempotency_key}
# GET /console/api/payment-evidence/mx/cep/checks/{id}
# GET /console/api/payment-evidence/mx/cep/checks/{id}/original
# No payout is created. Never submit a made-up or unapproved transaction.

Banco de México · CEP / SPEI · GridZen CEP Verify

Verified business email required. 10 lifetime trial attempts per business domain; 50 daily across the service. Free trial; paid checkout is not enabled.

Try CEP Verify