Verify mandates
You build a merchant or a payment platform. Add the verifier before your authorisation.
Merchant SDKsFor developers
Build with OID4Pay.
Check a mandate with the real verifier, offline, in five minutes. Then give your own agent a mandate.
npm install @oid4pay/oid4ac-merchant npx oid4ac-merchant accepted Standard Starter Set EUR 45.00, within the limit refused Refill Pack offer_digest_mismatch refused Deluxe 10-Piece Set offer_digest_mismatch, over_limit refused another shop audience_mismatch refused an expired mandate invalid_mandate_claims refused another agent kb_jwt_jkt_mismatch
01 / Try the verifier
Check a mandate in five minutes.
The example mints a fresh sample mandate with a stand-in issuer and checks it with the real verifier. Then it shows what a merchant refuses. It runs offline and makes no payment.
What the refusals mean
offer_digest_mismatch- The order is not the one the human approved.
audience_mismatch- The mandate is for another shop.
invalid_mandate_claims- A claim is not valid, for example the mandate has expired.
kb_jwt_jkt_mismatch- The agent key is not the key the mandate is bound to.
over_limit- The merchant's own rule: the charge is above the approved limit.
02 / Pick your path
Three ways in.
Give your agent a mandate
You build an agent. It asks a human for approval, then pays with the mandate, never with the card.
Agent quickstartRead the protocol
The wire format: the mandate, the key binding, the signed offer and the audit record.
Wire referenceConnecting an agent to OID4Pay is open to design partners during the developer preview. Talk to us.