What your stack is worth per year.
Toggle the rails you actually use - acquiring, banking, cross-border, digital assets and payment verification - and the builder models the annual commercial value of moving them onto a Crosswire-coordinated stack. It uses the same server-side pricing engine as the rate calculator, so the numbers agree with the offer you would receive.
What it needs from you
- Your vertical and reporting currency.
- Monthly processing volume per rail.
- Your current rate (bps, percentage or per-transaction fee).
- Optional: prefunding balance and cost of capital.
- Optional: monthly verification or KYC check volume.
What you get back
- Indicative annual value, totalled across the rails you enabled.
- A per-rail breakdown showing where the value comes from.
- The indicative rate range and secured ceiling for each priced rail.
- An option to email the full business case as a PDF.
All figures are indicative and subject to KYC/KYB and the licensed partner's approval. You contract with the licensed partners who hold your funds and run the rails; Crosswire designs the stack, negotiates the commercials and coordinates onboarding. Crosswire is paid by the infrastructure partners, so the infrastructure price carries no Crosswire margin; advisory or implementation work is quoted separately and agreed in advance.
Build your case. Not a pitch deck.
Toggle the rails you actually use. Every number is derived directly from your inputs, no hidden multipliers.
Your IC++ markup in bps (350 = 3.50%).
- AcquiringCalling the pricing engine…€0 / yr
- Banking & payoutsNot included - needs your numbers-
- Payment verificationNot included - needs your numbers-
Cost of fragmentation
The rate is the small number. The structure is the large one.
Every figure below comes from you or from a default that is shown as a default, with its basis stated in one line. Nothing is invented, and every cost line opens to show its formula. The result is a range, not a single dramatic number.
The shape of your flow
Two numbers from your statements, then one count.
DefaultDefault 3 to 4: acquiring, banking and at least one payout or FX rail is the common shape once a business sells cross-border. Count every contract you hold.
DefaultDefault 120 as a neutral mid-market ticket. It only drives payment counts, so replace it if your ticket is very different.
Capital and timing
What sits still, and for how long.
DefaultDefault T+2 to T+3, the standard card settlement window outside same-day arrangements. Your contract states yours.
DefaultDefault 0% to 5%. Low-risk merchants often hold none; 5% to 10% is common where the provider prices risk. Enter 0 if you hold none.
DefaultDefault 180 days, the standard rolling-reserve release period.
DefaultDefault 0. Only counted when you enter a balance you actually park with a provider.
DefaultDefault 8% a year, deliberately conservative: below the blended cost of capital most mid-market businesses carry, so trapped cash is never over-priced here.
Crossing a currency
The line that hides inside the rate.
DefaultDefault 20% to 35%: the band we see when a business collects in one currency and settles or pays out in another. Your ledger knows the exact figure.
DefaultIf nobody has told you your spread, assume a wide band: 25 bps is negotiated wholesale pricing, 150 bps is the retail-style markup embedded in a bank or PSP rate. Both ends are shown so you can see what the uncertainty costs.
DefaultDefault 2,500. Money crossing a currency usually moves as a batched settlement or a supplier or seller payout, not as an individual card payment, so this is deliberately larger than your average ticket. It only drives how many cross-currency payments carry a correspondent fee.
DefaultDefault 6 to 25 per cross-currency payment: a single intermediary at the low end, two or three hops with lifting charges at the high end.
Per-payment leakage
Small numbers, large counts.
DefaultDefault 0.3% to 0.6% of payments, the band we see on card volume outside dispute-heavy verticals. Each card scheme publishes its own monitoring thresholds, which differ and change; check the scheme rules for the ratios that apply to you.
DefaultDefault 15 to 40: the scheme fee plus the internal time to gather evidence and respond. Excludes the disputed amount itself, which is not a fragmentation cost.
DefaultDefault 1.5% to 3% of payments failing and being retried or chased. Your gateway reports the real figure.
DefaultDefault 3 to 12: the retry or return fee plus the operational time to chase it. Excludes any lost sale, which we do not model.
Fragmentation proper
The costs that scale with the number of relationships.
DefaultDefault 6 to 10 hours per provider per month: statement pulls, matching, breaks and month-end close, once per relationship. Scales with your provider count.
DefaultDefault 45 to 65 an hour: finance-operations salary plus employer costs and overhead, not the bare salary rate.
DefaultDefault 150 to 400 per provider per month: platform, account or minimum-processing fees paid in parallel whether or not you use the rail. Your invoices show the exact number.
DefaultDefault 2 to 6 engineering days per provider per year: API version changes, certificate and credential rotation, webhook and reporting fixes. Excludes the original build.
Enter your monthly volume and the blended rate you pay and the model runs. Everything else can stay on its stated default.