Documented REST contract
The same interface the platform uses internally, published and versioned.
Technology
API First architecture
It integrates with the ecosystem the chain already uses, including where SAP or TOTVS are already running.
The challenge
A chain with a corporate structure already has ERP, BI, and CRM selected, often with years of investment and process built on top. When the operating system demands to be the center of everything, the conversation stops being about the operation and becomes about replacing what already works.
What this costs
That stalls the decision. The technology director weighs the risk of replacing a piece that talks to everything else; finance adds up the cost of what would be discarded; and the project that would have fixed the operation halts because it turned into a stack-replacement project. File-export integration, when it exists, fixes the report and not the process.
The platform was built on its own API — the interface consumes the same contracts that the client consumes. This means integrating isn't about using a side door: it's about using the same path the product uses. EPOC comes in as a piece of a structure that already exists, instead of asking for it to be rebuilt.
8
certified acquirers
Cielo, Rede, Fiserv, Caixa, Sicredi, Stone, PagSeguro, Getnet
37
active integrations and certifications
Sum of every ecosystem group
Layer 03
Ecosystem and data
Together with the Data Lake, this is where the platform stops being a closed system and becomes part of the customer's corporate structure.
What this delivers
Data input through the API
Sales, products, and payments come into the platform through the API — it doesn't only push data out.
Webhook events
The client's system is notified when something happens, instead of having to keep polling.
Certification environment
Integration tested before it touches live operations.
Integration with corporate ERP
SAP and TOTVS are among the ecosystems already supported.
Output to BI
Data available to the tool the client already uses, including Qlik.
Payment methods
8 certified acquirers and 1 sub-acquirer.
Conversation with
- SAP
- TOTVS
- Qlik
- Certified acquirers
- CRM
- Delivery
Where it applies
Frequently asked questions
Do I need to replace my corporate ERP to use EPOC?
No. The architecture exists for exactly the opposite reason: the platform integrates with what the chain already uses. SAP and TOTVS are among the ecosystems already supported.
Is the API documentation public?
The API's technical documentation is provided during the integration and certification process. A public developer portal is in preparation.
How does the certification environment work?
The integration is built and tested against a separate environment, with test data, before anything touches the production operation.
Is the operation's data mine?
Yes. The Data Lake exists so that the chain's operational data is available for analysis, cross-referencing, and export by the customer, rather than locked into the platform.
Talk to a specialist
Your operation has grown. Is your technology ready?
How many locations, what stack is already running, what needs to be integrated, and what the rollout would look like.
