Saved Recipients

Create, list, update, and delete saved fiat and crypto recipients.

Saved recipients store reusable destination details for Stabyl Pro withdrawal workflows and account management. They are address book records, not payment instructions.

Endpoint	Purpose
POST /partner/wallets/recipients	Create a saved recipient
GET /partner/wallets/recipients	List saved recipients
PATCH /partner/wallets/recipients/{recipient_id}	Update recipient metadata
DELETE /partner/wallets/recipients/{recipient_id}	Delete a saved recipient

Fiat recipient creation should follow account verification with POST /partner/wallets/fiat/verify-account. Crypto recipients are saved addresses and metadata only.

Recipient Types

Type	Typical fields	Recommended validation
Fiat	bank code, account number, account name, display label	Verify account before saving
Crypto	asset rail, chain, address, display label	Confirm route and address format before saving

Use clear labels that operators can recognize in Stabyl Pro. Avoid labels that only make sense inside one internal service.

Saved recipients do not initiate withdrawals through the API.

Lifecycle

Action	Notes
Create	Store validated details for future use
List	Show current saved recipients for account review
Update	Change metadata or supported editable fields
Delete	Remove a saved recipient from future selection

Recipient routes require X-Api-Key enabled for recipient management. Common failures include a key that is not permitted for the action, invalid account details, duplicate recipient details, or a recipient identifier that does not exist.