Concepts and Glossary
Getnet Split Payments uses a consistent set of concepts and terms throughout this documentation, gathered here as a reference to understand the overall model or resolve a specific terminology question.
Model
| Concept | Definition |
|---|---|
| Platform (anchor) | The main establishment that contracts the solution with Getnet and either receives amounts on behalf of third parties or participates in the payment flow of its own sales: a marketplace, a services platform, software with embedded payments, a franchise network, or a group of associated establishments. |
| EC (Merchant Establishment) | The platform's registration within Getnet, identified by merchant_id in API calls. |
| Seller | The business linked to the platform that receives a share of the transaction amount. In API responses and fields, this record is identified as Subseller (for example, subseller_id, /update-subseller). Throughout the rest of this documentation, the term used is always seller. |
| Split rule | The configuration that determines how a transaction is distributed between the platform and the sellers. |
| Receivable schedule | The set of future amounts due to a seller, along with the corresponding payment calendar. |
| Release | The action by which the platform enables payment of an amount to the seller. It's optional. |
| Adjustment | A manual entry that corrects a seller's balance. |
| Settlement | The actual payment of the amount corresponding to a seller into their bank account. |
| D+N notation | A count of business days from the transaction date (D): D+1 is one business day later, D+2 is two business days later, and so on. |
| Receba-Já | Split's anticipation solution, for amounts with a future receipt date. |
| Statement | The transactional and financial detail used for reconciliation. |
| Payment plan | The way the sale amount is paid to the seller: the normal installment flow, or an anticipation via Receba-Já. |
| Settlement reference number | A unique identifier generated after the balance settlement, which groups all the entries credited in the same payment. |
Terminology Equivalents
This documentation uses a single term for each concept. The table below gathers the equivalents for terminology that may appear in other materials or in the API itself.
| Term used in this documentation | Common equivalents |
|---|---|
| Platform (anchor) | Marketplace, anchor, main establishment |
| EC (Merchant Establishment) | merchant_id |
| Seller | Recipient, store, vendor, Subseller |
| Receivable schedule | Schedule, receivables schedule |
| Release | Disbursement, payout |
| Adjustment | Ajuste (the term used in this documentation's pt-BR version) |
| Settlement | Liquidação (the term used in this documentation's pt-BR version) |
| Statement | Extrato (the term used in this documentation's pt-BR version) |
| Payment plan | payment_plan_name |
| Settlement reference number | reference_number |
| Balance | Saldo (the term used in this documentation's pt-BR version) |
Whenever a term used on another page of this documentation or a field name returned by the API isn't clear, come back to this page to check its definition or corresponding equivalent.
Next Steps
- Introduction: revisit the overview of Split and its components.
- Onboarding and Configuration: start registering your platform and your sellers.
On this page
Concepts and Glossary