Skip to main content

BRICK SUB ACCOUNT

One platform.
Every account in context.

Create and manage dedicated Sub-Accounts through the API, then switch between account contexts in Brick Dashboard. Keep each client's operational view clear as your platform grows.

Contact SalesExplore the workflow
Team managing dedicated account contexts together

BUILT FOR YOUR OPERATIONS

One clear account context for every client

Serve many users without mixing their day-to-day activity. Each Sub-Account has a distinct place in your platform's operating flow.

Payroll administrator reviewing reports at his desk

Payroll platforms

Keep each client company's payment operations in its own account context.

Freelance designer working with a drawing tablet

Freelancer marketplaces

Create dedicated account contexts as new users join your platform.

Small business team reviewing operations

SME aggregators

Separate the activity of merchants or branches while managing them from one platform.

FROM SETUP TO DAILY WORK

A distinct workspace for each account

Create accounts through the API, then use Brick Dashboard to move between them. The selected account determines the operational view your team sees.

  1. 01

    Create a Sub-Account

    Set up a dedicated account through the API for a client, merchant, or business unit.

  2. 02

    Choose the account

    Open the account switcher in Brick Dashboard and select the context you need.

  3. 03

    Work in context

    Review the balance, transaction history, and configuration for the selected account.

Brick Dashboard · Sub-Account view

ACCOUNT ACCESS

Choose the access that fits each client

Use Full-Access when a client needs API credentials, or Ledger-Only when the account is operated from the dashboard.

01

Full-Access

For clients that need their own API integration.

  • Own client ID and client secret
  • Activation after KYB verification
  • Key status controlled by the main account
02

Ledger-Only

For an account operated through the dashboard.

  • No direct API access
  • Transactions available through the dashboard
  • Can be upgraded when needed

PLATFORM CONTROLS

Manage the full account lifecycle

Keep account setup and access changes in the same integration flow as your platform grows.

Automated provisioning

Create Sub-Accounts programmatically through the API.

Credential management

Manage access for each Sub-Account as its needs change.

Key rotation

Regenerate credentials when they need to be replaced.

Request verification

Use the documented signing and public-key flow for API requests.

SECURITY & AUTHENTICATION

Keep account access under control

Plan request signing, public-key setup, and credential handling as part of the Sub-Account workflow.

Signed requests

Use X-Signature to verify that API requests come from the expected source.

Encrypted credentials

Handle Sub-Account credentials using the documented key setup and response flow.

Private-key control

Keep the private key in your own environment; upload the corresponding public key as required.

DEVELOPER PREVIEW

From account setup to an API response

See how a Sub-Account request fits into the integration flow. The example below is illustrative; use the current API reference for exact fields and requirements.

Explore API References
Illustrative request 
POST /v2/payments/general/b2c/sub-accounts

{
  "name": "PT Contoh Klien",
  "subAccountCode": "CLI01"
}
Review the current documentation before implementation

DEVELOPER RESOURCES

Find the reference for each step

Move from account setup to authentication and credential management with the published Brick documentation.

Open documentation
  1. 01

    Sub-Account Management

    Overview and core concepts

  2. 02

    B2C Subaccount Onboarding API

    Onboarding flow and key features

  3. 03

    X-Signature Authentication

    Request-signing guidance

  4. 04

    Setup Public Key

    Public-key registration

  5. 05

    Create Subaccount API

    Endpoint reference

  6. 06

    Regenerate API Key

    Credential rotation

FREQUENTLY ASKED QUESTIONS

Questions that come up during setup

Why am I getting a 401 Unauthorized?

Check whether the access token or Bearer token is valid and has not expired. Then review the authentication guidance for the request you are making.

Why was my Sub-Account code rejected?

The code may already exist. Check the existing account list and use a unique code for a new Sub-Account.

Why do I see a Public Key Not Found error?

Complete the public-key setup required for your account before creating a Sub-Account.

READY TO GET STARTED

Start onboarding your sub-accounts

Talk to our team about the account structure and onboarding flow that fit your business.

Contact SalesCreate Account