Core Integration Flows
This section provides comprehensive guides for implementing the complete customer lifecycle - from registration through to active payment operations.Customer Lifecycle Overview
Both Individual (B2C) and Organization (B2B) customers follow a linear flow with strict prerequisites at each phase. Operations are blocked until all requirements are met.Flow Timeline Comparison
| Phase | Individual (B2C) | Organization (B2B) |
|---|---|---|
| Registration | 5 minutes | 10 minutes |
| Personnel Setup | N/A | 20 minutes |
| Verification | 1-3 days (KYC) | 2-5 days (KYB) |
| Consent Acceptance | 5 minutes | 10 minutes |
| Activation | Instant | Instant |
| Operations | Ongoing | Ongoing |
| Total | ~1-3 days | ~2-5 days |
Individual Customer (B2C) - 7 Phases
Complete lifecycle for personal/individual customers.B2C Overview
Complete Individual customer flow guide
Phase 1: Registration
Customer registration with categorization
Phase 3: Verification
KYC verification process
Phase 5: Activation
Account activation & wallet creation
Organization Customer (B2B) - 8 Phases
Complete lifecycle for business/organization customers with multi-stakeholder management.B2B Overview
Complete Organization customer flow guide
Phase 2: Personnel
Directors, shareholders, employees
Phase 3: Verification
KYB verification process
Phase 8: Transactions
Business payment operations
Key Differences: B2C vs B2B
| Aspect | Individual (B2C) | Organization (B2B) |
|---|---|---|
| Registration | Single endpoint | Requires separate personnel endpoints |
| Personnel | N/A | Directors, Shareholders, Employees |
| First Employee | N/A | Must have ADMIN_USER role |
| Verification | KYC (Identity) | KYB (Business + UBO) |
| Approval Level | TENANT or POWER_TENANT | TENANT (medium-risk) |
| Consent Format | accepted: true | Requires acceptedBy + acceptedDate |
| Activation | Simple code | Requires activationReason + admin headers |
| Document Upload | Basic fields | Additional metadata (customerId, accountId, etc.) |
Critical Prerequisites
For Activation
For Transactions
Required before payment operations:
- Account status:
ACTIVE - Wallet status:
ACTIVE - Valid payment consent (for transfers)
- Pre-registered beneficiaries
Key Characteristics
Individual Customer (B2C)
- Risk-Based Processing: High-risk customers require power tenant approval
- Consent-Driven: Operations blocked until required consents accepted
- Smart Categorization: Feature-based customer categorization
- State Machine: Strict state transitions with no backward movement
Organization Customer (B2B)
- Multi-Stakeholder: Employees, Directors, Shareholders
- Role-Based Access: COMPLIANCE_OFFICER, TRANSACTION_APPROVER, ADMIN_USER
- Dual Record Creation: Organization + Individual records for personnel
- Enhanced Verification: KYB + UBO verification
Common Resources
Categorization
Smart categorization strategy
Error Handling
Error scenarios & troubleshooting
Best Practices
Implementation best practices
Quick Reference
Individual Customer Endpoints
| Phase | Endpoint | Method |
|---|---|---|
| Registration | /api/v2.1/customer/individual/registration | POST |
| Categorization | /api/v2.1/customer/individual/categorization/hierarchy/{tenantId} | GET |
| Session | /api/v2.1/customer/individual/{customerId}/users/{userId}/sessions | POST |
| Verification | /api/v2.1/customer/individual/{customerId}/verification | POST |
| Consents | /api/v2.1/customer/individual/{customerId}/consents/{type} | POST |
| Activation | /api/v2.1/customer/individual/{customerId}/activation | POST |
| Balance | /api/v2.1/fintrans/{accountId}/balance | GET |
| Beneficiaries | /api/v2.1/fintrans/{accountId}/beneficiaries | POST |
| Transfer | /api/v2.1/fintrans/{accountId}/types/transfer/prepare | POST |
Organization Customer Endpoints
| Phase | Endpoint | Method |
|---|---|---|
| Registration | /api/v2.1/customer/organization/registration | POST |
| Add Director | /api/v2.1/customer/organization/{orgId}/director | POST |
| Add Shareholders | /api/v2.1/customer/organization/{orgId}/shareholders | POST |
| Add Employee | /api/v2.1/customer/organization/{orgId}/employee | POST |
| Verification | /api/v2.1/customer/organization/{orgId}/verify | POST |
| Consents | /api/v2.1/customer/organization/{orgId}/consents/{type} | POST |
| Activation | /api/v2.1/customer/organization/{orgId}/activation | POST |
| Beneficiaries | /api/v2.1/fintrans/{accountId}/beneficiaries | POST |
| Payment Consent | /api/v2.1/fintrans/{walletId}/payment-consents/types/transfer | POST |
| Transfer | /api/v2.1/fintrans/{accountId}/types/transfer/prepare | POST |