Create Entity Onboarding (Banking Connectivity)
Onboard an existing entity with a banking connectivity provider using KYC or KYB documentation
Onboarding types
ONE_STEP: Submit all information, compliance declarations, risk assessment, and documents at once. The provider processes immediately.PREVIOUSLY_ONBOARDED: Generate an internal Yuno onboarding ID without contacting the provider. Use when the entity was already onboarded externally.
ONE_STEP, include compliance_declaration, risk_assessment, source_of_funds, and documentation. See Documentation types for the full list of supported document types.
Monitor progress via Get Entity Onboarding Status or webhook events. See Onboarding statuses for the full status lifecycle.Headers
Unique identifier used in HTTP headers to ensure that a request is processed only once, even if it is retried due to network issues or timeouts. See authentication for details (UUID).
Path Parameters
The id of the entity obtained from Create Entity.
Body
The unique identifier of the merchant's Yuno account (UUID, 36 characters).
"550e8400-e29b-41d4-a716-446655440000"
The pre-configured Banking Connectivity provider connection identifier.
"conn_550e8400-e29b-41d4-a716-446655440001"
The onboarding workflow type. ONE_STEP submits all information at once for provider processing. PREVIOUSLY_ONBOARDED generates an internal Yuno ID without contacting the provider.
ONE_STEP, PREVIOUSLY_ONBOARDED "ONE_STEP"
Legal agreements accepted by the entity. Required for ONE_STEP onboarding.
Pre-existing compliance screening results provided by the merchant.
AML/KYC information about the source of funds.
KYC/KYB documents. Each item uses a type discriminator to determine which sub-object to populate. Supported types: IDENTITY_DOCUMENT, PROOF_OF_ADDRESS, BANK_STATEMENT, BUSINESS_DOCUMENT, TAX_INFORMATION, FINANCIAL_DOCUMENT, BIOMETRIC_VERIFICATION, EMPLOYMENT_INFORMATION.