Swish is a real-time bank transfer (a2a) used in Sweden. Sweden's ubiquitous mobile-first real-time payment app, jointly owned by the Swedish banks. Used by the overwhelming majority of Swedish adults; effectively universal. This page covers how the flow works, where consumers use it, and which merchants should accept it.
Swish is a mobile P2P and P2M app jointly built by the major Swedish banks on top of the RIX-INST real-time settlement system.
At checkout the merchant's PSP triggers a Swish request to the shopper's phone number. The shopper opens the Swish app, reviews the merchant and amount, and authorises with BankID.
Funds move bank-to-bank in real time; the merchant's PSP receives confirmation within seconds.
Swish is also the dominant P2P method in Sweden and is used widely for events, market stalls, charities and small merchants without card acquiring.
Used by the overwhelming majority of Swedish adults; effectively universal.
The operational half of every method profile — settlement, refunds, disputes, PSP coverage and licensing — is reserved for Payment Methods List founding partners. It's the part vendor sites won't publish and the part that actually decides whether Swish works for your stack.
How fast Swish funds land after the payer confirms, behaviour outside scheme hours, whether the rail settles gross or net, and the realistic T+n to sweep to USD/EUR — plus the PSPs where the advertised timeline actually holds in Sweden.
Book a founding-partner call →How Swish refunds are executed end-to-end when the rail has no scheme-level reversal — payer-initiated pulls, credit transfers, or PSP-fronted refunds — plus partial-refund support, time limits, and the API surface each PSP exposes.
Book a founding-partner call →Whether Swish has any dispute construct at all, which recall/return/indemnity vectors actually exist on the rail, how consumer-protection rules in Sweden route claims back to merchants, and observed loss rates versus cards.
Book a founding-partner call →Which acquirers and aggregators run direct rail connections to Swish vs. reselling a partner, coverage depth and reliability, effective pricing bands, and who to pick when Sweden volume is your primary use case.
Book a founding-partner call →Requirements to accept Swish — local entity vs. cross-border MoR, licensing regime governing the rail in Sweden, KYC obligations at onboarding and per-transaction, and FX/reporting rules for foreign merchants.
Book a founding-partner call →Swish is a real-time bank transfer (a2a) used in Sweden, in the Europe region. Sweden's ubiquitous mobile-first real-time payment app, jointly owned by the Swedish banks. The profile on this page documents the checkout flow step by step, the use cases it fits, the consumer base that can pay with it, and the merchant types that should carry it. Last reviewed July 31, 2026 by Ale Aznar.
Swish is recorded against Sweden in the Europe region, which is the market where its consumer reach is meaningful for merchants. Cross-border acceptance depends on the acquirer or merchant-of-record you use rather than on the rail itself. The Sweden country hub lists every other alternative and local method tracked for that market alongside Swish.
Pricing for Swish is not a single published number: it moves with monthly volume, vertical, entity type and whether you connect through a direct acquirer or an aggregator. Effective pricing bands per provider, plus the fixed-fee and FX components that sit alongside the headline rate, are part of the founding-partner dataset rather than this public Sweden profile.
Access to Swish runs either through an acquirer with a direct rail connection or through an aggregator reselling a partner's connection, and the two differ in reliability and reporting. The list of providers processing Swish in Sweden today, whether each is direct or resold, and where onboarding is currently restricted sits in the founding-partner PSP coverage matrix.
Yes. That is one of the documented use cases for Swish in Sweden: Any Swedish e-commerce, in-app or in-person checkout. Vertical eligibility is ultimately set by the provider you onboard with, not by the rail, so regulated categories such as gambling, crypto and adult content are commonly excluded even where the real-time bank transfer (a2a) itself supports the flow. Confirm the restriction list with your acquirer.
Swish is a real-time bank transfer (a2a), so the payer-side confirmation and the merchant-side payout are separate events with different timing. Settlement windows, cut-off behaviour outside scheme hours, the payout currency, and the realistic timeline to sweep funds out of Sweden are documented in the operational section of this profile, available to Payment Methods List founding partners.