Integration ecosystem
Connect your existing systems.
Banks, payment gateways, accounting, ERP, ecommerce, subscriptions and internal APIs. Any source that can export a statement, a report or JSON can reach the transaction model.
Three ways in
Choose the connection that fits the source.
Direct connector
Authenticate once and let data flow on a schedule. Connectors are planned and shown with their status.
Availability varies by source.
File import
Upload or drop statements and settlement reports: CSV, MT940, CAMT.053 and similar.
Batch, not real-time.
API and webhooks
Push transactions from your own systems and read results back, with signed webhooks for events.
You build the mapping.
Directory
Planned and supported integrations.
Everything below is currently planned. Status is shown per tile, and it will change as connectors ship.
- PlannedBank accountsStatements, credits, debits Connector
- PlannedStatement filesCSV, MT940, CAMT.053 File import
- PlannedAccount aggregationConsent-based account feeds Connector
- PlannedRazorpayPayments, refunds, settlements Connector
- PlannedStripeCharges, payouts, balance transactions Connector
- PlannedCashfreePayments, settlements Connector
- PlannedOther gatewaysSettlement report files File import
- PlannedAccounting platformsLedgers, invoices, journals Connector
- PlannedJournal exportReconciled entries back to books API
- PlannedERP systemsGL postings, vouchers, receivables Connector
- PlannedVoucher importScheduled file drops File import
- PlannedShopifyOrders, refunds, payouts Connector
- PlannedOther storefrontsOrder and refund feeds API
- PlannedSubscription billingPlans, invoices, renewals Connector
- PlannedREST APIIngest and query transactions API
- PlannedWebhooksSigned events on state change API
- PlannedSFTP dropBatch file ingestion File import
Integration ecosystem. Connect your existing systems through connectors, file import or the API. Names indicate planned integration targets; availability is shown per tile, and no partnership or endorsement is implied.
Connector anatomy
What a connection does.
- 1
Authenticate
Credentials are entered once, stored encrypted and scoped to this source.
- 2
Fetch
Pull new records on a schedule, or receive them by webhook.
- 3
Map
Apply the source mapping into the transaction model.
- 4
Validate
Check totals, currencies and required fields.
- 5
Sync
Hand records to matching, with lineage to the raw source.
Missing something?
Request an integration.
Tell us which system you need. Requests help decide which connectors come first.
Make every financial transaction explainable.
Connect your financial systems, reconcile transactions automatically, and build a reliable source of financial truth.