2026-10-22
Verify an existing SPEI payment with CEP evidence
A screenshot helps locate a payment. A reconciliation decision also needs evidence tied to the operation your system expects.
Mexico CEP verification API
Retrieve and verify evidence for existing SPEI payments. Compare the transaction and beneficiary name through one web console, API and MCP workflow.
Try CEP VerifyVerified business email required. 10 lifetime trial attempts per business domain; 50 daily across the service. Free trial; paid checkout is not enabled.
Reference package: 250 MXN / 1,000 completed checks, 30 days. Paid checkout is not enabled.
Signature, transaction binding and name comparison are separate results. Historical names do not prove current control or document identity. Review and not-found results do not imply fraud.
Verification and retention termsSeven days of CEP integration guides
Seven days of CEP integration guides →
2026-10-23
CEP XML parsing, signature checks and transaction binding
These checks answer different questions. Keeping them separate makes a payment-evidence result useful to an auditor and to the application handling the order.
2026-10-24
A verified CEP can still have a beneficiary-name difference
Payment evidence and name matching should not collapse into one success flag. A name difference needs its own business policy.
2026-10-25
Deduplicate account research without losing payment reconciliation
A batch can contain repeated accounts and distinct payments. The correct deduplication key depends on the question you need to answer.
2026-10-26
Handle pending CEPs, not-found results and rate limits
An integration is useful when it explains what to do after an incomplete result. Missing evidence should not be turned into a false fraud verdict.
2026-10-27
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.
2026-10-28
Price CEP reconciliation separately from a new bank transfer
A payment-evidence service and an active account test have different cost drivers. Treating them as one product can make pricing and customer expectations inaccurate.
API, MCP and integration documentation
# 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.