# An insurer paying claims on the fastest sensible rail

A US property insurer paying claims to policyholders and repair shops.

**Illustrative scenario.** A fictional type of business, not a customer. No results are claimed.

Cohorts: Fi + Sc

## The problem

Claimants wait for checks. Some want money in minutes, others are fine with a bank transfer. Each claim payment needs a clear trail for the regulator.

## Value anatomy

1. **Transaction**: An approved claim creates a payout instruction with the payee and amount.
2. **Rails**: A payout rule picks the rail: instant bank payment where supported, ACH otherwise, a stablecoin for payees who ask.
3. **Record**: Each payout links to the claim, the rail chosen and why. Returns land in the exception queue.

## What it uses

- **Bank payouts**: ACH, same-day ACH and instant bank rails, per account.
- **Stablecoin payouts**: Pay sellers, suppliers or partners in stablecoins, by rule.
- **Payout cutoffs**: See the next settlement window before it closes.
- **Exception queue**: Disputes, refunds and failed payouts in one list, each with its rule.
- **Reconciliation**: Each settlement row matched to the transactions behind it.

Request access: sales@insimbi.net

_insimbi is in early access with design partners._