Swish
Offer Swish in Sweden: set up your platform as a Swish technical supplier once, then connect each merchant's Swish number and test.
Ginger connects directly to Swish, the mobile payment method of Sweden, so your merchants can offer it with the payment method swish. Swish is available on Ginger since December 2025 (see the changelog).
Your platform is the merchant's technical supplier at Swish: it sends the payments on the merchant's behalf, with one certificate for all your merchants. Each merchant keeps its own Swish agreement with its bank, and Swish pays the money straight into the merchant's bank account. Swish payments are not in the payouts of Ginger.
This page shows how you set up your platform with Swish once, how you connect a merchant, and how you test.
How it works
The customer chooses Swish, and Ginger shows a Swish page with a QR code and an Open the Swish app button. On a computer, the customer scans the QR code with the Swish app; on a phone, the button opens the app. The customer approves the payment in the app, Swish informs Ginger, and the transaction gets its final status.
- Currency:
SEKonly. A Swish payment is always a sale: there's no pre-authorisation. - Expiry: a payment request the customer doesn't approve expires after 3 minutes.
Set up your platform
You do this once, with Swish and your Ginger contact.
Become a technical supplier at Swish
Sign an agreement with Swish as a technical supplier (teknisk leverantör), so merchants can choose your platform to
send their Swish payments. For access to Swish's test environment, write to Swish technical support at
tekniksupport@getswish.se, and say you sign up as a technical supplier. See the
Swish developer documentation.
Hand the certificate to Ginger
Order the production certificate for your platform in Swish's certificate management portal, portal.swish.nu, where you log in with BankID. Pass the certificate and its private key to your Ginger contact through a secure channel. Ginger configures them for your platform and switches Swish on: it's off unless you asked for it.
Swish answers each payment at your platform's API domain, so it must be reachable from the internet over HTTPS.
Connect a merchant
The merchant chooses your platform at Swish
The merchant arranges Swish for e-commerce (Swish Handel) with its bank, and chooses your platform as its technical supplier. The bank gives the merchant its Swish number, the payee alias.
Allow the payment method
Allow swish in the base permissions of the merchant and in the permissions of the project: / with POST. In the Admin portal, open the project, go to the Payment Method Contracts tab and switch on Swish.
Fill in the contract
Open Swish on the Payment Method Contracts tab and fill in the merchant's Swish number. A live project without a Swish number refuses Swish payments.
With the Boarding API, set it as swish_ in the swish contract of the project. See
Update a project contract in the API reference:
curl https://api.example.com/v1/admin/merchants/$MERCHANT_ID/projects/$PROJECT_ID/contracts/swish/ \
--user "$API_KEY:" \
--header "Content-Type: application/json" \
--request PUT \
--data '{ "swish_merchant_id": "<the merchant'\''s Swish number>" }'Test
A project in test mode (status active-testing) sends Swish payments to Swish's test environment, with the test
certificate and test Swish number of your platform. The Swish number in the contract isn't used, so you can test before
the merchant has its Swish number.
Create an order with a swish transaction and open its payment_:
curl https://api.example.com/v1/orders/ \
--user "$API_KEY:" \
--header "Content-Type: application/json" \
--data '{
"currency": "SEK",
"amount": 10000,
"transactions": [{ "payment_method": "swish" }]
}'See Create an order in the payment acceptance docs. Approve the payment with the Swish sandbox app and a test BankID, as described in Swish's sandbox guide.
Refunds
The merchant refunds a Swish payment with the standard refund request: see Refunds. Ginger sends the refund from the merchant's Swish number with the same certificate: nothing else to set up.
Next steps
- Payments: the payment methods and processors of your platform.
- Processor contracts: how contracts work.