API, MCP and integration documentation

Check an existing SPEI payment: retrieve its original XML, validate the signature and compare transaction details and beneficiary name. No transfer is created.

# 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.

GET /console/api/payment-evidence/mx/cep/checks/{id} · GET /console/api/payment-evidence/mx/cep/requests/{original_idempotency_key}

202 queued · 409 idempotency conflict · 429 trial limit · 503 upstream held

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.