Skip to main content
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 with type: "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".

Authorizations

public-api-key
string
header
default:<Your public-api-key>
required
private-secret-key
string
header
default:<Your private-secret-key>
required

Path Parameters

recipient_id
string
required

ID of the recipient

onboarding_id
string
required

ID of the onboarding to continue

Body

application/json
account_id
string
required

Unique id of the account in Yuno

Example:

"9104911d-5df9-429e-8488-ad41abea1a4b"

type
enum<string>
required

Type of onboarding flow. Only TWO_STEP_ONBOARDING can be continued.

Available options:
TWO_STEP_ONBOARDING
Example:

"TWO_STEP_ONBOARDING"

workflow
enum<string>
required

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.

Available options:
HOSTED_BY_PROVIDER,
DIRECT
Example:

"HOSTED_BY_PROVIDER"

callback_url
string<uri>

URL in case to redirect your customer after the onboarding process with the provider, if needed.

Example:

"https://www.google.com"

provider
object
documentation
object[]

Specifies the documentation object.

withdrawal_methods
object

Specifies the withdrawal methods object.

Object to indicate the owners of the organization. Adyen, Stripe and dlocal have fields related to that.

terms_of_service
object

Object describing terms of service.

Response

Created

id
string

The unique identifier of the recipient.

Example:

"3aaa4d82-11e8-48ce-8ef5-04eee3a10802"

account_id
string

The account identifier associated with this recipient.

Example:

"fe14c7c6-c75e-43b7-bdbe-4c87ad52c482"

merchant_recipient_id
string

Unique identifier of the recipient defined by the merchant.

Example:

"MERCHANT_182acf1d-faeb-4ff0-94cd-7fab11b282f6"

national_entity
string

Beneficiary's national entity type.

Example:

"INDIVIDUAL"

entity_type
string

Beneficiary's type of organization.

Example:

"PRIVATE"

first_name
string

Beneficiary's name.

Example:

"Juan"

last_name
string

Beneficiary's last name.

Example:

"Perez"

Beneficiary's legal name.

Example:

null

email
string

The Beneficiary's email.

Example:

"juan.perez@example.com"

date_of_birth
string

Beneficiary's date of birth.

Example:

"1990-01-15"

country
string

The Beneficiary's country.

Example:

"CO"

website
string

The seller's website URL.

Example:

"https://juanperez.com"

industry
string

The seller's industry.

Example:

"Technology"

merchant_category_code
string

The merchant category code (MCC) (MAX 235; MIN 1).

Example:

"5734"

document
object
phone
object
address
object
withdrawal_methods
object
documentation
object[]
onboardings
object[]
split_configuration
object

Rules for automatic split calculation at the recipient level.

created_at
string<date-time>

Recipient creation date (ISO 8601 MAX 27; MIN 27).

Example:

"2025-08-27T15:41:19.497413Z"

updated_at
string<date-time>

Last Recipient updated date (ISO 8601 MAX 27; MIN 27).

Example:

"2025-08-27T15:41:19.497425Z"