PayVault · Section
Developers
Payment integrations do not fail on the happy path. They fail on the retry, the duplicate callback and the timeout that arrived after the client had already given up. The interface is designed around those.
Every mutating request carries a key. Sending it twice produces one payment and two identical responses.
Callbacks retry until acknowledged. Your handler must be safe to run twice, and the docs say so on the first page.
Schemas are versioned and old versions keep working. A payment integration should not break because we shipped on a Tuesday.
Failures return a stable code and a reason, so your support team can explain a decline without contacting us.
See it live
The same interface the console runs on
Request shapes, response codes and the callback contract, laid out the way an engineer would want to read them before writing a single integration.
The three pieces
Request it, hear about it, and break it safely first
Bring an engineer, not a procurement form
We will walk through the interface, the callback contract and the sandbox with someone who has integrated it, rather than through a slide deck.