Swish or Card Payment in Your Service?

If your service charges Swedish customers, the choice often comes down to Swish or card payment. Both work, but they’re good at different things. Swish owns the fast mobile flow in Sweden; cards provide reach and recurring payments. Which one you should offer – and in what order – is decided by how and where your customers actually pay.

Swish: the king of Swedish mobile flows

Swish’s strength is reach and simplicity on home turf. With over 8 million users in Sweden, in practice almost all of your Swedish customers already have it installed. That removes one of the biggest obstacles in a payment: the customer not having the right payment method.

Just as important is how short the flow is. A Swish payment takes a few seconds – the customer confirms in their app and is done, without fumbling with card numbers, expiration dates, and codes. On mobile, where every extra step loses customers, that’s decisive. The shorter the path between decision and completed purchase, the more customers make it all the way, and there Swish is hard to beat for fast one-time purchases.

Cards: subscriptions and reach

Card payment wins where Swish doesn’t reach. Two areas stand out.

The first is recurring payments. Cards are built for subscriptions and can be charged automatically period after period once the customer has approved it. If your service is built on a subscription, cards are more or less a requirement – Swish is made for the single purchase, not for being charged every month without renewed action.

The second is international reach. Cards work for customers around the world, while Swish is a Swedish payment method. If you have customers outside Sweden, or plan to, you need cards to be able to accept their payments at all.

Differences in implementation

Behind the checkout, the two also differ technically. A card integration is usually done through a payment provider and is fairly well-understood work.

Swish in a commerce solution requires a bit more. A Swish Handel agreement is signed through the bank, and the technical integration involves certificate management, among other things – digital certificates that verify the calls come from the right party. It’s more to set up initially than many expect. Once in place, the payment experience itself is simple for the customer, but the path there has more steps than a plain card integration.

That difference is worth knowing when you plan, so the work with agreements and certificates doesn’t come as a surprise late in the project.

The recommendation: usually both

Since Swish and cards solve different needs, it’s rarely a real either-or. Swish captures the fast one-time purchase in Sweden with minimal friction; cards cover subscriptions and customers outside the country. If you offer both, you meet more customers and more types of purchases, and you don’t force any customer to give up because their particular payment method is missing.

The question therefore is more often what order you introduce them in than which one you skip:

• One-off purchases, mostly Swedish mobile customers → start with Swish, add cards when reach or subscriptions become relevant.
• Subscriptions or international customers → start with cards, add Swish to lower the barrier for Swedish one-time purchases.

Start from your business. A café with an ordering app and a subscription service with customers in multiple countries have different answers, and both are right.

A common misunderstanding

A common false conclusion is that Swish is always the cheaper or simpler choice just because customers recognize it. The recognition is real and valuable, but it says nothing about what fits your particular business model. A subscription service that skips cards because “everyone has Swish” soon discovers that Swish doesn’t charge a payment automatically every month – and has to rebuild the payment flow from scratch.

Another misunderstanding is treating Swish as a quick add-on integration at the last minute. The agreement through the bank and the certificate management take time to put in place, and adding that work late in the project easily becomes a bottleneck before launch. Plan your payment methods early, so the agreement and technology have time to mature before the service goes live.

At Weapp we build payment flows with both Swish and cards and help you determine what your service should offer and in what order. Check out our services or get in touch and we’ll walk through your setup.