Swedbank Pay Payments
This section of the Developer Portal is under review. While it can be used to integrate with Swedbank Pay’s APIs, please be aware that changes in text and examples may occur.
Payments is our off-the-rack assortment of payment instruments. You can pick and choose among them to tailor the instrument package best suited for your business.
Is Card the only payment instrument you need? Go for Card only. Do you want Card and Invoice? Implement Card and Invoice. Want them all? Have them all. Each payment instrument is set up with a separate contract and integration.
With a couple of exceptions, our payment instruments are available on three platforms. Choose between our easy-to-use PCI compliant platforms Redirect and Seamless View – or use Swedbank Pay Direct API to integrate directly. Our payment instruments and their platform availability are listed in the table below.
|Payment instrument||Seamless View||Redirect||Region|
To start integrating Swedbank Pay Payments, you need the following:
- An HTTPS enabled web server.
- An agreement which includes Swedbank Pay Payments.
- Credentials (Merchant Access Token) from Swedbank Pay retrieved from Swedbank Pay Admin.
Here are our three platform options at a glance. You can read more about the integration process by visiting the sections for each payment instrument.
With Seamless Views you can initiate the payment process
directly in an
iframe on your site. If you prefer that the consumer isn’t
redirected away from you, this option enables you to embed our payment page
seamlessly into your shopping experience.
The Redirect platform redirects the consumers to a Swedbank Pay hosted payment page. The consumer will be redirected back to your page when the payment is completed.
Direct is the option where you integrate directly using our Direct API. This is an integration with the most flexibility and opportunities. If you want to offer Card Payments and choose this option, you have to be PCI-DSS compliant.
All Payments APIs in the Swedbank Pay API Platform share a common foundation with a similar payment process for all payment instruments, reducing complexity and enabling a more straightforward integration.
There are two main payment types, two-phase and one-phase payments. The two seem very similar from a consumer’s point of view, but there are key differences you should know about.
A two-phase payment is performed in two steps – an
reserves the consumer’s funds, and a
capture of the funds at a later time,
usually when the goods are shipped.
This is the most common payment type, and it is used by Card Payments, Vipps Payments, MobilePay payments, Invoice Payments and Credit Account Payments. A capture of an invoice will not capture any funds, but trigger the invoice distribution and send it to the consumer.
There are two types of one-phase payments –
sale is used by payment instruments such as Direct Debit and Swish.
These payments will have a
sale transaction instead of the
capture. The funds will be captured from the consumer straight away.
autoCapture is only available for Card Payments. The mechanics work the same
way as a two-phase payment, with two separate transactions – one for the
authorization and one for the
As the name implies, the capture transaction is performed automatically when the
authorization is successful. Because of this,
autoCapture should only be used
when dealing with digital products, since they are shipped instantly.
As the funds are captured instantly,
cancel is not available for either of the
reversal can be performed the same way as with
The payment is the container object that holds all transactions created during the payment process. When Swedbank Pay receives the payment request body (in JSON format), a payment is created and you will be given a unique payment ID in return. The response also includes (in a true RESTful way) the URIs and operations for further actions, given the state of the payment.
After creating a payment, you can:
- Authorize funds. An authorization transaction reserves the funds. It is
aborta payment before the end user has completed the payment process. And either:
Capture funds. Before delivering the merchandise you need to create a capture transaction to ensure that the money is charged from the consumer credit card or properly billed by invoice. One-phase payments will combine these two in a
autoCapturetransaction as described in the section above.
- Cancel the authorized amount. Funds that are authorized but not yet captured, can be released back to the consumer. This is done by creating a cancel transaction. This is not available for one-phase payments.
- Reverse captured funds. In some cases you may need to make a reversal of captured funds. This is achieved by creating a reversal transaction.
All actions after creating the payment can be done by using our APIs, or from
our admin tool.
abort is only available when using APIs.
Please visit our demoshop to see our Payment Menu and Redirect implementation in action.