SET API (Platforms) · Recipients & payouts
Create a recipient
POST/v1/recipients
A third party a customer pays from its custodial wallet: a supplier, a contractor, or the platform itself. The name and address are sealed at rest and appear in no event.
Platform key
party: {type: "platform"}needs platform funds allowed for the platform (403 platform_funds_not_allowed).
Headers
Idempotency-Keystring- Optional. The same key and body run once; a replay answers with
Idempotent-Replayed: true. Kept 24 hours.
Body
customerstringrequired- The paying customer.
partyobjectrequired{type: "business" | "individual", name, address: {country (alpha-3), streetLine1?, city?, state?, postalCode?}, legalEntityIdentifier?, firstName?, lastName?}, or{type: "platform"}: the platform itself, with the legal details SET registered for it.destinationobjectrequired{kind: "bank", currency, …}with the fields ofPOST /v1/bank_accountsin any of the six currencies (raildefaults from the currency);{kind: "wallet", chain, address}for any wallet, a Cash-Out Address included;{kind: "bridge_wallet", wallet}for another of your customers' custodial wallets;{kind: "email", email, chain?}for SET Payable Email.externalIdstring- Your id for the recipient.
Notes
- Bank numbers go to the provider only, held there in the recipient's name under the paying customer; an email goes to the sign-in provider only.
- Events
recipient.created,recipient.disabled.
Errors
400 party_invalid400 destination_invalid400 currency_invalid400 rail_invalid400 bank_details_refused400 chain_invalid400 address_invalid400 wallet_type_invalid400 recipient_is_customer400 external_id_invalid404 wallet_unknown409 platform_details_incomplete403 platform_funds_not_allowed403 payable_email_merchant403 payable_email_off503 payable_email_disabled503 recipients_unavailable401 api_key_required401 api_key_invalid401 api_key_wrong_mode403 scope_missing429 rate_limited