Guides
Five recipes, each one a task somebody actually has to do: first authorization, sandbox, seller-side checks, escrow, and the day you switch on enforcement.
Concepts explain the model; the API reference is the contract. These are the recipes in between — each one a task somebody actually has to do, start to finish, with the parts that bite in production called out where they bite.
Your first authorization
From an issued key to a signed verdict, all in the sandbox
Test in the sandbox
What is real and what is simulated, and how to force each of the eight verdicts on purpose
Accept a signed approval
The seller's side: verify a buyer's approval yourself, without a Saifuro account
Escrow a deal end to end
Create, fund, deliver, attest, with a webhook receiver you can copy
Before you switch on enforcement
The checklist between observe mode and the first blocked payment
Which one you want
Start with the first authorization. It is the whole product end to end and costs nothing to run.
Sandbox tells you how to make each verdict happen on demand, which is how you test the branches you hope never fire.
Accept a signed approval is written for someone who will never hold a Saifuro key.
Go live collects everything from elsewhere in these docs that the switch day is too late to look up.