Certified acquirers
Multiple certified acquirers, so the chain can switch by rate without reintegrating.
Technology · Trust
What's certified works together — without reopening a project for every connection.
In a large operation, every new connection — acquirer, ERP, tax issuer — can turn into a project and a point of failure. And what isn't certified is a risk: it stops working with any random update, and responsibility ends up floating between vendors.
An uncertified integration breaks silently and shifts the blame from one side to the other. On the tax side, an error isn't an inconvenience — it's a fine. And depending on a fragile connection at high volume multiplies the risk by location.
Layer 03
It's the data and ecosystem layer looking outward: what the platform produces goes out through certified integration to corporate systems and payment methods, under a known contract.
Multiple certified acquirers, so the chain can switch by rate without reintegrating.
SAP, TOTVS, and Qlik among the corporate systems that operate with the platform.
Tax document issuance follows each regime's certification, per CNPJ.
Delivery, digital menu, loyalty, and pay-at-table within the certified ecosystem.
Every certified connection has a documented contract — it's not an improvised workaround.
Certified means it has an owner: it doesn't fail silently or go unaccountable.
The integrations page shows what the platform talks to and how (the API). This one covers what's certified — the certified list, the tax side, and the responsibility behind each connection.
São 8: Cielo, Rede, Fiserv, Caixa, Sicredi, Stone, PagSeguro, Getnet, além do subadquirente FrogPay. A lista é a mesma exibida na página de pagamentos.
Issuance follows the certification required by tax regime, per CNPJ. The details of tax scope by operation are covered in the implementation assessment.
Talk to a specialist
How many locations, what stack is already running, what needs to be integrated, and what the rollout would look like.