← Stories
Banking
Banks, neobanks, and wallet apps — ship payment initiation with open banking routing, and offer invoicing & payment links to your merchant programmes.
Merchants and platforms expect account-to-account checkout and simple “pay this invoice” links — without you rebuilding a different aggregator per market. StixBNK provides open banking routing for PIS (Pay by bank) and the same rails for invoicing & payment links, so your merchant portfolio collects through one API and hosted checkout layer.
Use case 1
PIS with multi-provider routing
Pain
Hard-coding a single open banking aggregator creates coverage gaps, outage risk, and painful migrations when you expand markets.
What StixBNK delivers
Market-aware routing across the providers you enable — one initiation contract, bank SCA, webhooks, and reconciliation for every merchant collection.
Flow
- Merchant or API creates a collection (checkout or invoice pay link).
- StixBNK routes to the best available provider for the market.
- Payer authenticates at their bank (SCA).
- Status webhooks update your ledger and the merchant dashboard.
Impact
One APIHide aggregator complexity from product teams
ResilienceFail over by market instead of a single vendor bet
Use case 2
Merchant invoicing & payment links
Give SMEs and corporate clients on your platform a way to issue invoices and collect via hosted pay links — settled by the same open banking routing as API checkout. PDF, email, and payer receipt included.
Typical feature set
- Invoice draft → issue → pay link
- Hosted checkout with bank picker
- Shared transaction feed for gateway + invoices
Impact
StickinessBilling tools keep merchants on your rails
A2ALower CNP risk vs. card pay links
