Rootline Glossary
3
3D secure
An authentication protocol for online card payments that adds an extra verification step, reducing fraud.
A
Account
A unique financial entity within Rootline linked to a platform or client merchant. Used to send and receive funds. (rootline.com)
Account activation
The process by which a user completes onboarding (e.g. via hosted forms). Once onboarding finishes, an account.created webhook confirms the account is ready. (docs.rootline.com)
API key
A unique token used to authenticate API requests to Rootline. Functions as a secure credential for server-to-server communication.
API user
A user entity in Rootline with API access permissions. Linked to API keys for request authentication.
B
Buy-rate
The rate at which a service is bought. For instance, the fee a platform pays to Rootline for payment services. The difference between the buy-rate and the sell-rate is the margin on a pricing component.
C
Capture
The operation that confirms and secures payment funds after authorization. Related to partial or full refund/cancel capability. (docs.rootline.com)
Checkout
The ready-to-use Checkout pages Rootline provides; triggered after initiating a payment and redirecting via checkout_url. (docs.rootline.com)
Client merchant
Also known as sub-merchant or platform user. Operates under a Partner Merchant and utilizes Rootline via that relationship. (docs.rootline.com, rootline.com)
D
Dynamic 3D secure
A configurable 3D Secure implementation that triggers or skips authentication only when transactions meet specific criteria (e.g. risk thresholds).
Dynamic funds release
A flexible funds release configuration in the Payments API that determines when funds are made available to an account.
F
Fee ID
A unique identifier for a specific fee applied to a transaction in Rootline.
Fund release
The process of making funds available to an account; triggered by schedule (e.g. T+2), via release_funds_at in split payments or based on funds received by Rootline (passthrough mechanism). (docs.rootline.com)
I
In-person payments
Transactions processed using a physical payment device, also known as point-of-sale (POS), rather than online.
Interchange fees
Fees set by and paid to the card-issuing bank for each card transaction.
Invoice
A Rootline provided document detailing charges, taxes, and payment instructions.
M
Markup
The additional percentage and/or fixed fee added to base costs (e.g., interchange or scheme fees), typically applicable to card payments.
P
Partner merchant
The primary partner entity to Rootline, usually the Platform. Manages onboarding, payment routing and invoicing of client merchants. (docs.rootline.com, rootline.com)
Payment
A transaction object initiated via POST /payments, reflecting an overall or split-payment. (docs.rootline.com)
Payment ID
Unique identifier for each payment (root or split). Enables operations like refund, cancel, or fee update. (docs.rootline.com)
Payment method
A method (e.g. credit card, iDEAL) through which a payment is accepted and processed via Checkout or the Payment API.
Payout
Process of transferring a positive balance from a Rootline Account to an external bank account. (docs.rootline.com, rootline.com)
Platform
A business that uses Rootline to process payments on behalf of multiple sellers or service providers, though it is possible for the platform to sell their own products and services through Rootline as well.
Platform fees
Fees typically charged by the Platform, paid by Client merchants.
Processing account
An account that is designated to be the 'processor', or in other words the merchant of record. This is the case if the merchant representing the account is directly interacting with buying customers: these (client) merchants are clearly visible in the Checkout flow as the Merchant that the customer is buying from. Disputes and questions are typically the responsibility of the client merchant, rather than the platform or marketplace.
R
Reconciliation
The process of matching transactions three-way: 1) the amount received on the bank account, 2) the settlement report provided by Rootline, and 3) the platform's internal records for these transactions.
Refund
The action to return funds (full or partial) to a customer, via API or Dashboard. Processed asynchronously with events like refund.scheduled. (docs.rootline.com)
Reserve
Funds held by Rootline as collateral against potential chargebacks, refunds, fines, or adjustments. (rootline.com)
Reserve level
A set threshold for how much reserve a merchant must maintain, per terms of service. (rootline.com)
S
Scheme (owner)
The provider or overseer of a given payment method (e.g. Visa, Mastercard). (rootline.com)
Scheme fees
Charges imposed by card schemes for processing card payments.
Sell-rate
The rate or fee at which a service is sold. This could be the fee at which the platform sells payment services to their client merchants.
Settlement report
Mutation overview, usually generated for each payout; details gross amount, fees deducted, net amount for any mutation booked on the relevant Account(s) in the relevant time period. Essential in the reconciliation process for partner- and client merchants. (docs.rootline.com)
Split payment
Functionality allowing payments to be routed to one or multiple accounts. Supports multi-layer splits (e.g. platform → seller → employee). Gives each sub-payment its own payment_id. (docs.rootline.com)
Statement descriptor
The text that appears on the customer's bank statement for a transaction. Configurable per payment.
W
Webhook
Notifications sent to inform another system about asynchronous events such as account creation, payment status, refund/cancel scheduling and failures.
Webhook event
The specific notification payload sent to your webhook endpoint, containing details of the event (e.g., payment.succeeded).