> For the complete documentation index, see [llms.txt](https://pivot-payment.gitbook.io/pivot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pivot-payment.gitbook.io/pivot-docs/account-and-balance-management/transaction-capability.md). # Transaction capability {% hint style="info" %} Remember, you need to define your sub-account type as KYC or Non-KYC when registering your sub-account account {% endhint %} ## Transaction interface As a main account, you are allowed to manage your sub-account transaction, from transaction creation to refund request. | Type | Interface | | ------------------- | ---------------------------------------------------------------------------------------------------- | | Payment processing | API - using on-behalf information | | Send money / Payout | | ## Payment identity | Use Case example | KYC condition | Payment Identity and descriptor in transaction and payment page | | ---------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- | | Retailers which have multiple outlets |

KYC:

(A) Retailers Main Account

Non-KYC:

(B) All outlets as sub-account

| Show Retailers Main account name | | PG Reseller which host multiple different company / entity |

KYC:

(A) PG Reseller as Main Account

(B) Company 1

(C) Company 2

| Show respective company identity when each processing their payment | ## Derived Payment Identity

Derived payment identity and configuration

Non-KYC Sub-account inherits payment identity from the Main Account. It means the accountability and responsibility of any transaction (in and out) on the Non-KYC sub-account belongs to the Main Account (your account) ## Split and Route Payment One of the key capabilities of the Account and Balance management product is to accept payments, then automatically split and re-route the funds automatically from the Main Account / Sub-account account to the Main Account / other Sub-account account. Example Use Case: **Marketplace** Flows of payments from end-customers which need to be distributed to * The Marketplace, * 3PL partners, and * product provider/seller

Split and Route Payment — Marketplace case

**Tech Enabled Industry / SaaS Platform** Two examples, they are * A referral model, when your user refers new activated (or paid) user, then your user will get some credit * A restaurant with a food delivery service where the payment delivery fee needs to be distributed to the freelance courier — let's use this scenario for illustration

Split and Route Payment — Food Delivery case


--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://pivot-payment.gitbook.io/pivot-docs/account-and-balance-management/transaction-capability.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.