KYB Session Process Guide
What is KYB?
KYB (Know Your Business) is the business identity verification process that a Business User must complete in order to reach the REGULAR KYB level. This level is a prerequisite for creating an operational account on the Ralio platform.
Prerequisites
Before starting the KYB process, make sure you have the following:- A valid API Key with access to the management endpoints.
- The Business User already created on the platform. Use the endpoint below if you haven’t done so yet:
Once created, you will receive the
uid(unique identifier of the Business User). Thisuidis required in all subsequent steps. - The business documentation ready to upload (at minimum, all mandatory documents).
Step 1 — Create a KYB Session
Using the Business User’suid, the next step is to create a KYB Session. This session acts as the container where all documents uploaded during the verification process will be associated.
Endpoint:
| Parameter | Type | Description |
|---|---|---|
uid | string | Business User ID |
| Field | Type | Description |
|---|---|---|
id | string | KYB Session ID — save this value |
kybId | integer | KYB ID associated with the Business User |
documents | array | List of documents (initially empty) |
createdAt | string | Creation date and time |
updatedAt | string | Last update date and time |
⚠️ Important: Save theidfield from the response. This is thesessionIdyou will need in the following steps.
Step 2 — Upload documentation
Using thesessionId obtained in the previous step, proceed to upload all required documents. Each document is uploaded individually through the upload endpoint.
Endpoint:
| Parameter | Type | Description |
|---|---|---|
uid | string | Business User ID |
sessionId | string | KYB Session ID |
| Field | Type | Required | Description |
|---|---|---|---|
category | string | Yes | Document category. Value: COMPANY_INFO |
type | string | Yes | Document type. E.g.: MEMORANDUM_ARTICLES, BUSINESS_NUMBER, etc. |
file | file | Yes | The document file |
Document category
| Document | type value | Mandatory |
|---|---|---|
| Memorandum and Articles of Association | MEMORANDUM_ARTICLES | Yes |
| Business Number | BUSINESS_NUMBER | Yes |
| Proof of Company Address (utility bill, bank statement, etc.) | PROOF_OF_ADDRESS | Yes |
| Certificate of Directors and Shareholders Register | DIRECTORS_SHAREHOLDERS_REG | Yes |
| Recent Financial Statements (balance sheets, audited financial statements if available) | FINANCIAL_STATEMENTS | No |
| Business Licenses & Permits | LICENSES_PERMITS | No |
| Any other relevant documents (contracts, audit reports, etc.) | OTHER | No |
File restrictions:
Maximun size: 10MBAccepted formats: PDF (.pdf), Excel (.xlsx, .xls), Word (.docx, .doc), Images (.jpg, .jpeg, .png)
Document considerations
- All mandatory documents must be uploaded before the session can be submitted for review.
- Additional (optional) documents can also be uploaded up until the moment of submission.
- You can delete an already-uploaded document using the delete endpoint, but only before submitting the session for review.
- You can list the documents uploaded to the session at any time.
| Action | Method | Endpoint |
|---|---|---|
| List documents | GET | /api/v1/account/business-user/{uid}/kyb-sessions/{sessionId}/documents |
| Delete document | DELETE | /api/v1/account/business-user/{uid}/kyb-sessions/{sessionId}/documents/{documentId} |
Step 3 — Submit the session for review
Once all mandatory documents have been uploaded, the next step is to submit the KYB Session to the Compliance team for review. This action is irreversible. Endpoint:| Parameter | Type | Description |
|---|---|---|
uid | string | Business User ID |
sessionId | string | KYB Session ID |
🚫 From this point on:
- No more documents can be uploaded to the session.
- No uploaded documents can be deleted.
- The session will transition to the IN REVIEW state.
Step 4 — Compliance team review
Once submitted, the KYB Session enters the IN REVIEW state and is handled internally by Ralio’s Onboarding Compliance team. During this phase:- The Compliance team reviews all submitted documentation.
- Related Parties are declared (individuals linked to the business, such as partners, directors, beneficial owners, etc.).
- A KYC Session is generated for each Related Party, so they can complete their own individual identity verification process.
- If necessary, the Compliance team may request additional information or documentation.
Where can you track the process status?
This information is visible in two places within the Portal:- Inside the Business User profile — detailed view of the business entity.
- Onboarding Business section — global view of the onboarding process.
Step 5 — KYC for Related Parties
The Related Parties declared by the Compliance team must complete their KYC (Know Your Customer) process, i.e., individual identity verification. This process runs in parallel with the KYB review and is managed through the corresponding KYC Sessions.ℹ️ The KYC process for Related Parties is a requirement for the KYB Session to be approved.
Step 6 — Approval and REGULAR level activation
Once the review process has been successfully completed:- The KYB Session is approved by the Compliance team.
- The Business User’s KYB level changes from LIGHT → REGULAR.
- The Merchant is notified via a webhook with the corresponding KYB level change event.
💡 Make sure your webhook endpoint is properly configured to receive this notification. You can check the Webhooks Events section in the documentation.