Update Recipient
Update the details of an existing marketplace recipient, identified by its recipient_id.
Bank-account updates
For Zoop and Pagar.me onboardings with a provider recipient ID, an explicitwithdrawal_methods.bank update waits for the provider result. Other recipient fields retain their existing update behavior.
Without onboarding_id, Yuno combines the bank fields you send with the recipient’s saved bank account to form one account for eligible onboardings. It does not combine your request with each provider’s different bank account. Send a complete account if the saved account does not provide the missing fields. Accepted account types are CHECKINGS and SAVINGS.
With onboarding_id, the bank update targets only that onboarding and leaves the recipient default and other onboardings unchanged. Omitted fields come from the onboarding’s saved account, or the recipient default if the onboarding has no saved bank record. If the onboarding shows no bank account, send a complete account.
For example, a store changes its payout account from A to B. Zoop confirms B, but Pagar.me does not confirm the change. Yuno keeps B for Zoop, preserves Pagar.me’s previous saved account, and updates the recipient default to B. The request returns an error describing the outcomes. An error does not mean every provider stayed unchanged. Successful provider changes are not rolled back.
The recipient default advances after at least one provider confirms the update. If every attempted provider refuses or has an unknown result, the old default remains. When there is no eligible provider-bound target, the account can be saved locally. Reading a saved account from Yuno is not an independent confirmation of an unknown provider outcome.
Bank updates do not apply to onboardings in ERROR, BLOCKED, CANCELLED, INACTIVE, TRANSFERRED or TERMINATED. Targeting one of them (with onboarding_id, Update Onboarding or Continue Onboarding) returns 400 INVALID_STATE; a recipient-level update without onboarding_id skips them and keeps their previous account.
Bank errors and retries
Authorizations
Body
ID of an existing onboarding belonging to the recipient. When set, the identity fields sent in this request (e.g. first_name, email, phone, address) are stored as a per-onboarding override for that onboarding only, without modifying the shared recipient; when omitted, the update applies to the shared recipient and propagates to all non-terminal onboardings. Request-only, not returned in responses or webhooks.
"1b9d6bcd-bbfd-4b2d-9b5d-ab8dfbbd4bed"
Response
Recipient updated successfully