Skip to main content
Sent when a reviewer rejects a payout destination. A rejected destination never becomes usable, and a withdrawal to it fails with DESTINATION_REJECTED. Like other events on an account, a platform on event_source connect receives it for the accounts it owns, and the account itself receives it on account. See Connect events.

​
Event fields

​
string
The event’s unique identifier, prefixed evt_. Use it to deduplicate deliveries.
​
string
Always payout_destination.rejected.
​
string
When the event occurred, in UTC.
​
string
The account that owns the destination.
​
string
The owning account’s id, repeated at the top level. Present only when the account has a parent. This is how a platform tells which of its accounts the event concerns.
​
string
The destination’s id, prefixed pd_. The same id the payout destinations endpoints return.
​
string
bank_account, mobile_money or crypto_wallet.
​
string
The destination’s currency, as an ISO 4217 code.
​
string
rejected.
​
string | null
The reviewer’s note when there is one, otherwise a plain explanation. Null when the destination was approved without a note.
​
boolean
Always false on this event.
​
boolean
Whether it is the account’s default destination for its currency.
​
string | null
When a person reviewed it, in UTC. Null when the system decided on its own.
No account number, bank detail or wallet address is sent. Fetch the destination to read those.

​
What to do on receipt

Show data.status_reason to the account holder and ask them for a different bank account, mobile money number or wallet. Register a new destination. Editing the rejected one sends it back to review rather than approving it.