Verify an existing SPEI payment with CEP evidence

Start with the operation, not the picture

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. If you have only an account and a name, the missing payment details cannot be inferred from those two fields.

Keep three conclusions separate

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.

Put the result in your reconciliation workflow

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. The limited trial shows pending and review outcomes as well as verified evidence.