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

Markets (consumer)SE
Processing currenciesSEK
Consumer currenciesSEK
Authentication methodsREDIRECT SCAN_CODE APP_INTENT
Authentication timeout4 minutes
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
Settlement riskYes

Make a Swish payment

Swish payments follow our standardized REDIRECT, SCAN_CODE and APP_INTENT payment 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. We recommend including all relevant settings for any authentication methods you support.

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

Field

Description

paymentMethod

SWISH

paymentDescriptor

Description of the payment. It is visible to the consumer in their Swish app when approving the payment.

amount.value

The amount to be paid in the smallest units of the currency used.

amount.currency

SEK

consumer.country

The country of residence of the consumer.

authenticationSettings: REDIRECT settings.returnUrl

Specify the URL to which the consumer should be redirected after completing the payment. This is required for the REDIRECT payment flow.

authenticationSettings: SCAN_CODE settings.scanBy

Specify the QR code’s expiration time.

authenticationSettings: APP_INTENT settings.mobileIntentUri

Specify the URI to which 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": {
    "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 with the available authentication methods:

{
  "id": "charge_qPoB2h51KyW3CcOiYdbUv",
  "paymentMethod": "SWISH",
  "paymentMedium": "ECOMMERCE",
  "scheduleType": "UNSCHEDULED",
  "instrumentId": "instr_l0cbLJx0mniRjCknrPL0b",
  "currency": "SEK",
  "country": "SE",
  "paymentDescriptor": "Description of payment",
  "status": "AUTHENTICATION_PENDING",
  "consumer": {
    "country": "SE"
  },
  "authenticationMethods": [
    {
      "details": {
        "requestUrl": "https://redirection-target.ppro.com",
        "requestMethod": "GET"
      },
      "type": "REDIRECT"
    },
    {
      "details": {
        "mobileIntentUri": "swish://paymentrequest?token=AAAAAAAAAAAAABYJmXQEEojHxoSjfRCF"
      },
      "type": "APP_INTENT"
    },
    {
      "details": {
        "codeType": "QR",
        "codeImage": "https://qr.ppro.com/payment/charge_Y3JVzvEaJpvG53xd2R2Zt/qr.png",
        "codePayload": "DAAAAAAAAAAAAABYJmXQEEojHxoSjfRCF"
      },
      "type": "SCAN_CODE"
    }
  ],
  "authorizations": [
    {
      "id": "authz_1KBdVLWcqMHwqqJT0ZDwV",
      "amount": 1000,
      "status": "AUTHENTICATION_PENDING",
      "createdAt": "2025-06-21T11:42:00.940Z",
      "updatedAt": "2025-06-21T11:42:00.940Z"
    }
  ],
  "captures": [],
  "refunds": [],
  "discards": [],
  "voids": [],
  "createdAt": "2025-06-21T11:42:00.438Z",
  "updatedAt": "2025-06-21T11:42:00.940Z",
  "_links": {
    "authorizations": {
      "href": "/v1/payment-charges/charge_qPoB2h51KyW3CcOiYdbUv/authorizations"
    },
    "captures": {
      "href": "/v1/payment-charges/charge_qPoB2h51KyW3CcOiYdbUv/captures"
    },
    "refunds": {
      "href": "/v1/payment-charges/charge_qPoB2h51KyW3CcOiYdbUv/refunds"
    },
    "discards": {
      "href": "/v1/payment-charges/charge_qPoB2h51KyW3CcOiYdbUv/discards"
    },
    "voids": {
      "href": "/v1/payment-charges/charge_qPoB2h51KyW3CcOiYdbUv/voids"
    }
  }
}

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 be presented with the reference number and instructions to complete the payment.

SCAN_CODE

  1. Render the code using one of the techniques available.
  2. The consumer will scan the 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. After the consumer completes the payment, they are redirected to the returnUrl specified in the payment charge creation request.
  2. Upon redirect back to your site, retrieve the latest payment status by performing a GET /v1/payment-charges/{paymentChargeId}. Use the returned status field to determine and display the final payment outcome to the consumer.
  3. Additionally, webhooks are triggered to notify you of the payment result. This ensures you receive the outcome even if the consumer closes their browser or fails to return to your website.

SCAN_CODE

  1. You'll be notified of the payment outcome via Webhook.
  2. You can check the payment status at any time by making a GET /v1/payment-charges/{paymentChargeId}.
  3. Use the Status that you received to display the payment outcome to the consumer.

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_l0cbLJx0mniRjCknrPL0b",
    "type": "PASSTHROUGH_WALLET"
}

Sandbox testing

Contact your account manager for test credentials.