Welcome to Xendit’s latest documentation. For legacy content, access the previous documentation here or the previous API reference here.

Overview

Prev Next

xenPlatform is a payment solution for platform businesses that need to manage funds for multiple merchants. Think of it like a central hub for handling all your platform's payment needs.

xenPlatform enables your business to:

  • Create and manage individual sub-accounts for each merchant.

  • Accept payments on behalf of your merchants.

  • Split payments between multiple accounts.

  • Track all transactions in one place.

  • Pay out to your merchants’ bank accounts.

This simplifies complex payment flows for businesses like:

  • Marketplaces:  E-commerce platforms with multiple sellers.

  • SaaS Platforms:  Subscription services with various vendors.

  • Brick-and-mortar: Businesses operating multiple physical stores with unified payment systems.

  • Other platforms:  Any business model with multiple partners receiving funds.

xenPlatform Terminology

  • Master Account: Your Xendit account with xenPlatform activated, and can create sub-accounts. We also refer to multi-account businesses as Platforms.

  • Sub-Account: The Xendit account where transactions are processed for your merchants. Each account has a separate balance and transaction history. The entity represented by the sub-accounts can be your merchants, partners, sellers, vendors, branches, drivers, etc.

Account IDs for API Requests

An Account ID is the account identifier used for various requests (card charges, payouts, reports, etc.). It is how you can identify which sub-account you wish to perform the requests for. In our API references, there are synonyms to an Account ID which are: user-id , owner_id , business_id .

Use Cases

Using xenPlatform to manage payments for sub-accounts involves 4 simple steps:

  1. Creating a sub-account

  2. Managing their payments

  3. Monitoring their transactions

  4. Paying out

In each step, there are different options that you can choose based on the payments experience that you want to provide to your merchants. We have created several suggested recipes for common business models:

Business Models

Examples

Account Setup

Payment Routing

SaaS Platforms

TADA, Qoala

Owned sub-accounts to onboard merchants at-scale

  1. Accept payments on behalf of your merchants by using our hosted checkout solution for easy integration

  2. Create Split Fees to automate charging commissions per transaction

  3. Disburse funds to your merchants’ bank accounts

Point-of-Sale Platforms

ESB, Raptor POS

Managed sub-accounts to allow merchants to manage their own payments

  1. Accept payments on behalf of your Partners by building your own payment page with our range of payment options via API

  2. Create Split Fees to automate charging commissions per transaction

  3. Merchants can withdraw their own funds to their bank accounts

Payment Service Providers

Helixpay, Tazapay

Sub-account types are determined based on onboarding policies and license requirements

  1. Accept payments on behalf of your Partners by building your own payment page with our range of payment options via API

  2. Create Split Fees to automate charging commissions per transaction

  3. Disburse or allow merchants to withdraw their own funds

Conglomerates

XL, Ciputra Group

Managed sub-accounts to allow branches and subsidiaries to manage their own payments

  1. Each branch or subsidiary operates their own dashboard to accept payments from customers, monitor transactions and withdraw.

  2. Use Transfers to move balances from subsidiaries to the Platform account as needed.