Integrations
Your systems.
One operational view.
PulseControl connects to six categories of financial system. This page describes the connection model: what each category supplies, how it connects and how its data becomes comparable.
Categories describe the connection model. No specific third-party products are named or claimed as available.
Six categories feed one view.
Select a category to see what it supplies and how it connects.
- Exceptions
- Alerts
- Reports
- API
- Supplies
- Authorizations, captures, refunds, settlement batches and provider responses.
- Connection methods
- API · webhooks · settlement files
- Typical source
- Payment gateway · acquirer · payout provider
Each system connects the way it can.
| Category | Supplies | Connection methods | Typical source |
|---|---|---|---|
| Payments | Authorizations, captures, refunds, settlement batches and provider responses. | API · webhooks · settlement files | Payment gateway · acquirer · payout provider |
| Banking | Statements, credits, debits and remittance references. | Statement files · account feeds | Operating account · collection account |
| ERP | Receivables, payables and ledger postings. | API · scheduled export | General ledger · receivables module |
| Accounting | Journals, invoices and chart-of-accounts mappings. | API · file import | Journal export · invoice register |
| Data | Warehouse tables and flat files for history and enrichment. | File drop · scheduled query | Warehouse table · CSV drop |
| Internal APIs | Order, wallet and entitlement events from your own services. | REST · webhooks · event stream | Orders service · wallet service |
From credentials to monitored connection.
Every connection follows the same four stages, and each stage is visible in source health.
- 01AuthenticateCredentials stored as secrets and scoped to read what is needed
- 02MapSource fields mapped to the canonical event
- 03BackfillHistory loaded so matching starts with context
- 04MonitorDelay and failure surfaced to operators
One event, whatever the source.
Each source is mapped to a canonical event, so a settlement, a credit and a posting can be compared field for field.
{
"id": "evt_01HZX48291",
"source": "gateway_b",
"kind": "settlement",
"amount": "500000.00",
"currency": "INR",
"occurred_at": "2026-10-05T18:30:00+05:30",
"reference": "STL-20931",
"state": "PARTIAL",
"raw_ref": "raw/gateway_b/7731"
}- Amounts, currency and timestamps are standardized on ingestion.
- The original payload is retained by reference, so every field can be traced back.
- New sources are added by mapping, not by changing the reconciliation rules.
Illustrative schema. Field names may change before general availability.
Anything with an API can be connected.
If a system exposes events, statements or files, it can supply PulseControl. Internal services connect through the same API and webhook model used by everything else.
See PulseControl with your own systems in mind.
Tell us which systems your team reconciles today. We will show you how the platform would handle them.