Version numbers: The version numbers used in headers on this page refers to the version of this very documentation, not to a version of any APIs described by it.
We spent some time building up steam after new years, but we have lots of treats lined up.
Are you looking to get started with recurring payments, but not really sure where to start? We have compiled everything you need in a use case, and walk you through it all.
Or are you maybe looking to upgrade to our newest Digital Payments version? See how easy it is in our migration guide.
errorType goes live any day now, so a preview in the developer portal
seems fitting. The aim is to give you clearer feedback when a token has become
inactive. Read more about it in the problems section.
We have also made improvements to the domain verification steps of our Apple Pay documentation.
The Resources are being split up. We have moved the test-data and release notes up a level for convenience. Development guidelines are moved to Modules & SDKs if you need them. The partners are now on our front page and Data Protection can be found in Checkout v2.
In addition to the usual handful of improvements and bug fixes, of course.
Until next time!
The last release of 2023 is finding its way down the chimney, and is mainly consisting of maintenance and small fixes.
There is however, one quite important update among the small ones. We have added a test data section for Network Tokenization, with both test cards and useful information. Head to the Network Tokenization feature section if you want to learn more about what it is.
From all of us, to all of you: Merry Christmas!
Today, we go live with Payment Order v3.1, which has some changes in the
request, the post-purchase operations and the
callback. We have also added a new resource model called
failedPostPurchaseAttempts. Go check it out!
There is a new section regarding Trustly in Digital Payments, with important information regarding overlay and Trustly Express.
If you are reading these notes, you have probably noticed some changes already! As the Payment Terminals section is growing bigger, we have moved most of the Digital Payments related content away from the front page. The release notes can now be found where you are reading this, and the resources at the bottom of the front page will follow suit shortly.
The biggest news is the arrival of the Swedbank Pay Playground, where you can experience our payment solutions both as a payer and – since we give you access to the toolbox – a merchant. Play around with amounts, different menu setups (full menu, selected instruments or a single instrument) and styling. It is also a great opportunity to see the upcoming accessibility compliant UI. Read more about accessibility changes here. With that in mind, we have also written a section regarding custom styling of your payment UI.
If you are looking for Cross Channel Payments and can’t find it, that is because we have renamed it Integrated Commerce.
The wheels are picking up traction going into the autumn. Our first release after getting back is mostly maintenance and small fixes, but an important new addition is a section on Network Tokenization, which is a fantastic way of processing cards. Get to know it, and put it to use!
We have also adjusted our search results somewhat. Now we only display results from the sections Digital Payments and Payment Terminals. We hope it gives you an easier time finding the right result in the correct section.
Big things are coming up around the bend. Stay tuned!
We had time for one more before we clock out for summer, so we added a PATCH example to our payout feature section. Go check it out if you are on your way to implementing it.
Have a great summer!
A small batch of changes which barely missed the last deadline. We’ve done a few correction and some major changes, most notably the renaming of Checkout v3 to Digital Payments and Pax Terminal to Payment Terminal. The changes are in name only, the structure stays the same.
We have also added information regarding the Eligibility Check, and the availability of invoice for Swedish merchants, where the payment instrument integrations have been removed. You have to go through an implementation using payment order to offer this in Sweden.
You spoke, we listened! We have worked a lot on making the portal easier to navigate. The main menu has been slimmed down, where we have removed the Introduction (but you can still read the main points under fundamental principles). If you are looking for the Resources and Modules & SDK sections, they have found a new home under Digital Payments.
Speaking of Digital Payments, we’ve cleaned that up as well, and hope it will make things easier for you. The payment request example now contains what you need to create a payment order. Adding more to it is up to you and the features section. The common implementations steps have been merged to avoid duplicate information, only sending you separate places when it’s time to display the ui.
A new terminal section has been added. Exciting things are coming, so we will make sure it grows and develops going forward.
Other highlights and important changes include:
- A new Payout section, currently supporting Trustly.
- An important field related to Network Tokenization has been added to the Paid models.
- A separate split settlement section, previously a part of settlement & reconciliation.
- Links to our partner pages.
- How to contact us before you get started.
- 3DS2 is now named Frictionless payments.
- Order items have been moved to optional features.
- Terms of Service has gotten its own optional feature.
Plus the usual handful of bug fixes and smaller changes.
The keen observer might spot some changes in our menu. The Checkout v2, Payment Menu and Payment Instruments have been moved to Old Implementations. You can still find everything you want and need, so no need to worry. A new .NET SDK section has also been added, in addition to the usual bugs and small fixes.
A lot of changes are happening these days. We’ve made the decision to focus the Digital Payments offering, so our Starter and Business implementations are no more. This means that we can do what we do best: giving you a payment experience packed with options. The Payments Only implementation is still here, and for those of you with a Strong Consumer Authentication who want access to our safely stored card data, Enterprise is still available too.
We promised you something big, and here it is. Click to Pay and Google Pay™ have been added to our arsenal of payment instruments. Click on your instrument of choice to see what is needed for you to activate in your integration. We have also added information on how to activate Apple Pay, which we recommend reading up on.
As you’ve probably already seen, our new sidebar is finally live too! We have given it a facelift and different levels which we hope make it easier for you to navigate. All the content is where it used to be. Check it out (and let us know what you think)! You might also wonder where the tables following our code examples have gone. We have made them expandable, and given them a facelift as well.
We have also added 3DS2 test data, along with smaller maintenance tasks and bug fixes.
Bigger things are coming up around the bend, so we are stopping by with some smaller fixes and a Digital Payments matrix giving you a better overview over which payment instruments v3 has to offer, and the countries they are available.
We’ll be back soon!
We kick off the new year with a new field in our payment order request. Your Digital Payments implementation of choice is now added in the request. Version 2 of the balance report and transaction list is our second newcomer this release. Head over to Settlement & Reconciliation to learn more.
Our last update in 2022 mainly consists of clean-ups and fixes, but the most
important changes are
msidn fields added (where they are relevant)
to Paid resource model
and Paid status model, plus a small rework of
Happy holidays, everyone! We look forward to seeing you in 2023!
Our penultimate release of the year has a few things up its sleeve. The most exciting being the new capabilities Integrated Commerce, Automated Fuel Dispenser Payments, SSN and Age restrictions. We’ve also added some new fields in the Paid and Cancelled models, a new Payer resource model. Please note the organization number added to the essential information for Checkout v3 set ups. Apart from that, there are no releases without typo corrections and bug fixes.
Another small one. We’ve added Digital Payments
paid responses for all
instruments in both status and
resource-models, finished up the headers which was missing,
added MobilePay to Request Delivery Information
and done away with some more bugs and typos.
We have been picking up steam since our summer break, hitting full throttle as September arrived. A smaller release this time around, but there are some important additions nonetheless. We have added a siteID field to Digital Payments implementations, re-worked nearly all headers across the portal to make navigation easier, added a section on deleting payment tokens, along with the usual batch of assorted bug fixes and typos.
A release filled with leftovers before we clock out for summer. Mostly small fixes in code examples and tables, but the most important additions are the new fields added in the paid resource model. Have a great summer!
Summer has finally arrived, and we have quite a treat waiting in our final release before the vacation pulse kicks in. Without further ado: We now proudly offer Apple Pay! It is available in all our Digital Payments implementations and integrations. There are a couple of other new additions as well:
- Our SDKs have been updated to support Digital Payments
- You can now request delivery information for selected instruments
- An eligibility check eligibility check for wallets has been added to instrument mode
- Fixed typos, minor bugs and code examples
- Added a new card error code and restructured the tables.
- Fleshed out the Unscheduled Purchase section.
- Fleshed out the Recur section.
- Moved the callback section to core features.
- Typos and minor bug fixes in code examples and tables.
- Typos and minor bug fixes in code examples and tables.
- Re-wrote Payer Aware Payment Menu
OnAbortedSeamless View event
- Elaborated user agent fields in requests.
- Added links to resource models in Digital Payments response tables
- Added descriptive card icons
- Added Payer Aware Payment Menu
- Added new screenshots for Digital Payments implementations
- Rewrote instrument mode section
- Reorganized features in the sidebar
- Fixed internal links
It’s been a minute, but the day is finally here. We can proudly present Checkout version 3.0! The same range of payment instruments, checkin options and features as always, but since different merchants have different needs, we’ve made it easier for you to get the checkout experience which fits you best. So, what’s new?
- Two Checkout implementations tailor-made for different needs and wishes: Enterprise or Payments Only. We’ve summed them up to help you find the right fit and get started.
- Each implementation starts off with a guide to set up your test account quickly.
- Want to see the new implementations in action? Head over to the demoshop.
- The Seamless View events have been re-worked to make the integration smoother for you.
- Renamed and gathered the Post-Purchase options on one page. The rest of the features are still where they used to be.
- We’ve given the front page a touch up, and given the new sections a slightly different look to distinguish them.
- Already up on Checkout version 2.0? No worries. All the documentation is still available in the sidebar and here.
- Updated Android SDK documentation
- Added info about consumerProfileRef expiration
- Added important information about WebView integrations for mobile card payments
- Updated iOS SDK documentation
- Added information about authorization timeouts (bottom of page)
- Added important info about MobilePay shoplogoUrl
- Fixed minor bugs and code examples
- Added payment link for Payment Menu v2
- Renamed Merchant Authenticated Consumer section (previously Delegated Strong Authenticated Consumer)
- Updated Unscheduled Merchant Initiated Transaction
- Fixed typos, minor bugs and code examples
- Added payment link option for Trustly
- Added information about invoice capture in Checkout v2 and Payment Menu
- Added MobilePay
shoplogoUrlin the Checkout v2 and Payment Menu v2 items section
- Added Delete Token section in Card’s technical reference
- Fixed minor typos and bugs
- Restructured Features sections for all implementations into core features, optional features and technical reference
- Renamed Checkout to Checkout v2
- Added TRA exemption section
- Fixed a handful of typos and bugs
- Updated Theme version to 1.9.9
- Updated Design Guide Version to 5.0.1
- Updated theme with visual fixes
- Search icon is now clickable
- Various bug fixes
- Various corrections and typo fixes
- Re-worded split settlement
- Clarified that callback is a fail-safe
- Updated tables and code examples with payerReference in various places, like card purchase
- Updated Mobile SDK configurations for both iOS and Android to include integration with custom backends
- Updated GitHub references for Mobile SDK
- Re-wrote Prices section
- Various bug fixes
- Various corrections and typo fixes
- Corrected information about 3D-Secure
- Added paragraphs about different consumer flows in Checkin
- Added link to gift card on the front page
- Added section for MobilePay Seamless View
- Split MobilePay Capture to a separate page
- Code examples for digital products added in Checkin
Launched new developer portal theme:
- New design
- New menu structure
- Reading time
- Added GDPR disclaimer.
- Added custom 404 page.
- Added section about Transaction On File
- Added Seamless View for Trustly.
- Added documentation about payment and transaction states. See Card Other Features for example.
- Added event override warning for Seamless View Events, see Card Seamless View Events for example.
- Added section regarding MOTO in Card Other Features.
- Deleted Merchant Identified Payer in Checkout.
- Renamed Merchant Authenticated Consumer to Delegated Strong Customer Authentication.
end-usernaming for most sections.
- Updated expiry date for test cards in test data.
- Updated callback documentation.
- Updated regex pattern for
- Added documentation on deprecated operations in Checkout.
instrumentdescription in Checkout.
shoplogoUrlin MobilePay Online Payments.
- Updated Test data in Resources.
- Documented problems in Trustly Payments.
- Added an alert for two-phase payments in Capture pages.
- Added description on
metadatafor all payment instruments.
- Updated files in Settlement & Reconciliation.
- Added information on token deletion in Card Payments and Invoice Payments.
- Updated the documentation on
paymentRestrictedToSocialSecurityNumberin Swish Payments.
- Added documentation on guest checkout in Checkout.
- Updated information about
- Added a list of accepted banks in Trustly Payments.
- Updated the
UpdateOrderdescription in Checkout.
- Removed documentation for Trustly Payments Seamless View.
- Updated Other Features in Trustly Payments.
- Updated Test Data for Vipps Payments.
- Added updated documentation on the
- Added documentation on Mobile SDK in Modules & SDKs section.
- Added tables for mapping API fields to settlement files in Settlement and Reconciliation.
- Corrected the documentation by removing
- Added information on 3-D Secure 2 for Checkout and Card Payments.
- Updated reconciliation files in Settlement & Reconciliation.
- Added test card for Forbrugsforeningen in Test data.
abortedacross all resources.
- Added additional information on
paymentorderresource in Checkout.
- Corrected and updated
view-operations for all resources.
- Updated Seamless View Events for all resources.
externalNonPaymentTokenin Card Payments.
- Small corrections to Swish Payments documentation.
- Clarified the
- Added additional information on the settlement files in Settlement & Reconciliation for all Payments.
- Corrected Card Payments Redirect and Card Payments Seamless View sequence diagrams.
- Added Abort in Swish Payments.
- Added a new Trustly Payments section.
- Added information about Storing URLs in the Technical Information section.
- Updated Swish Redirect requests.
orderReferenceinformation in Payment Order Callback in Checkout Other features.
- Added a new gift card section with descriptions of our Gift Cards API.
- Added a new section Co-badge Card Choice for Dankort in Card Payments.
- Corrected table in payments page.
- Corrected sequence diagrams in Swish Payments and Vipps Payments.
descriptionfield is now more thoroughly described for all requests it’s present in.
languagefield is now better described for all requests it’s present in.
- All broken links should now be unbroken.
- Added a new section SDKs and Modules in Resources.
- Corrected problem
typeURLs for Card Payments, Checkout and Swish Payments.
- Required checkmarks have a new, fresh look: check
- Flags now also sport a new look:
- Bug fixes to Mermaid diagram and alert styling, plus improvements to code block styling after the update to Swedbank Pay Design Guide 4.5.0.
- Added examples with screenshots of the effects of Delegated Strong Customer Authentication.
- Added a more thorough description on
completeUrlin all relevant payments.
orderItemsto be required in all requests and responses.
- Clean up of Swish Payments
pageStripDownin Vipps Redirect.
- Updated the main page to be more welcoming.
- Updated information on Delegated Strong Customer Authentication.
- Documented allowed characters in
receiptReferencein Invoice Payments and Payment Order in capture and reversal.
- Callback is now moved to Other features in all payments instruments.
- Clean up of MobilePay.
- Corrected the address of Leia Ahlström in Test Data.
- Updated the documentation in Card Payments
to recommend using
payeeReferenceto have an unique description for Payment Order and every Payment Instrument.
- Updated Invoice Payments Direct where
approvedLegalAddressshould now be use for all countries.
- Small text changes and clarifications.
- Restructured Invoice Payments and Card Payments.
This change contains build updates for the page. :octocat:
- Several links has been corrected. The chance of 404 is now much lower.
- Other small text changes and clarifications.
- New page! Technical reference into has been moved from the front page to technical information.
- Front page got a slimmer look.
- Abort reference is back in credit card reference.
- Swish error code reference got a face lift, check it out here .
- Expanded information about the field
- Added information about the field
- Added and fixed several missing headings in template files.
- Expanded information about
- Created new page for Checkout Capture.
- Mobile Pay Online was previously only referred to as Mobile Pay, this has been corrected.
- Removed several duplicate headers in features pages.
- Added unscheduled purchase information in card payments.
- We have added card logos when selecting card in payment menu. See updated screenshot of payment menu.
All sections have been released.
- README is updated with info about includes.
- Added several includes.
- Updated payeeReference description in Checkout and Invoice section.
- Using snake case consistently.
- Added section for unscheduled purchase in Card section.
- Added info about mobile verification in Swish Other Features.
- Added section about Authenticated Merchants in Checkout section.
- Cleanup in
swishobject in Swish Redirect.
socialSecurityNumberadded to the new
payerInfoobject in Swish Seamless View. Properties added in
- Added section about migration key in Resources section.
restrictedToInstrumentsadded back to Payment Order purchase requests.
Direct Debitsection and mentions in various includes removed.
- Various improvements and fixes.
homePhoneNumberadded to the
payerobject in Payment Order requests.
cardholderadded to Card Payments Purchase requests.
- Various improvements and fixes.
- The Swish Payments and Vipps Payments have received a few updates and are now ready for another round of review.
- MobilePay Online Payments is now ready for review.
paymentAgeLimitis now added in Swish Payments.
- The Terminology page is updated and 3-D Secure 2.0 (3DS2) , PSD2 and SCA explanations are added.
- Added descriptions for Payment States And Transaction States everywhere appropriate.
- Google Analytics has been added to Developer Portal.
- The review of Invoice Payments is complete and as such the section is now released and ready for use.
- The Card Payments section has received an overhaul, inching it closer to release.
- The Swish Payments and Vipps Payments sections are ready for review.
- Updated Swish Redirect and Swish Direct sections in preparations for review and the transition from PayEx Developer Portal.
- Added Data Protection section.
- Payment Orders now support
orderItemsin all operations.
- Added Terminology page.
- Clarified what the
awaitingActivitystate means for different payment instruments.
- Removed erroneous
noCVCin examples for One-Click Card Payments section.
- Added description for the
onBillingDetailsAvailableevent in the Checkin Front End section.
We have added support for specifying language as input in checkin module,
language. Supported languages are Norwegian, Swedish and English. Consumers
outside Sweden and Norway can now purchase in our Checkout service. You can
specify supported countries for shipment in a new input parameter,
shippingAddressRestrictedToCountryCodes, in our checkin module.
Updated API specification can be found here.
shippingAddressRestrictedToCountryCodes have replaced the former
PayEx’ Commerce offerings are being rebranded to Swedbank Pay and as a result of that rebranding, PayEx Checkout is now known as Swedbank Pay Checkout and its documentation can be found on here.
We have added support for sending in international phone numbers in the request. Check our Swish documentation here. This is supported in API, and when payer’s enter their phone number on the payment page.
The input parameter
quantity in the
orderItems field is now updated to decimal.
You may send up to 4 decimals. See updated documentation
We have added the URL field called
paymentUrl for Card
Seamless View (previously added for Vipps and Checkout), that will be used
when the user is returned from 3rd party. The URL should represent the page in
where the payment Seamless View was hosted originally, such as the checkout page,
shopping cart page, or similar. Basically,
paymentUrl should be set to the
was added, in order to initiate the payment. Please note that the
that initiated the payment originally, so it should include some sort of state
identifier in the URL. The state identifier is the ID of the order, shopping
invoked after return of the payer, they will either be redirected to
completeUrl (event onPaymentCompleted) or if payment has failed, see an
error-message and get the option to retry the payment.
On Payment Orders,
vatSummary has been replaced with the more
versatile and powerful
itemDescriptions will continue
to work, it is recommended that all integrations switch over to
as soon as possible. When
orderItems is used,
itemDescriptions must be
removed from all requests as the two cannot be used simultaneously.
For our Seamless Views (currently Vipps or in
Checkout), we have added a new URL field called
paymentUrl that will be used when user is returned from 3rd party. The URL
should represent the page of where the payment seamless view was hosted
originally, such as the checkout page, shopping cart page, or similar.
paymentUrl should be set to the same URL as that of the page where
payment. Please note that the
paymentUrl must be able to invoke the same
the payment originally, so it should include some sort of state identifier in
the URL. The state identifier is the ID of the order, shopping cart or similar
invoked after return of the payer, they will either be redirected to the
completeUrl, or, if payment failed, see an error message and get the option
to retry the payment.
paymentUrl is not implemented, retry of payments will not be possible in
either individual payment instruments such as
or in Checkout.
It makes it more tedious to retry payment as the whole process including the
creation of the payment or payment order needs to be performed again. With
paymentUrl in place, the retry process becomes much more convenient for both the
integration and the payer.