Swish payments
Swish payments represent the primary checkout choice for Swedish consumers expecting immediate authentication via BankID. Cardflo orchestrates these transactions alongside broader European networks, allowing merchants to capture local volume while centralising reconciliation across all operating markets in a single platform.
- Category
- Methods
- Capabilities
- 6
- Available on
- All plans
E-commerce operations targeting the Swedish market face high abandonment rates if the dominant national mobile method is absent from the checkout. Consumers expect to trigger transactions using their mobile phone number and authenticate instantly via the national electronic identification system. Presenting unfamiliar flows forces buyers into slower verification routines that harm conversion metrics.
Cardflo integrates Swish payments into the core checkout flow, routing Swedish krona volumes to regulated acquirer partners that handle the underlying bank settlement. The platform standardises the transaction data alongside other European methods, giving finance teams a unified view of authorisation rates, settlement timelines and refund processing across the entire regional strategy.
Merchants can enable Swish via Cardflo to facilitate instant fund settlement and secure transactions for Swedish consumers, offering a faster boarding experience. This integration ensures robust fraud prevention and swift processing for all payment flows.
Swish payments overview
Penetrating the Swedish e-commerce sector requires specific alignment with local consumer habits, where mobile numbers act as primary identifiers for digital transactions. Merchants must present a checkout interface that triggers the national mobile payment application and links securely to the user's electronic identity application for immediate authorisation.
Cardflo orchestrates this flow, connecting digital storefronts to acquirer partners that manage the underlying bank clearing process in Swedish krona. The orchestration layer ensures these regional mobile flows operate in parallel with other European checkout choices.
While operators managing extensive consumer finance options might explore Klarna payments, or look to Trustly-style bank payments for broader Nordic coverage, this integration focuses purely on the domestic mobile number flow.
Operators gain access to Sweden instant bank payments without needing to manage separate API integrations or reconcile disparate data feeds across their Scandinavian expansion efforts.
How swish payments works
Customer initiates checkout flow
The shopper selects the Swedish mobile option at the merchant checkout and enters their registered mobile telephone number. Cardflo captures this request and passes the transaction details, including the SEK purchase amount and merchant identifier, to the relevant acquirer partner. This partner subsequently communicates with the national central infrastructure to trigger the payment request on the user's device.
BankID application authentication
A push notification alerts the consumer to open their domestic mobile payment application. The application automatically redirects the user to their installed BankID software, presenting the exact purchase amount and merchant name for verification. The shopper confirms the transaction using their biometric data or personal identification code, which authorises the immediate transfer of funds from their linked bank account.
Real-time webhook notification
Once the electronic identity network confirms the authentication, the domestic clearing system processes the account transfer. The acquiring partner immediately relays this success status back to Cardflo. The orchestration platform updates the transaction record and fires a real-time webhook to the merchant's e-commerce backend, permitting the immediate release of digital goods or physical inventory for dispatch to the buyer.
Why swish payments matters
Localised conversion rates
Swedish consumers overwhelmingly prefer their domestic mobile application for online purchases, avoiding manual data entry and complex authentication steps. Merchants offering this precise flow benefit from reduced friction at the final checkout stage. Cardflo ensures this method is routed efficiently, allowing operators to capture highly engaged local traffic that would otherwise abandon a standard checkout.
Unified regional reporting
Expanding into the Nordics often fragments financial data across multiple local gateways and regional acquirers. By orchestrating Swedish volume through a single platform, finance teams remove the need to manually consolidate disparate settlement reports. Cardflo standardises the transaction lifecycle, bringing domestic mobile transfers into the same analytical environment as broader European and global payment methods.
Regulatory notes for swish payments
Mobile BankID authentication requirements
Operating in the Swedish digital landscape must line up precisely with European payment security standards, specifically the multi-factor authentication protocols mandated by regional regulatory authorities.
Domestic mobile transactions naturally fulfil the criteria for Strong Customer Authentication by relying on the national electronic identity application, Mobile BankID, which links directly to the consumer's verified bank profile.
Cardflo ensures that merchants maintain compliance without building complex biometric capture flows themselves. By routing the transaction to acquirer partners integrated with the central identity infrastructure, the platform shifts the authentication burden away from the merchant.
The electronic identity network secures the user's consent and passes a cryptographic proof of authorisation back through the payment chain.
Currency handling and local entity requirements
Processing domestic Swedish transfers historically demanded that international merchants establish a local corporate entity and secure direct acquiring relationships within the region. Cross-border regulations now permit technical intermediaries to route these transactions to eligible European acquirer partners.
This structure allows foreign digital storefronts to process Swedish krona volumes transparently.
Merchants must ensure their checkout correctly displays pricing in the local currency and accurately presents the required terms before initiating the mobile notification.
Cardflo facilitates this compliance by standardising the transaction payload sent to the acquirer partner, ensuring all consumer-facing metadata and currency indicators meet the exacting technical specifications demanded by the Swedish financial infrastructure.
Swish payments use cases
Swedish mobile checkout
Swedish storefronts accepting SEK need a Swish flow that transfers the payable amount to the customer’s mobile banking app, where BankID confirms the purchase without manual payment details. Cardflo connects the checkout to supported acquirer partners, routes domestic transactions and returns payment status to the order system.
Swedish mobile subscription payments
Merchants taking Swish payments must associate the customer’s mobile number, payment reference and SEK amount with the correct basket while avoiding duplicate fulfilment after repeated callbacks. Cardflo orchestrates the payment request, validates status updates and supplies transaction references for reconciliation by finance and operations teams.
Swish payment confirmation
Swedish merchants with time-sensitive stock or collection slots need confirmed Swish status before reserving inventory, issuing a receipt or releasing an order. Cardflo manages API responses and webhook events from supported acquirer partners, helping commerce systems distinguish completed, declined, cancelled and timed-out payment attempts.
Swedish digital goods purchases
Retailers returning Swish purchases need refunds linked to the original payment reference and reflected correctly in SEK settlement records, particularly when orders are partially returned. Cardflo passes eligible refund instructions through supported acquirer partners and provides reporting data that finance teams can match against orders, payment events and settlement files.
Swish payments by the numbers
This represents the typical percentage of the Swedish population that frequently uses the app, according to various regional digital payment reports.
Industry standard for the technical processing of the payment once the user has authorised the transaction in their bank app.
The estimated proportion of Swish transactions initiated on mobile devices, reflecting its origin as a mobile-first payment utility.
Methodology: these figures are illustrative ranges drawn from published industry data and observed merchant cohorts, not guarantees. Actual results depend on your risk profile, card mix, geography and acquiring setup, and are confirmed only in your own pricing and approval terms.
Related terms
Talk to our team about a live rollout across our acquirer partners' rails.
What you get with Swish payments
- Native Swedish BankID authentication integration to capture immediate, secure consumer authorisations via the mobile application.
- Automated routing of Swedish krona transaction volumes to appropriate regulated acquirer partners to ensure high settlement reliability.
- Standardised mobile number entry flows that mirror local consumer expectations for frictionless checkout experiences.
- Unified reconciliation reporting that places domestic Swedish transactions alongside broader European digital wallet and card volumes.
- Programmatic refund management that returns funds directly to the consumer's linked bank account without manual intervention.
- Dynamic checkout presentation that surfaces the appropriate domestic payment options based on the shopper's geolocation and currency.
A short scoping call, then a written plan for your MIDs.
Questions about Swish payments
How do I accept Swish payments on my international e-commerce site?
International merchants can accept Swish payments by integrating an orchestration layer that connects to eligible regional acquirer partners. Cardflo provides this technical bridge, allowing operators to present the local mobile option at checkout without establishing a local Swedish corporate entity.
The platform captures the buyer's phone number, triggers the domestic BankID authentication flow, and routes the transaction data to the appropriate regulated partner. This single integration standardises the process alongside other European methods, enabling efficient Nordic expansion.
What happens if a Swedish customer closes the BankID app during checkout?
If a consumer closes the electronic identity application before confirming the transfer, the authentication session times out at the central infrastructure level. The relevant acquirer partner registers an incomplete authorisation and transmits this status back to Cardflo.
The orchestration platform subsequently updates the transaction state to failed and alerts the merchant's front end. This allows the digital storefront to prompt the shopper to retry the mobile notification or select an alternative regional checkout method to complete their purchase.
Can I process refunds back to the customer's mobile number?
Merchants manage refunds through the standard Cardflo API rather than interacting directly with the consumer's mobile identifier. When an operator initiates a return, the platform routes the request to the acquirer partner that processed the original settlement.
The underlying banking infrastructure matches the transaction reference and reverses the transfer, depositing the exact SEK amount back into the bank account originally linked to the shopper's mobile profile. The merchant dashboard tracks this entire lifecycle automatically.
Does integrating Swedish mobile payments require a dedicated SEK merchant account?
Integrating this domestic method requires the transaction to be initiated and authorised in Swedish krona. However, operators do not necessarily require a local bank account, as Cardflo connects merchants with acquirer partners capable of executing like-for-like settlements or applying foreign exchange conversions before payout.
The specific settlement currency depends on the commercial agreement with the chosen acquirer, while Cardflo handles the technical routing, displaying the correct SEK pricing and managing the mobile number input format.
Related guides.
See how Cardflo compares.
From the blog
A merchant acquirer is a licensed bank that holds your account, takes liability for transactions, and settles funds. The payment processor is the technology layer routing data between the checkout, card networks, and issuing banks. Every card payment requires both components to manage technical encryption and financial liability. They are often separate entities with distinct fee structures.
Read articleA merchant acquirer is a financial institution that processes card transactions and verifies funds. The payment gateway acts as the technological bridge, encrypting sensitive data between the website and the acquirer. Merchants need both components to ensure that electronic payments are accepted, authorised, and settled. Together, they create a seamless and secure payment experience for customers.
Read articleA merchant account is a specialised business account used to accept electronic payments like Apple Pay and Google Pay. It acts as a bridge between the business and the customer bank. Funds are held here for verification and compliance before being transferred to a main bank account. This process ensures that all transactions are secure and reduces the risk of fraud for the merchant and the customer.
Read articleReady to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.