Retail, marketplaces, and payment service providers — lower cost, stronger authentication, measurable conversion lift.
Card networks still dominate online checkout. They stack intermediaries, push scheme fees into the 1.5–3% range, stretch settlement to T+1–T+3, and leave merchants exposed to card-not-present fraud and chargebacks. StixBNK routes compliant account-to-account (A2A) flows over PSD2-style open banking so shoppers can Pay by bank with SCA at their institution — while you receive webhooks, references, and reconciliation data in one API layer.
Use case 1
Instant A2A payment at checkout
Context
Traditional e-commerce stacks depend on Visa, Mastercard, and acquirers. That implies multiple hops, blended pricing, and fraud models optimised for cards — not for high-trust bank rails.
Several intermediaries between shopper and settlement
CNP fraud, chargebacks, and dispute handling overhead
Merchant pain
Compressed margins after payment fees
Slow settlement (T+1 to T+3)
High card-not-present fraud exposure
What StixBNK enables
Direct payment initiation from the customer’s bank account via regulated open banking APIs. The payer authorises in their bank app or web session (SCA); funds move account-to-account with a clear payment reference tied to your order.
Technical flow
Checkout presents Pay by bank alongside existing methods.
StixBNK creates a payment initiation request with amount, creditor, and reference.
Customer is redirected to their bank (OAuth-style handoff + SCA).
Strong authentication — biometrics, device signing, or OTP as required by the ASPSP.
Bank confirms authorisation; status propagates to StixBNK.
Webhook notifies your OMS / ERP so you only fulfil on authorised or settled states.
Settlement can be near real-time or same-day depending on rail and geography.
Illustrative API surface
Paths below are representative; your live integration uses the endpoints and keys from your merchant or reseller dashboard.
< 10sTarget confirmation window where instant rails apply
Use case 2
Intelligent checkout with bank-sourced data
Friction
Long address and IBAN forms
Industry-average cart abandonment around 70%
Manual errors and support tickets
Approach
With consent, connect the shopper’s bank once via StixBNK to retrieve verified identity fragments, IBAN, and structured address data — then autofill checkout and immediately initiate payment.
Flow
User selects Checkout with bank.
Secure connection through StixBNK (AIS / identity scopes as licensed).
Normalised payer details returned to your front end.
Fields pre-filled; user confirms in seconds.
Payment initiation completes the journey in one session.
+15–25%Conversion lift in A/B tests (category-dependent)
Use case 3
Recurring payments & mandates
Why cards churn
Expired, lost, or reissued cards
Involuntary churn on subscriptions
Retry logic and dunning cost
Bank mandates — SEPA Direct Debit, variable recurring open-banking consents, or hybrid models — tie billing to an account that changes less often than a card. StixBNK stores consent artefacts, surfaces mandate status in your dashboard, and fires webhooks on success, failure, or mandate revocation.
Flow
Customer authorises a mandate in a hosted or embedded flow.
StixBNK persists consent metadata and compliance timestamps.
Scheduled or event-triggered collections execute per your rules.
↓ ~30%Involuntary churn vs. card-only (programme-dependent)
↑ LTVLonger subscriber lifetimes when mandates stick
API paths and KPI ranges are illustrative benchmarks from composite programmes — not guarantees. Regulatory coverage, bank participation, and your commercial terms determine live behaviour.
