Payments built into the ERP, without becoming a Payment Institution
Embed collections into your own management suite without building a gateway or securing a banking license: that's the path Zucchetti took to turn its ERP into a full fintech platform.
REST APIs ready to power native collections in your software
Rolling out native payment flows without becoming a Payment Institution: that's what Zucchetti achieved with Daevon's API infrastructure, built for people who ship software.
Go to the API docsOne REST endpoint for every collection flow
From the ERP console, govern one-off charges, recurring payments, refunds and chargebacks through a single REST endpoint.
Invisible checkout
Iframe modules and server-side tokenization capture card data without ever leaving your software's own interface.
Real-time webhooks
The moment the banking node confirms the transaction, a server-to-server notification settles the invoice in the ERP automatically.
Cash flow managed without leaving the ERP
A genuinely complete accounting experience raised the perceived value of Zucchetti's suite among its own customers.
The technical layer connecting software and banking rails
The building blocks behind a full Embedded Finance offering, the ones Zucchetti adopted.
Calls to initialize, authorize and capture funds, callable from any server-side language.
Card PAN data is captured by secure frontend components, inside the ERP, without touching the software's own compliance scope.
Each transaction is routed to the most cost-effective acquirer to cut commission costs.
If the management server doesn't respond, the webhook system retries delivery automatically under a set retry policy.
The collected amount splits automatically between marketplace and seller, software house fees included.
A dedicated test environment lets the dev team validate every call before it ships to production.
"We were looking for a payment API interface that was robust, but above all modern and well-documented. Daevon proved to be the natural choice: an architecture designed for software creators, which allowed us to equip our ERPs with highly advanced fintech functions with an exceptional time-to-market."
The technical questions developers ask about APIs and Embedded Finance
Customers settle or collect with one click without leaving the invoice screen: that's Embedded Finance, and it means less drop-off and a smoother experience than opening home banking or an external portal.
Not if it's designed correctly. With Daevon's Iframe or hosted-fields modules, sensitive card data bypasses the ERP's servers and lands directly in Daevon's secure Vault: the software only receives a token, so PCI-DSS certification stays outside the development scope.
The banking circuit processes the payment, Daevon detects the successful outcome and calls the management server via webhook to report which invoice was settled: the ERP updates its status on its own, with no manual reconciliation.
No: the architecture is RESTful, so it communicates through standard HTTP requests and JSON payloads. You can integrate it from any backend language, Java, C#, Python, PHP or Node.js, and any commercial framework.
Building a SaaS platform or ERP software?
Add a native payment layer to your software through a single REST API interface.
Chiara
Daevon Support