Collections
SET API, SET Merchant API and SET Direct Deposit API · Staging · 2026-11-10
Everything you need to try SET before you write an integration. Import a collection, add a sandbox key, and run a recipe from its first call to its last event. Nothing a sandbox key does moves money, and every simulated result is labelled "Sandbox: simulated".
| Page | What it gives you |
|---|---|
| Postman collections | Two collections to download, one per API, with every documented call and a folder for each recipe |
| Recipes | Four complete integrations: exact-net payout, a Payout Safe, a marketplace split, and wallet everywhere |
| Simulators | The staging calls that stand in for money moving: payees, payments, deposits, payouts and balances |
| Sandbox scenarios | Rare outcomes on demand: a rejected verification, a request for information, a returned payout |
| OpenAPI documents | The three APIs as OpenAPI 3.1, for Insomnia, Bruno or a generated client |
Start in three steps
- Get a key. One call gives you a test key, without waiting for SET (Get a sandbox key).
- Import a collection into Postman and set the key variable (Postman collections).
- Run a recipe folder in order. On staging, each step that would need real money or a real signature runs its simulator instead (Recipes).
Staging and production
The collections point at staging (https://wallet-staging.simpleeasytransactions.com). Calls whose names start with "(staging)" are simulators. In production they answer 404, and the step they stand in for is yours: a real payment, a real signature, or a payee's own verification. Every other call works the same in production with a live key. See Environments and sandbox.