Yes or no isn't enough
A receipt-validation service can confirm different things: that the payment exists, that it exists and goes to the right account, or that it exists, goes to the right account, and carries the amount you expected. A useful verdict says which of the three it confirmed, not just "valid".
Without that distinction, your system can't decide with judgment: treating "the payment exists" the same as "the payment is exactly what you expected" is the difference between confirming a real order and confirming one with the wrong amount.
When the receipt doesn't show up
The CEP isn't always published at the moment of the lookup: Banxico can take seconds or hours, depending on when the payment was made. A "not found" verdict describes that moment, not the payment.
A well-designed response distinguishes "not found, it may still appear" from "not found, retries exhausted": the first asks you to wait, the second asks you to investigate with the beneficiary.
ImportantA "not found" never proves a payment is fake: it only says the CEP wasn't published at that moment with that data.
How certain the reading was
When validation starts from a photo or a PDF instead of typed data, the system has to read the receipt first, before anything else. That reading carries its own degree of certainty, distinct from the verdict: a blurry image can be misread even when the payment is real.
A complete response keeps the two numbers apart: how certain the reading was, and whether the payment was confirmed. Mixing them into a single verdict hides the case where the reading failed but the payment does exist.
With VerikoVeriko's response brings the two figures separately: how certain the receipt reading was, and the verdict Banxico confirmed.
How Veriko does it
A Veriko validation brings the verdict, the state Banxico reports, and — when it wasn't found — a diagnosis of which field didn't match: the date, the account, the amount, or a combination.
When the payment is confirmed, the response includes the official CEP in PDF and XML, ready to save as a tax or audit record.
| What you need | A generic yes or no | With Veriko |
|---|---|---|
| Data | Valid or not, with no further context | Verdict, Banxico's state, and a diagnosis if not found |
| Hours | Doesn't say whether a retry is worth it | Distinguishes "not yet" from "won't ever show up" |
| Volume | The same format for every case | A consistent schema, whether one or a thousand payments |
| Result | A boolean you have to interpret | CEP in PDF and XML, with date, amount and banks |
| Log | Whatever you build | History of every validation, with its full response |
If your system decides based on the payment, the validation's response matters as much as the payment itself. There's a free plan that never expires to try it, and the pricing page compares the plans.
Frequently asked questions
Does a "not found" verdict mean the payment is fake?
No. It means the CEP wasn't published with that data at the time of the lookup.
What's the difference between the verdict and the state Banxico reports?
The verdict is the conclusion for your system (confirmed, not found, returned); Banxico's state is the raw data that conclusion comes from.
Why can a validation take a while to give a definitive answer?
Because the CEP itself can take a while to publish after the payment settles. The validation can't confirm what Banxico hasn't published yet.
What happens if the receipt image is blurry?
The image reading may fail on some field, and a complete response says so separately from the verdict: it doesn't confuse "I couldn't read the image well" with "the payment doesn't exist".
Do the PDF and XML CEP say the same thing?
Yes, the same content in two formats: the PDF to read or file, the XML to process by system.
What should I save from a validation, the verdict or the full CEP?
Both: the verdict for your business logic, and the full CEP in case you need the documentary proof later.