Integrations
Choosing between the API, webhooks, Zapier and Open Banking
Last updated 14 September 2026
There are four ways to get data in and out of Xace. They overlap, and most integrations use two of them. This page is the decision guide.
The four routes
| Route | Direction | Best for | Needs code |
|---|---|---|---|
| Customer API | Read and write | Your own systems: reconciliation, payouts, dashboards | Yes |
| Webhooks | Xace to you | Reacting to events without polling | Yes, a small endpoint |
| Zapier | Both, via Zapier | Automations between SaaS tools, alerts, tasks | No |
| Open Banking via Salt Edge | Read, and payment initiation | Treasury, accounting and analytics platforms that already support Salt Edge | No |
By job
Reconciliation into your own ledger or warehouse. API. Page transactions per account, fetch daily CAMT.053 statements as the control. Add webhooks later to shorten the lag. See Syncing transactions.
Reconciliation into Xero or QuickBooks. Neither API nor Zapier: use the built-in integration from the Connections page. See Zapier, Slack and Xero without code.
Automated payouts from your platform. API, with idempotency keys and approval tracking. See Creating a payment.
Alerts to people. Slack integration for channels; Zapier for email, SMS or anything else.
Tasks in Jira or Trello when something happens. Zapier, or the direct Jira and Trello integrations.
A live cash position in a treasury tool. If the tool supports Salt Edge, Open Banking is the fastest route and needs no code. If it does not, the API's accounts and balance endpoints. See Building a live cash position.
Reacting the moment money arrives. Webhooks, TransactionReceived. See Subscribing to webhooks.
Combining them
A typical production integration:
- API for the nightly reconciliation and the payout service.
- Webhooks to mark payouts complete and to notice inbound settlements as they land.
- Slack for the approvals channel.
- Zapier for the odd internal automation nobody wants to write code for.
Controls are the same on every route
Whatever route a payment comes in by, approval policies, roles and permissions apply. A Zap or an Open Banking payment initiation cannot bypass a two-approver rule. That is deliberate; it means you can choose the route on convenience without weakening control.
For the customer-facing overview, see Read API introduction and webhooks.