Sokin Embedded API
  1. Onboarding Models
Sokin Embedded API
  • Getting Started
    • Sokin Definitions
    • Guides
      • Authentication
      • Receiving Payments
      • FX Payments
      • Payments
      • Unfunded Payments
      • Unfunded FX Payments
      • Corporate Onboarding
        • Data Requirements
        • Step 1: Create a corporate profile
        • Step 2: Add associates
        • Step 3: Add a parent entity (if applicable)
        • Step 4: Upload company documents
        • Step 5: Upload associate documents
        • Real-time Status Updates via Webhook
        • Conditional Step: Upload Parent Entity documents (if applicable)
        • Step 6: Finalise onboarding submission
        • Uploading supporting documents using Pre-signed URLs
        • Onboarding Reference Data
        • Onboarding Models
          • Data-Only model
          • Supported Jurisdictions & National ID Requirements
      • Payments Reference Data
        • Purpose of Payment
        • Transfer Reasons
        • Beneficiary Fields
  • Authentication
    • Get Token
      POST
    • Get Token on behalf of corporate
      POST
    • Schemas
      • TokenResponse
  • Corporates
    • v2025-12-01
      • Create a new Corporate
      • Add a parent entity (corporate associate) to an onboarding request
      • Add an associate to a corporate onboarding request
      • Request pre-signed URLs for onboarding document uploads
      • Request pre-signed URLs for parent entity document uploads
      • Request pre-signed URLs for associate document uploads
      • Finalise corporate onboarding submission
    • Schemas
      • NumericRange
      • ApiResponse[AddIndividualAssociateResponse]
      • ApiResponse[AddAssociateDocumentsResponse]
      • ApiResponse[AddOnboardingDocumentsResponse]
      • AddOnboardingDocumentsResponse
      • AssociateDocumentPresignedUrlResponse
      • AssociateType
      • ErrorResponse
      • MessageResponse
      • FinaliseSubmissionResponse
      • AddParentEntityRequest
      • MoneyRange
      • AddOnboardingDocumentsRequest
      • ApiResponse[CreateCorporateResponse]
      • CreateCorporateRequest
      • CreateCorporateResponse
      • FinaliseSubmissionRequest
      • PresignedUrlResponse
      • AddressTypeEnum
      • OwnershipType
      • AddAssociateDocumentsResponse
      • ErrorDetail
      • AddIndividualAssociateRequest
      • UboDetails
      • AddParentEntityResponse
      • AddIndividualAssociateResponse
      • CorporateAssociateType
      • AddParentEntityDocumentsRequest
      • AssociateDocumentPresignedUrlResponseItem
      • ApiResponse[AddParentEntityResponse]
      • AssociateIdentityType
      • AddAssociateDocumentsRequest
  • Corporate Currency Accounts
    • v2025-12-01
      • Get Corporate Currency Accounts
      • Get Corporate Currency Account By Reference
    • Schemas
      • ErrorResponse
      • PaginationInfo
      • ErrorDetail
      • ApiResponse[GetCCAByReferenceResponse]
      • GetCCAByReferenceResponse
      • GetCCAByReferenceResponsePayInDetail
      • GetCCAsResponseItem
      • PaginatedApiResponse[GetCCAsResponseItem]
  • Beneficiaries
    • v2025-12-01
      • Get Beneficiary Fields
      • Create External Beneficiary
      • Get Beneficiary List
      • Get Beneficiary Details
      • Delete Beneficiary
    • Schemas
      • ErrorResponse
      • FieldType
      • IdentifierType
      • TransactionTypeEnum
      • BeneficiaryType
      • AccountType
      • ApiResponse[BeneficiaryDetails]
      • ApiResponse[CreateExternalBeneficiaryData]
      • ApiResponse[DeleteBeneficiaryData]
      • ApiResponse[GetBeneficiaryFieldsResponse]
      • BeneficiaryField
      • BeneficiaryListItem
      • CreateExternalBeneficiaryData
      • CreateExternalBeneficiaryRequest
      • DeleteBeneficiaryData
      • GetBeneficiaryFieldsResponse
      • PaginatedApiResponse[BeneficiaryListItem]
      • StateOrProvince
      • PaginationInfo
      • PaginatedBeneficiaryFieldsResponse
      • ErrorDetail
      • BeneficiaryDetails
  • Instruction Requests
    • v2025-12-01
      • Get Instruction Request By Reference
      • Create Payment Instruction Request
      • Create Fx Instruction Request
      • Create Fx Payment Instruction Request
      • Create Unfunded Payment Instruction Request
      • Create Unfunded Fx Payment Instruction Request
    • Schemas
      • ErrorResponse
      • ApiResponse[CreateInstructionRequestResponse]
      • ErrorDetail
      • ApiResponse[GetInstructionRequestResponse]
      • CreateFXInstructionRequest
      • CreateFxPaymentInstructionRequest
      • CreateInstructionRequestResponse
      • CreatePaymentInstructionRequest
      • CreateUnfundedFxPaymentInstructionRequest
      • CreateUnfundedPaymentInstructionRequest
      • GetInstructionRequestResponse
  • Instructions
    • v2025-12-01
      • Get Instruction By Reference
    • Schemas
      • ErrorDetail
      • ErrorResponse
      • ApiResponse[GetInstructionResponse]
      • GetInstructionResponse
  • Foreign Exchange
    • v2025-12-01
      • Get Fx Rate
    • Schemas
      • ErrorResponse
      • FxRateData
      • FixedSide
      • ApiResponse[FxRateData]
      • ErrorDetail
      • FxRateRequest
  • Webhooks
    • Webhooks
    • v2025-12-01
      • Create Subscription
      • Update Subscription Status
      • Update Subscription
      • Delete Subscription
      • Get Subscription By Id
      • List Notification Logs
      • Retry Notification
    • Schemas
      • ApiResponse[CreateSubscriptionResponse]
      • NotificationStatus
      • ApiResponse[NotificationLogList]
      • NotificationAttemptResponse
      • ApiResponse[UpdateSubscriptionResponse]
      • NotificationLogList
      • ErrorResponse
      • NotificationLogResponse
      • SubscriptionCreateOrUpdate
      • SubscriptionStatusUpdate
      • CreateSubscriptionResponse
      • UpdateSubscriptionResponse
      • InstructionCreated
      • ErrorDetail
      • InstructionReqeustRejected
      • InstructionProcessedWebhook
      • InstructionRejectedWebhook
      • OnboardingRequestApproved
      • OnboardingRequestRejected
      • CorporateActivated
      • CorporateDeactivated
      • CorporateCurrencyAccountFundingReceived
      • WebhookSubscription
      • WebhookNotificationLogs
  1. Onboarding Models

Data-Only model

The Data-Only model enables streamlined onboarding in tightly controlled scenarios.
This model is exclusively available when strict eligibility criteria are met and has been enabled by Sokin for your integration. It is not selectable via API and applies only to approved use cases that satisfy the defined jurisdictional and risk conditions.

Eligibility criteria:#

The Data-Only model applies when:
The corporate entity is registered in the United States
At least one Director or UBO is either:
A US resident, or
A resident of a supported jurisdiction
If eligibility conditions are not met at any stage of the onboarding flow, the system will automatically transition the onboarding session to the appropriate due diligence model (typically Non-Reliance).
The API response will clearly indicate:
The updated due diligence model
Any additional document or data requirements
Once a model transition has occurred, it cannot be reverted within the same onboarding session. If you wish to proceed under the same model, a new onboarding request must be created.
This ensures compliance is maintained without disrupting your integration flow.

Model characteristics#

The Data-Only model is designed to reduce document friction while preserving regulatory screening and oversight.
Key characteristics:
Corporate document uploads are not required at submission stage
Associate documentation is limited to proof of identity (Passports only).
Parent entity documentation may be requested depending on structure and risk
Full compliance screening is still performed before account issuance
All Data-Only applications remain subject to regulatory screening, sanctions checks, and internal risk assessment prior to approval.

Data scope#

Although document uploads are reduced, the following information categories must still be submitted via the Create a new corporate API:
1. Corporate information
Registered legal name
Registration number
Jurisdiction of incorporation (must be US only)
Registered address
Business activity details
Corporate tax identification number (EIN)
Corporate website
Business description
2. Business identification information
Government-issued identification details
Tax identification number (where applicable)
All submitted information must be complete and accurate. Incomplete or inconsistent data may result in model escalation or review delays.

Associate constraints (Data-Only)#

Additional eligibility rules apply at associate level.

Residency requirement#

At least one qualifying associate must meet residency requirements:
LTD / LLC / PLC / Pty Ltd
At least one Director must be US-based or resident of a supported jurisdiction
LLP
At least one Partner must meet residency requirements
Sole Trader
The Sole Trader must meet residency requirements

Identity requirements#

Passport required as proof of identity
SSN required for US residents
National ID number required where mandated by jurisdictional screening rules
Screening requirements are determined by the associate’s residence country and regulatory configuration.

Parent entity structures#

If a layered ownership structure exists:
Parent entity information must still be declared
Documentation requirements may be reduced, but risk-based review still applies
The same jurisdiction and associate residency eligibility criteria applicable to the primary onboarding entity also apply to the parent entity and its associates
For example:
If the primary corporate entity must be registered in the United States to qualify for the Data-Only model, the parent entity must also meet the same US registration requirement.
If at least one Director or UBO of the onboarding entity must be a US resident or resident of a supported jurisdiction, the same requirement applies to the parent entity’s Directors and UBOs.
If a parent entity introduces associates who do not meet residency eligibility criteria, the application may no longer qualify for the Data-Only model.
If risk thresholds are exceeded, or if parent entity eligibility requirements are not met, the application may be escalated to a full-document due diligence model.

Automatic model transition#

The Data-Only model is continuously validated during onboarding.
If:
Jurisdictional criteria are not met
Ownership structure introduces elevated risk
Required identity conditions are not satisfied
The system will automatically migrate the onboarding session to the appropriate due diligence model.
The API response will indicate the model change and additional requirements.
Modified at 2026-02-20 08:22:05
Previous
Onboarding Models
Next
Supported Jurisdictions & National ID Requirements
Built with