PulseConnect

Every source. One schema.

PulseConnect is the financial data connectivity and normalization layer. It ingests events, statements and postings from the systems you run, and maps each one to a single canonical event.

Talk to us PulseControl

01 · Overview

From source to control plane.

Four stages stand between a provider's payload and a record PulseControl can reconcile.

01SourcesProviders, banks, ERP, billing, internal services
02ConnectAuthenticate and keep the connection healthy
03NormalizeMap to the canonical event
04PulseControlReconcile, detect, control

The connector model shown here is a demonstration. Connectors are not claimed for any specific third-party product.

02 · Data ingestion

Four ways in.

Systems differ in how they expose data. PulseConnect accepts what each one offers, rather than forcing one method.

Ingestion methods
Method	Best for	Behavior
API pull	Providers with query APIs	Scheduled and on-demand reads, with cursor tracking so nothing is read twice.
Webhooks	Event-driven providers and internal services	Signed deliveries are accepted, acknowledged and queued before processing.
File import	Bank statements and settlement reports	CSV and fixed-width files are parsed against a per-source template.
Event stream	High-volume internal systems	Ordered events are consumed with replay from a stored position.

03 · Schema normalization

Different fields, one meaning.

A gateway's settlement_amount, a bank's credit and a ledger's amount_local describe the same money. Normalization is where they become comparable.

Illustrative mapping

Field mapping from Payment gateway to the canonical event
Source field	Canonical field	Example value
id	provider_ref	STL-20931
settlement_amount	amount	500000.00
settled_at	occurred_at	2026-10-05T18:30:00+05:30
status	state	PARTIAL
batch	batch_ref	STL-20931

Canonical eventillustrative

{
  "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"
}

04 · API connectivity and webhooks

Connect outward as well as inward.

Events leave PulseConnect as webhooks, so exceptions can open tickets or notify teams in the systems they already use.

Webhook deliveryillustrative

"POST" "https://your-service.example/pulse/events"

{
  "event": "exception.created",
  "id": "evt_01HZX48291",
  "created_at": "2026-10-06T09:14:09+05:30",
  "data": {
    "exception_id": "PX-48291",
    "type": "settlement_mismatch",
    "severity": "HIGH",
    "expected": "542580.00",
    "actual": "500000.00",
    "variance": "42580.00"
  }
}

Deliveries are signed so receivers can verify the sender.
Failed deliveries are retried with backoff and visible in source health.
Events carry stable identifiers, so receivers can process each one once.

Illustrative payload and endpoint. No live API is connected to this website.

05 · Data pipelines

Six steps between receipt and record.

Every event goes through the same pipeline, and each stage reports its own health.

01ReceiveAccept and acknowledge
02ValidateCheck shape and signature
03DeduplicateDrop repeats by reference
04NormalizeMap to canonical fields
05EnrichAttach counterparty and account
06PublishHand to PulseControl

06 · Source categories

Six categories, one model.

Select a category to see what it supplies.

PulseControlOne operational view

Exceptions
Alerts
Reports
API

01 · PaymentsDemo connector model

Supplies: Authorizations, captures, refunds, settlement batches and provider responses.
Connection methods: API · webhooks · settlement files
Typical source: Payment gateway · acquirer · payout provider

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.

Talk to us Explore the platform