Verify an existing SPEI payment with CEP evidence

Description and use

Retrieve existing payment evidence without initiating a transfer by providing operation details (date, tracking key, institutions, beneficiary CLABE, amount in integer MXN cents). GridZen retrieves the original XML, checks the signature, and compares all fields. A parsed document is not automatically verified. Name comparison may show differences requiring review. Save task ID with business order; preserve request UUID after timeout for retry. Trial limits: 10 lifetime attempts per domain, 50 service-wide per day, paid checkout disabled.

Problem

A screenshot helps locate a payment, but reconciliation decisions also need evidence tied to the operation the system expects. The user needs to retrieve and verify existing payment evidence (original XML, signature, operation date, tracking key, amount, sending/receiving institutions, beneficiary account) without initiating a new transfer.

Outcome

Verified transaction evidence can include a name difference that requires team review; do not treat payment confirmation as an assertion that the applicant controls the account or passed document identity checks. Limited trial shows pending and review outcomes as well as verified evidence.

Workflow

• Record the operation date, tracking key, sending institution, receiving institution, beneficiary CLABE and amount (integer MXN cents).
• Send the details of an existing operation you are authorized to process.
• Save the task ID with your business order.
• Preserve the original request UUID after a timeout and read that task before retrying.
• Release goods or mark an invoice paid only under your own policy once the required evidence is available.

Evidence

Record the operation date, tracking key, sending institution, receiving institution, beneficiary CLABE and amount. Keep the amount in integer MXN cents in your integration. The amount must be the transferred principal, not a payout platform’s combined principal and fee.

Send the details of an existing operation you are authorized to process. This route retrieves payment evidence; it does not initiate a transfer.

GridZen retrieves the original XML through its integrated SDK and separately checks the signature. It then compares the operation date, tracking key, amount, sending institution, receiving institution and account with your submitted operation.

A parsed document is not automatically verified.

Beneficiary-name comparison is another result. A verified transaction can still have a name difference that your team needs to review.

Do not turn payment confirmation into an assertion that the applicant controls the account or passed document identity checks.

Save the task ID with your business order. A queued response means work is pending; release goods or mark an invoice paid only under your own policy once the required evidence is available.

Preserve the original request UUID after a timeout and read that task before retrying.

Limited real trial: verified business email, 10 lifetime attempts per domain, 50 service-wide per day. Paid checkout is disabled. Upstream access and CEP availability can delay results. No new transfer is created.