Overview
Sub-accounts allow you to create isolated Payaza accounts under your main merchant account for internal business units — for example, your Finance department, Admin team, or separate cost centers. Each sub-account operates independently for collections and payouts while remaining fully visible and controllable from your main account. Approved use cases:- Finance department — separate ledger for finance team operations and disbursements
- Admin unit — isolated account for operational expenses and vendor payments
- Cost centers — segment revenue and spend by internal division or project
Key Requirements
Use your public API key encoded in Base64. See the Authentication
guide for setup instructions.
Switch
X-TenantID to live when operating in the production environment.Endpoints
| Method | Endpoint | Description |
|---|---|---|
POST | /payaza-account/api/v1/subaccounts/merchant | Create a new sub-account |
GET | /payaza-account/api/v1/subaccounts/merchant/enquiry/{payazaSubAccountReference} | Retrieve sub-account details by reference |
How it works
Create the sub-account
Call the Create endpoint with the sub-account name and the required business
details. On success, you receive a
payazaSubAccountReference — store this
immediately against the relevant internal unit in your system.Use the sub-account for transactions
Pass the
payazaSubAccountReference in your transfer and collection
requests to route transactions to the correct internal unit.Create a sub-account
cURL
| Parameter | Type | Required | Description |
|---|---|---|---|
mainAccountPayazaReference | string | Yes | The account reference of the main Payaza account |
name | string | Yes | The name of this subaccount |
currency | string | Yes | The currency code |
country | string | Yes | The country code in ISO 3166-1 alpha-3 format |
Retrieve sub-account details
cURL
| Parameter | Type | Required | Description |
|---|---|---|---|
payazaSubAccountReference | string | Yes | The account reference of the Payaza sub account that has been created |
Compliance requirements
Sub-accounts are subject to your organization’s KYB (Know Your Business) approval. The following rules apply:- Sub-accounts must map to real, identifiable internal units within your organization
- Each sub-account must have a documented owner or responsible team
- Transaction flows through sub-accounts are audited — ensure all activity aligns with the stated purpose of the unit
- Do not create sub-accounts as pass-through accounts for unrelated third parties
Best practices
- Map each sub-account to exactly one internal unit — never share a reference across unrelated departments
- Store
payazaSubAccountReferencedurably in your database immediately after creation — it cannot be recovered if lost - Use the Enquiry endpoint to verify a sub-account’s status before routing live transactions to it
- Scope system access so that only the authorized team can initiate transactions from each sub-account
What’s next
Transfers
Send payouts from your Payaza account or sub-account to a beneficiary.
Payaza Account
View balances and account references across all currencies.