Before creating payments on behalf of your merchants, the Platform may need to confirm that the necessary payment methods are activated for each sub-account.
Managed sub-account
Your merchants need to activate each payment method through their own dashboard. They can activate any payment method by going to Payment Method Settings and click “Activate” on respective payment method.
Owned sub-account
Owned sub-accounts use most payment methods that are active on the Platform account. There are some channels that may not be supported yet, or require the sub-account to complete verification. The next section covers channel support for Owned sub-accounts.
Supported payment methods for Owned sub-accounts
Symbol | Description |
|---|---|
✅ | Supported |
❌ | Not supported |
ℹ️ | Merchant verification required |
Payment Methods | Indonesia | Philippines | Thailand | Malaysia | Vietnam |
|---|---|---|---|---|---|
Cards | ❌ | ℹ️ | ℹ️ | ❌ | ❌ |
Virtual Accounts | ✅ | ✅ | |||
Virtual Accounts (ID BCA) | ❌ | ||||
Direct Debit | ✅ | ✅ | ✅ | ✅ | ✅ |
Ewallets | ✅ | ✅ | ✅ | ✅ | ✅ |
Ewallets (PH GCash) | ℹ️ | ||||
QR Codes | ✅ | ✅ | ✅ | ✅ | ✅ |
QR Code (ID Static) | ❌ | ||||
Retail Outlets | ✅ | ✅ | ✅ | ||
PayLater | ❌ | ❌ | ❌ | ❌ | ❌ |
Flow & Implementation
You or your merchants can use the Dashboard and our APIs to create payments. However Owned sub-accounts cannot create API keys and hence are unable to create their own API requests:
Platform | Managed Sub-accounts | Owned Sub-accounts | |
|---|---|---|---|
Create invoices via Dashboard | ✅ | ✅ | ✅ |
Create payments via API | ✅ | ✅ | ❌ |
With the Platform account API key, you can send Create payments requests via API on behalf of sub-accounts using a header parameter called for-user-id. The following flowcharts are some examples on what the process looks like.
Payment Links
Fixed Virtual Accounts
Merchant Name Displayed to Customers
When customers pay, they will see the name of your merchant in various touch points. Whose name gets displayed name depend on the sub-account type as well as the interface that the customer is on.
For Managed Sub-Accounts, all payment methods will display your merchant’s name, except for channels that allow for customization in the transaction request (Virtual Accounts, Retail Outlets).
Since Owned Sub-Accounts are not verified and only has a Xendit business name, the name displayed outside of Xendit interfaces will be the Platform’s registered business or legal name
Xendit Invoice: Sub-account business name
Payment channel application or web checkout: Platform business name or legal entity name
Cards authorization: Platform legal entity name
Bank Statements: Platform legal entity name
Receiving Payment Event Webhooks
To receive webhooks on events occurring on your merchant’s accounts, you may need to set relevant webhook URLs on the sub-account depending on its type. For example, to receive Payment Status webhook for your partner, you have to make sure that your partner’s account has already been set for Payment Status webhook URL.
Owned sub-accounts
Once the master account has set a webhook URL, all Owned sub-accounts will use the same webhook URL automatically. For example:
The Platform account has set an Payment Status webhook URL.
When a sub-account’s payment is paid by a customer, the webhook will be sent to the same webhook URL set on the Platform.
Managed accounts
There are two methods to set webhook URLs for Managed sub-accounts:
Your merchants can log in and set their own webhook URL by navigating to Webhook Settings
The Platform can request Set webhook URL via API, and provide the sub-account’s ID in the
for-user-idheader