Sempre incluído
Core
The baseline every tenant runs on
O que resolve
A gateway is not useful until money can move, be attributed to a merchant, and be seen by everyone who needs to act on it. Core is the part of the platform that has to exist before any optional module makes sense.
Como funciona
Merchants and their contracts
Each tenant onboards its own merchants with tariffs, commissions, assigned methods and per-merchant overrides. The merchant record is the anchor everything else hangs off.
Transactions as one model
Payments, payouts, exchanges, refunds and chargebacks are all transactions with a shared status model, a public token, and a single collapsed status mapping that merchants see.
Wallets and balances
Multi-currency wallets per merchant, with balance history and reserve visibility so a manager can always answer where an amount came from and what is being held.
Providers, methods and routing
Providers are attached as modules, MIDs are registered against them, and each currency gets its own enabled method set. Route resolution can be previewed for a given merchant and method before any traffic reaches it.
Hosted checkout and the Processing API
A branded payment page on your pay host, and one signed API for merchants to create and read transactions. Provider quirks are normalised into canonical payment instructions before they reach anyone integrating.
Invoices and customers
Merchants raise invoices, send them through branded mail in the recipient's language, and let payers settle on a public page. A tenant-scoped customer directory stores payer details encrypted, with blind-index lookup so search never needs plaintext.
Refunds, chargebacks and disputes
The full post-payment path is in the baseline: refunds, chargeback handling, and a structured dispute workflow with document upload and download on shared evidence storage.
Currencies, rates and exchanges
Currency pairs with rate sources and rate locks, merchant-to-merchant exchanges with live quotes, and rounding rules enforced server-side so exports and screens always agree.
Access, security and audit
RBAC down to individual panel actions, tenant-scoped two-factor authentication and password resets, session controls, and a recorded trail of administrative activity.
A vantagem
Nothing to assemble
You are not integrating a ledger library, a status machine and a permission system into a coherent product — they already agree with each other.
One status vocabulary
Provider-specific states are collapsed before they reach a merchant, so your support team and your merchants' support teams speak the same language.
Auditable by construction
Balance movements carry their history rather than being recomputed, which is what makes disputes and reconciliation tractable later.
A gateway on day one
Core is not a trial tier. A tenant running only Core can onboard merchants, take payments, pay out, invoice, exchange currency and resolve disputes — the optional modules add reach, not the ability to trade.
Disponibilidade
Core is present in every billing plan and cannot be switched off — it is the contract the platform needs in order to operate at all.