Idempotency
Looks for stable identifiers to help prevent duplicate payment processing.
A tool for payment teams
Paste a Pix event to spot structure, idempotency, and security issues before they affect your operation.
Your browser analyzes the payload locally. It is never sent to AZPay.
Paste JSON to start the analysis.
The endToEndId identifies the Pix transfer. The txid links the charge when present. Confirm receipt with your PSP and post it once. Banco Central do Brasil · API Pix 2.10.0 · WebhookPixBody
Run a quick check to build more predictable webhook consumers. Signature validation still belongs on your server.
Looks for stable identifiers to help prevent duplicate payment processing.
Helps make transitions such as pending, confirmed, failed, and refunded explicit.
Flags potential tokens, passwords, or card data before you share an example.
Record the event ID before applying side effects, respond promptly, and process the event asynchronously.
for (const pix of payload.pix) {
await db.transaction(async tx => {
if (await tx.insertReceiptIfAbsent(pix.endToEndId)) {
await tx.enqueueReconciliation(pix);
}
for (const refund of pix.devolucoes ?? []) {
await tx.reconcileRefundOnce(refund.rtrId, refund.status);
}
});
}
return response(200);No. The basic analysis runs in your browser. Avoid pasting real tokens, keys, personal information, or card data.
Signature validation requires your integration’s secret and algorithm. The inspector flags structural and security issues. Run cryptographic verification on your backend.
Webhooks may be retried after a timeout or network failure. A stable identifier helps you recognize processed events and avoid duplicate charges, payment records, or fulfillment.
See how AZPay Checkout fits your payment experience.