Payout methods
Keeping your beneficiaries’ payout method details in sync means keeping their recipient records - the API objects that store each individual payout method - up to date.
Beneficiary (end‑user): the person or business that owns the payout methods.
Payout method: a bank account, E-wallet, card or similar destination.
Recipient: the API resource that stores one payout method. A beneficiary can therefore have several recipients.
Real-time updates
To maintain the most current recipient information, we strongly advise setting up webhooks and subscribing to RECIPIENT.*
event types.
This ensures your system is immediately notified of any changes or updates to recipient details, such as when a beneficiary adds, updates, or removes their information through a management session.
For detailed instructions on how to set up and manage webhooks, please refer to our webhooks guide.
Retrieving recipient data via API
While webhooks notify you of changes, the way to get the complete, updated recipient details is to call the API after you receive a relevant webhook event.
1. Get Recipient by ID
After receiving a webhook for a specific recipient, you should use the id
from the webhook event to retrieve their full, updated details.
This is the most direct way to get the latest information because all RECIPIENT.*
webhook events include the id
of the affected recipient.
GET /beneficiaries/organizations/recipients/{recipientId}
2. List recipients by external user ID
You can retrieve all recipients associated with a specific one of your end-users using the ID you provided when creating the management session. This endpoint is helpful if you want to synchronize the state of all recipients for a given end-user or to simply list all recipients they have added.
GET /beneficiaries/organizations/recipients
Query parameters:
The identifier of the end-user whose recipients you want to retrieve.