Settled premium, on time, to the right entity

Sweeps to carriers, transfers to programs, fee splits to designees. Every payout starts from typed records of what came in, so the carrier statement and your books reconcile to the same number every time.

pay.yourbrand.com/revenueLive
May 2026
$815,281.00 total revenue
Brand payout
$84,231.00Settled
SettlementSame-day, every day
This month31 payouts, 0 delays
Carrier payout
$621,550.00Settled
Producer commissions
$58,962.00Settled
Taxes and fees
$50,538.00Settled
How money goes out

Disbursement is its own pipeline

Sure moves money between programs, fee designees, and carriers. The same primitives, the same audit trail, whether it's a daily ACH sweep or a one-off fee transfer. Treasury sees a single chain instead of a vendor portal per gateway.

Sub-merchant transfers

Settle program balances on a schedule that matches the contract. Every payout maps to the charges that funded it, so program operators can answer 'why is this number what it is' without opening a ticket.

Fee splits, separately

When a fee should land somewhere other than the main payout, Sure routes it. Producer fees, MGA splits, whitelabel rev-share, all on the same transfer chain with the same audit row.

Carrier ACH sweeps

Daily or per-cadence transfers to each carrier on the bank rail. Premium, refunds, and adjustments aggregated in one batch. The carrier sees a single number that matches the policies underneath.

Event-driven status

Gateway events update payout status the moment they land. Treasury watches transfers move from processing to settled in real time. Bank holidays and partial settlements stop being mysteries.

Idempotent reconciliation

Every transfer is keyed to a stable reference. A replayed webhook, a redelivered event, a manual investigation pull, none of them double-write a payout. The chain stays clean.

Reconcilable from day one

Each transfer is a fold of typed records, not a free-text bank memo. Pull any payout and walk back to the charges that produced it, the program that owns it, and the rules that priced it.

Three surfaces

Treasury, ops, engineering

Treasury sees the cash position. Ops watches the webhooks. Engineering owns the integration.

For treasury

Cash position view

Pending transfers, in-flight payouts, settled balances. Filter by carrier, program, rail. Reconcile bank statements against the same payout records ops watches.

  • Aging by payout status
  • Program-level rollup
  • Bank-statement match by transfer ID
For ops

Event investigator

When a transfer hangs in processing, agents can replay the event, force a status pull, or open the gateway dashboard. Every action writes a row, never a Slack message.

  • Replay status events
  • Drill into payout history
  • Surface missing references with a typed error
For engineers

Gateway client SDK

One transfer surface, multiple rails underneath. Add a new gateway without touching reconciliation code.

  • Stripe, Checkout.com, Column
  • Composable webhook handlers
  • Typed records and statuses
Guardrails

Disbursement only where the records say so

Transfers fold typed records of what came in. Operators cannot send money where no record points.

01
Transfers fold real records

Every payout is a sum of receivables tied to a program or designee. Stray collections cannot leak into the wrong payout.

02
Carrier-pinned routing

Each carrier resolves to its own gateway and rail. The wrong rail returns no client, never a misrouted transfer.

03
Webhook signatures verified

Every gateway event is signature-verified before it changes a payout status. Mismatched signatures are dropped.

04
Idempotent on every reference

Replays are safe. The chain is keyed to gateway references, not to clock time, so investigations don't accidentally double-write.

05
Status is mapped, not free-text

Gateway statuses translate to a small enumerated set. Unknown values log a warning for human review.

06
Settlement entity per program

Each program holds its own gateway entity. Settlement balances do not commingle across carriers or programs by accident.

The specs

What it supports

Rails supported
ACH · bank rail · card · pay with escrow
Gateways
Stripe · Checkout.com · Column
PCI scope
PCI-DSS Level 1
0

Disbursement gateways live behind one transfer surface today

<0hours

Carrier ACH sweeps settle on the bank rail. Same-day, every day

0%

Of webhook events arrive signed and verified, or get dropped before they post

Chubb's insurance offering, through Sure's technology platform, further reinforces our commitment to innovative, digital solutions and providing consumers with peace of mind.
James Walloga
EVP Accident & Health, Chubb North America
Chubb

See insurance payments done the right way

Walk through Sure's payments system with our team. We'll cover everything from premium collection to reconciliation, and the parts of insurance money movement that power programs.