Continue Onboarding
Resume a recipient’s onboarding after providing additional required data or documentation
Prerequisites
This endpoint requires a prior Create Onboarding call withtype: "TWO_STEP_ONBOARDING" where the account creation step has been completed successfully. This is the second step in two-step onboarding flows for the split payments marketplace.
The continue process supports two workflow types:
- HOSTED_BY_PROVIDER: Returns a Yuno redirect URL that logs activity and redirects to the provider’s KYC interface. Use
workflow: "HOSTED_BY_PROVIDER". - DIRECT: Processes KYC validation directly without external redirects. Use
workflow: "DIRECT".
Supplying a bank account
For an existing Zoop or Pagar.me provider recipient, an explicitwithdrawal_methods.bank is confirmed through the bank-update path before KYC continues. This includes the first bank account on an existing seller.
After the provider confirms the bank, Yuno saves it for the selected onboarding and continues KYC without resending the bank. The recipient default is unchanged. A successful bank update does not mean KYC is complete: the onboarding can still require identity documents or other information.
A definite bank refusal returns 400; an unconfirmed result returns 409. In either case, KYC is not started by that request and the unconfirmed bank is not saved. Follow the bank error and retry guidance before retrying. If the bank succeeds but a later KYC step fails, the bank change is not rolled back.
Other providers and initial onboarding without a provider recipient ID retain their existing continuation behavior.Authorizations
Path Parameters
ID of the recipient
ID of the onboarding to continue
Body
Unique id of the account in Yuno
"9104911d-5df9-429e-8488-ad41abea1a4b"
Type of onboarding flow. Only TWO_STEP_ONBOARDING can be continued.
TWO_STEP_ONBOARDING "TWO_STEP_ONBOARDING"
Workflow of the KYC process. HOSTED_BY_PROVIDER calls create KYC service and returns Yuno URL that redirects to provider. DIRECT calls create KYC service and processes KYC directly.
HOSTED_BY_PROVIDER, DIRECT "HOSTED_BY_PROVIDER"
URL in case to redirect your customer after the onboarding process with the provider, if needed.
"https://www.google.com"
Specifies the documentation object.
Specifies the withdrawal methods object.
Object to indicate the owners of the organization. Adyen, Stripe and dlocal have fields related to that.
Object describing terms of service.
Response
Created
The unique identifier of the recipient.
"3aaa4d82-11e8-48ce-8ef5-04eee3a10802"
The account identifier associated with this recipient.
"fe14c7c6-c75e-43b7-bdbe-4c87ad52c482"
Unique identifier of the recipient defined by the merchant.
"MERCHANT_182acf1d-faeb-4ff0-94cd-7fab11b282f6"
Beneficiary's national entity type.
"INDIVIDUAL"
Beneficiary's type of organization.
"PRIVATE"
Beneficiary's name.
"Juan"
Beneficiary's last name.
"Perez"
Beneficiary's legal name.
null
The Beneficiary's email.
"juan.perez@example.com"
Beneficiary's date of birth.
"1990-01-15"
The Beneficiary's country.
"CO"
The seller's website URL.
"https://juanperez.com"
The seller's industry.
"Technology"
The merchant category code (MCC) (MAX 235; MIN 1).
"5734"
Rules for automatic split calculation at the recipient level.
Recipient creation date (ISO 8601 MAX 27; MIN 27).
"2025-08-27T15:41:19.497413Z"
Last Recipient updated date (ISO 8601 MAX 27; MIN 27).
"2025-08-27T15:41:19.497425Z"