bLink Sync Cost Calculator

Estimate the cost incurred to keep a customer's bank accounts in sync over SIX bLink — the API-call and registration cost we pay as Service User, not a price charged to end customers.

Sync frequency
Accounts & expected transactions

Transactions expected per account over the initial load window (used only for the one-time backfill).

months

Drives the initial balance-history backfill: one call per day per account over this window.

Balances have no list API and no pagination — one call per day per account. This is the single biggest cost driver.

Advanced assumptions
Ongoing cost / month –
One-time cost –
First-year cost –

Recurring — per month

Total per month

Initial load — one-time

Total one-time

Estimate only. These figures are the cost incurred — what you pay as Service User for API calls and registration — not a price charged to end customers. All amounts in CHF, excl. VAT. Based on the SIX bLink price list Annex 4 (AIS per-call prices & customer-registration fees) and the documented call-count assumptions below. SIX platform participation and onboarding fees are not included — they are fixed and independent of the number of users.

How we calculate

Recurring calls (per sync run)

  • 1 call for the account list (once per run)
  • 1 call per account for balances
  • 1 call per account for new transactions
    (assumes one call fetches all new TXs)

4× per day = 1 end-of-day + 3 intraday. Month = 31 days / 4 weeks.

Initial load (one-time)

  • 1 call for the account list
  • 1 balance call per day per account over the load window (no pagination)
  • ⌈TX ÷ page size⌉ transaction calls per account
  • the bank's one-time customer registration fee

Pricing source

  • Per-call price = bank's AIS rate (Annex 4 §8.3)
  • Registration = Annex 4 §8.2
  • Banks not in the price list charge CHF 0

SIX retains 20% of these prices from the provider; the Service User still pays the full list price shown here.