Swish

Swish is a secure and user-friendly payment app in Sweden, allowing consumers to pay online, in-store, and transfer money to friends. For three consecutive years, Swish has been named Sweden's strongest brand and holds a 39% share of checkout, making it the preferred payment method for Swedish consumers. Learn more about Swish.

Payment method properties

MarketsSE
Processing currenciesSEK
Consumer currenciesSEK
Settlement currenciesSEK
Authentication methodsREDIRECT SCAN_CODE APP_INTENT
Minimum payment amount0.01 SEK
Maximum payment amount999,999,999,999.99 SEK
Payment instrumentPASSTHROUGH_WALLET
Recurring paymentsNo
Separate capturesNo
RefundFull - Partial - Multiple
Refund validity13 months
DisputesNo
Sandbox availabilitySwish sandbox

Make a Swish payment

Swish is available through follow our standardized REDIRECT, SCAN_CODE and APP_INTENT flows. Enabling you to offer a seamless desktop or in-store QR code to mobile handoff, as well as a smooth app-to-app experience.

To create a Swish payment, you'll need to provide the following data at minimum when calling our /v1/payment-charges API:

Data FieldDescription
paymentMethodSWISH
amount.valueThe amount to be paid in the smallest units of the currency used.
amount.currencySEK
consumer.nameFull name of the consumer.
consumer.countryThe country where the consumer is shopping.
paymentDescriptorDescription of the payment.
authenticationSettings: REDIRECT
settings.returnUrl
Add the URL where the consumer should be redirected after they complete the payment. Required for the REDIRECT flow.
authenticationSettings: SCAN_CODE
settings.scanBy
Specify the expiration time for the QR Code. Required for the SCAN_CODE flow.
authenticationSettings: APP_INTENT
settings.mobileIntentUri
Add the mobile URI where the consumer should be redirected after they complete the payment. Required for the APP_INTENT flow.

Request

POST /v1/payment-charges

{
  "paymentMethod": "SWISH",
  "paymentDescriptor": "Description of payment",
  "amount": {
    "value": 1000,
    "currency": "SEK"
  },
  "consumer": {
    "name": "John Smith",
    "country": "SE"
  },
  "authenticationSettings": [
    {
      "type": "REDIRECT",
      "settings": {
        "returnUrl": "https://www.webshop.com/order-results-page"
      }
    },
    {
      "type": "SCAN_CODE",
      "settings": {
        "scanBy": "2025-03-26T20:24:27Z"
      }
    },
    {
      "type": "APP_INTENT",
      "settings":{
      "mobileIntentUri": "webshop://paymentresponse?123"
      }
    } 
  ]
}

Response

You'll receive our standard payment charge response (see potential responses in the API Reference) with the available authentication methods.

{
  "id": "charge_X0O78tadFHrZCbGhkycPk",
  "status": "AUTHENTICATION_PENDING",
  
  // ...
  
  "authenticationMethods": [
    {
      "type": "REDIRECT",
      "details": {
        "requestUrl": "https://redirection-target.ppro.com",
        "requestMethod": "GET"
      }
    },
    {
      "type": "SCAN_CODE",
      "details": {
        "codePayload": "swish://open/paymentrequest?amount=1000&currency=SEK&from=QR",
        "codeImage": "https://qr.ppro.com/image.png?payload=aWQ9YWJjJmFtb3Vuk9VVNEJmZyb209UVI",
        "codeDocument": "cdn.ppro.com//linktocodedocument",
        "scanBy": "2023-03-26T20:24:27Z",
        "codeType": "QR"
      }
    },
    {
      "type": "APP_INTENT",
      "details": {
        "requestUrl": "swish://open/paymentrequest?amount=1000&currency=SEK"
      }
    }
  ]
}

Pick the desired authentication method

REDIRECT

  1. Redirect your consumer to the returned $.authenticationMethods[?(@.type == "REDIRECT")].details.requestUrl.
    For example, with the value of https://redirection-target.ppro.com/ using the returned $.authenticationMethods[?(@.type == "REDIRECT")].details.requestMethod HTTP method.
  2. The consumer will finalize the payment process on the redirected page.

SCAN_CODE

  1. Render the QR code using one of the techniques available.
  2. The consumer will scan the QR code to complete the payment.

APP_INTENT

  1. Use the intent system on Android or a similar mechanism on iOS to trigger the URI.
  2. The consumer will be taken to the native app to complete the payment.

Handling the Payment Result

REDIRECT

  1. Once the consumer has confirmed the payment, they are redirected to the returnUrl provided in the initial payment charge creation request.
  2. After the consumer is redirected back to your site, check the payment status by making a GET /v1/payment-charges/{paymentChargeId}. Use the Status that you received to display the payment outcome to the consumer.
  3. Webhooks are also sent to inform you of the payment outcome. If the shopper closes the browser and doesn't return to your website, you can rely on webhooks to receive the payment result.

SCAN_CODE

  1. Check the payment status by making a GET /v1/payment-charges/{paymentChargeId}. Use the Status that you received to display the payment outcome to the consumer.
  2. Webhooks are also sent to inform you of the payment outcome.

APP_INTENT

  1. Once the consumer has confirmed the payment, they are returned to your app using the mobileIntentUri provided in the initial payment charge creation request.
  2. After the consumer is redirected back to your app, check the payment status by making a GET /v1/payment-charges/{paymentChargeId}. Use the Status that you received to display the payment outcome to the consumer.
  3. Webhooks are also sent to inform you of the payment outcome.

Payment instrument

A PASSTHROUGH_WALLET instrument will be created for Swish, with no additional data provided.

Request

GET /v1/payment-instruments/{instrument-id}

Response

{
    "id": "instr_5ChenWBwW8xARvJ3GccAx",
    "type": "PASSTHROUGH_WALLET"
}