Because of changes we’re making to our Swish payments integration, as of August 15, 2024 Stripe will be temporarily pausing the ability of some accounts to accept Swish payments. From August 15th, you can check whether your account has been impacted by looking at the payment method settings in your Dashboard: Swish will no longer be listed as Active if you are affected.

FAQs

When do these changes take effect?

Starting on August 15, 2024, affected accounts will temporarily no longer be able to complete transactions with Swish.

What is the impact?

You will no longer be able to complete transactions with Swish. You should remove Swish from your website temporarily until we confirm that we have reenabled access to Swish.

You can still continue to accept payments via other payment methods such as MobilePay, PayPal and Klarna.

When will Swish be reenabled for impacted accounts?

We are working as quickly as possible to renew access to Swish, but do not have a specific date to communicate yet. We will update this page and communicate with you when Swish is again available.

What changes do I need to make to my integration?

We have automatically hidden Swish for affected Stripe accounts that use Stripe Checkout, the Payment Element, and the Mobile Payment Element.

However, if your integration does not use dynamic_payment_methods (i.e., you manually list payment methods for your integration), and it meets one of the following criteria, you will need to manually remove Swish:

• Your integration uses Stripe Checkout, and Swish is the only payment method you offer: Remove “swish” from the payment_method_types specified at Checkout session creation to remove Swish as an option in Stripe Checkout.
• Your integration uses the Payment Element or Mobile Payment Element, and Swish is the only payment method you offer: Remove “swish” from the payment_method_types specified at PaymentIntent creation.
• You use a custom API integration: Remove “swish” from the payment_method_types specified at PaymentIntent creation (or from the sources types you create, if using the Sources API) and remove Swish from available options in your checkout.

Now that Swish has been switched off, any PaymentIntent confirmation that specifies payment_method_type as swish or any Source creation that specifies type as swish will fail with an HTTP 400 response.