Swipelux
Business Onboarding

KYB Workflow

Follow the business onboarding flow from customer creation to KYB review.

KYB Workflow

Integration Flow

1. Create Business Customer

POST /v1/customers/business

Include the core business profile fields. KYB can then move into ownership and document review.

2. Add Or Update Shareholders

POST /v1/customers/business/{id}/shareholders

Add shareholders, UBOs, control persons, directors, and signers with the shareholder endpoints.

3. Get Required Documents

GET /v1/meta/kyb/documents

Retrieve the document list for the business jurisdiction.

4. Upload Required Documents

POST /v1/documents

Upload each required document as a base64-encoded file. Send customerId for business-owned KYB documents or shareholderId for shareholder evidence. The endpoint returns normalized document state with status.

5. Check Verification Status

GET /v1/customers/business/{id}

Monitor the verificationStatus field until review reaches approved or rejected.

6. Request Business Rail Applications

GET /v2/customers/business/{customerId}/rails
POST /v2/customers/business/{customerId}/rail-applications
GET /v2/customers/business/{customerId}/rail-applications

Business rail access is reviewed per rail. List business rail states first, then submit one or more available rails in a batch:

{
  "data": [
    { "rail": "pse" },
    { "rail": "ach_named", "banks": ["jpmorgan_chase"] }
  ]
}

Successful rails are returned as application resources in data. Unsupported or blocked rails are returned as item-level errors, so one blocked rail does not prevent another rail in the same batch from moving into review.

These v2 business rail routes do not create or update global KYB verdicts. They expose per-rail status, reasons, requirements, selected banks, and timestamps.


Enhanced Due Diligence (EDD) Triggers

EDD may be required for:

  • High-risk jurisdictions
  • High-risk verticals (gaming, trading, crypto exchanges)
  • Complex ownership structures
  • Expected monthly volume exceeding thresholds
  • Operations involving sanctioned countries

Outcome: KYB approval, conditional approval with caps, or rejection.


Verification Timeline

StageTypical Duration
Document UploadImmediate
Initial Review1-2 business days
Standard KYB2-5 business days
EDD (if triggered)5-10 business days

Common Rejection Reasons

ReasonResolution
Missing documentsUpload all required document types
Unclear/blurry documentsRe-upload higher quality scans
Mismatched informationMake sure the entity name matches exactly across all documents
Incomplete ownership structureProvide documentation for 100% ownership
Expired documentsProvide current/valid documents

On this page