Tovanix

Payment Lifecycle Replay Lab

Before you accept real funds, replay a payment from creation to its final state with synthetic orders and synthetic callbacks, and prove how your system handles every non-happy path. Every order, address, transaction and callback on this page is synthetic.

Seven scenarios: normal payment, underpaid, overpaid, reorg-induced uncertainty, expired unpaid, webhook retries with a duplicate delivery, and an illegal transition
Event timeline: each state transition step by step; rejected transitions come with a reason and leave the run untouched
Synthetic callback payload: the field set comes from the platform contract; the signature is an explicit unsigned marker and cannot be verified
Delivery target: replay may only reach the in-product isolated consumer or an allowlisted local test endpoint
Run retention and export: runs stay in your own browser and exports carry no identifiers

Frequently Asked Questions

Does the lab touch real funds or real callbacks?

No. Every order, address, transaction and callback is synthetic, the callback signature is an explicit unsigned marker, and delivery can only reach the in-product isolated consumer or an allowlisted local test endpoint — never a real merchant system.

What does a replay actually prove?

It checks that your handling logic is correct under confirmation delays, expiry, amount mismatches, inconclusive on-chain evidence and duplicate notifications — for example that a duplicate delivery is ignored idempotently. It is not a production integration test and does not replace signature verification against a real sandbox.

Loading…