# A retailer taking control of card costs

A US omnichannel retailer with stores and an online shop.

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

Cohorts: Fi + Vs

Video (36 s, illustrative): [MP4](/assets/use-cases/retailer-card-costs.mp4) · captions: [WebVTT](/assets/use-cases/retailer-card-costs.vtt) · step list for software: [flow.json](/assets/use-cases/retailer-card-costs.flow.json)

## The problem

Card fees arrive as one blended number. Nobody can say what each payment cost, which debit network carried it, or what choosing another network would save.

## Value anatomy

1. **Transaction**: Each card payment runs through the retailer's own rules: by card type, channel and amount.
2. **Rails**: Eligible debit goes to the debit network the retailer's rule chooses, compared against your current setup, payment by payment.
3. **Record**: Every payment shows its network, the rule that chose it and its fee lines, so finance can model the next change before making it.

## What it uses

- **Your rules**: Rules by card type, region, amount or time. Reviewable and reversible.
- **Debit network choice**: Send eligible debit to the network your rules pick.
- **Parallel run**: Compared against your current setup, payment by payment.
- **Cost modelling**: Preview a rule or payout change before you make it.
- **Fee lines**: Network, scheme and insimbi fees, itemized per transaction.

Request access: sales@insimbi.net

_insimbi is in early access with design partners._