Recipients for Marketplace
Continue Onboarding
Resume a recipient’s onboarding after providing additional required data or documentation
POST
Continue Onboarding
Continues the onboarding process for a recipient. This endpoint is used for two-step onboarding flows to execute the KYC step after account creation.
This endpoint continues the onboarding process for a recipient, specifically executing the KYC (Know Your Customer) step in two-step onboarding flows. Use this when you need to complete KYC validation after account creation has been completed via Create Onboarding.
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
Body
application/json
Response
Created