Skip to main content
SingaPay lets you create and manage multiple accounts under a single merchant credential. Each account has its own balance, transaction history, and payment instruments — cleanly separated, centrally managed.

​
What is a sub-account?

Businesses can create and manage multiple sub-accounts to achieve both financial isolation and centralized administration across different operations, merchants, stores, or partners. Each sub-account supports independent management of:
  • Account balance
  • Payment collection
  • Settlements and payouts
  • Transaction history
  • Billing records
  • User access permissions
  • API token permissions
Sub-accounts may represent:
  • Business divisions
  • Marketplace merchants
  • Business partners
  • Sellers
  • Suppliers
  • Branch offices
  • Drivers
  • Investors
Currently, Singapay supports two types of sub-accounts:
FeatureOwned Sub-AccountManaged Sub-Account
DefinitionRepresents a sub-account belonging to your own organization or internal business unit.Represents a third-party merchant account that you manage or collect payments on behalf of individual company or business company.
Typical ScenarioUsed when the platform operates multiple internal business units and needs separate balances.Used when the platform operates on behalf of merchants or enables merchants to receive payments directly.
Verification RequirementAvailable immediately after creation; no additional verification required.Can be created after the platform completes the merchant’s KYB verification.
VisibilityInvisible to end users unless explicitly invited.Invited merchants can access and manage their own funds while the platform retains administrative control.
Customer Information Displayed During PaymentThe Master Account information is displayed to customers.The corresponding Sub-Account information is displayed to customers.
Invoice RecipientInvoices are issued to the Master Account.Invoices are issued directly to the Sub-Account.
Webhook ConfigurationInherits the Master Account’s webhook configuration automatically.Can manage its own webhook settings independently through the Dashboard, while the Master Account may also configure them via API.

​
Account lifecycle

StateWhat it means
ActiveFully operational. Payment instruments can be created and payments are accepted.
InactivePaused. No new payments accepted, but existing records are retained.

​
Typical Use Cases

  • Marketplace Platforms
Create independent financial accounts for each seller while maintaining centralized platform management.
  • Franchise and Retail Chains
Allow each store or branch to independently manage revenue and transactions.
  • SaaS Platforms
Provide enterprise customers with dedicated account structures under a shared platform.
  • Channel Partners and Agents
Enable independent settlement and fund management for distributors and business partners.