Overview
Beneficiaries are the recipients of your payouts. This guide covers best practices for managing them at scale — creating different types, attaching multiple payment instruments, and handling common scenarios.Individual vs. business beneficiaries
Choose the right type based on who you’re paying:| Type | Use when | Required fields |
|---|---|---|
individual | Paying a person (freelancer, contractor, employee, refund customer) | first_name, last_name, country, currency |
business | Paying a company (supplier, vendor, partner) | company_name, country, currency |
Adding payment instruments
A beneficiary can have multiple instruments — different ways to receive payment. For example, a contractor might have both a US bank account and a UK bank account.Create the beneficiary first
Then add instruments
Listing and filtering
Retrieve beneficiaries with pagination:Deletion considerations
When you delete a beneficiary:- In-progress payouts to that beneficiary will still complete
- New payouts to that beneficiary will fail
- Historical data (completed payouts) is preserved for audit
Best practices
Validate bank details early
Validate bank details early
Create beneficiaries and verify their details well before you need to send a payout. This catches errors (wrong account number, invalid routing number) before time-sensitive payments.
Use email for notifications
Use email for notifications
Include the beneficiary’s email when creating them. This allows Anton to send delivery confirmations where applicable.
One beneficiary per recipient
One beneficiary per recipient
Don’t create duplicate beneficiaries for the same person. Use instruments to add multiple payment methods to a single beneficiary.
Store your mapping
Store your mapping
Keep a mapping between your internal user/vendor IDs and Anton beneficiary IDs. This makes it easy to create payouts from your business logic.