What keeps working if SET's provider is down
SET API, SET Merchant API and SET Direct Deposit API
SET's provider converts currencies and moves money to and from banks. If it cannot be reached, calls that read or write its objects fail, and everything that SET answers from its own records or from the chain keeps working. This page lists today's behaviour only.
Keeps working
| What | Why it keeps working |
|---|---|
Events: GET /v1/events, GET /api/partner/events and webhook delivery | Events are stored and sent by SET from its own database |
| Monthly statements and year-end tax data | Built from SET's own ledger |
Payable Email payments into a payee's wallet, and payable_payment.in_wallet | You pay USDC on Base straight to the payee's own wallet; SET confirms the payment by reading the chain |
| A payment the provider had already accepted | It completes. SET's records catch up from the provider's signed events when it is reachable again (Flow of funds) |
Waits until the provider is back
- Verifying a new customer, and opening accounts or addresses.
- Bank payouts, and the bank leg of a Cash-Out Address or a Payable Email claim.
- Bank details shown to payers (
depositInstructions), which are read from the provider on each answer and never stored by SET.
Retry these with the same Idempotency-Key (Idempotency). Service status: simpleeasytransactions.com/status.