Release Notes

The latest updates about our releases will be published on this page.

info

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.

04 Sep 2020

Version 1.13.3

28 Aug 2020

Version 1.13.2

21 Aug 2020

Version 1.13.1

17 July 2020

Version 1.13.0

10 July 2020

Version 1.12.1

  • Corrected the documentation by removing generatePaymentToken and paymentToken from Checkout.

07 July 2020

Version 1.12.0

  • 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.
  • Documented paid, failed and aborted across all resources.
  • Added additional information on payerReference, generateRecurrenceToken, paymentToken, generatePaymentToken, recurrenceToken and instrument for the paymentorder resource in Checkout.
  • Corrected and updated view- operations for all resources.
  • Updated Seamless View Events for all resources.
  • Described nonPaymentToken and externalNonPaymentToken in Card Payments.
  • Small corrections to Swish Payments documentation.
  • Clarified the updateOrder documentation.

04 June 2020

Version 1.11.1

29 May 2020

Version 1.11.0

22 May 2020

Version 1.10.1

14 May 2020

Version 1.10.0

07 May 2020

Version 1.9.2

Version 1.9.1

  • Corrected sequence diagrams in Swish Payments and Vipps Payments.
  • The description field is now more thoroughly described for all requests it’s present in.
  • The language field is now better described for all requests it’s present in.
  • All broken links should now be unbroken.

April 2020

Version 1.9.0

Version 1.8.3

Version 1.8.2

March 2020

Version 1.8.1

  • Documented allowed characters in orderItem.class.
  • Added receiptReference in Invoice Payments and Payment Order in capture and reversal.
  • Callback is now moved to Other features in all payments intruments.
  • Clean up of MobilePay.
  • Corrected the address of Leia Ahlström in Test Data.
  • Updated the documentation in Card Payments to recommend using shippingAddress.
  • Updated payeeReference to have an unique description for Payment Order and every Payment Instrument.

Version 1.8.0

Version 1.7.7

This change contains build updates for the page. :octocat:

Version 1.7.6

  • Several links has been corrected. The chance of 404 is now much lower.
  • Other small text changes and clarifications.

Version 1.7.5

  • New page! Technical reference into has been moved from the front page to technical information.
  • Front page got a slimmer look. :swimmer:
  • Abort reference is back in credit card reference.
  • Swish error code reference got a face lift, check it out here :candy:.

February 2020

Version 1.7.4

Version 1.7.3

  • Expanded information about the field restrictedToInstruments.
  • Added information about the field receiptReference.
  • Added information about direct integration in Credit card.
  • Added and fixed several missing headings in template files.
  • Expanded information about verify.
  • Created new page for Checkout Capture.
  • Mobile Pay Online was previously only refered to as Mobile Pay, this has been corrected.

Version 1.7.2

Version 1.7.1

All sections have been released. :trophy:

Version 1.7

  • 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.
  • Fixed JavaScript example in Checkin section.
  • Added info about mobile verification in Swish Other Features.
  • Added section about Authenticated Merchants in Checkout section.
  • Cleanup in Vipps Other Features.
  • paymentRestrictedToAgeLimit and paymentRestrictedToSocialSecurityNumber added to swish object in Swish Redirect. paymentAgeLimit , socialSecurityNumber added to the new payerInfo object in Swish Seamless View. Properties added in Swish.
  • Added section about migration key in Resources section.

January 2020

Version 1.6.3

  • restrictedToInstruments added back to Payment Order purchase requests.
  • Direct Debit section and mentions in various includes removed.
  • Various improvements and fixes.

Version 1.6.2

Version 1.6.1

Version 1.6

  • Credit Payments (née “Credit Account”) sections have been deleted from the Swedbank Pay Developer Portal.
  • The Swish Payments and Vipps Payments have received a few updates and are now ready for another round of review.
  • MobilePay Payments is now ready for review.
  • paymentAgeLimit is 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.

Version 1.5

Version 1.4

December 2019

Update in checkin module

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. The parameters language and shippingAddressRestrictedToCountryCodes have replaced the former consumerCountryCode.

The parameters msisdn and email have been made obsolete due to GDPR rules. This information cannot be sent in without an explicit consent from the consumer.

November 2019

Welcome, Swedbank Pay Developer Portal

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.

Support international phone numbers in Swish

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 consumer enters their phone number on the payment page.

Order Items

The input parameter quantity in OrderItems-node is now updated to decimal. You may send up to 4 decimals. See updated documentation here

October 2019

Payment Url Credit Card

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 same URL as that of the page where the JavaScript for the hosted payment view was added, in order to initiate the payment. Please note that the paymentUrl must be able to invoke the same JavaScript URL from the same Payment as the one 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 cart or similar that has the URL of the Payment stored. When the JavaScript is invoked after return of the consumer, the consumer will either be redirected to the completeUrl (event onPaymentCompleted) or if payment has failed, see an error-message and get the option to retry the payment.

August 2019

Order Items in payment orders

On Payment Orders, itemDescriptions and vatSummary has been replaced with the more versatile and powerful orderItems. While itemDescriptions will continue to work, it is recommended that all integrations switch over to orderItems as soon as possible. When orderItems is used, itemDescriptions must be removed from all requests as the two cannot be used simultaneously.

Payment Url

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 hosted view was hosted originally, such as the checkout page, shopping cart page, or similar. Basically, paymentUrl should be set to the same URL as that of the page where the JavaScript for the hosted payment view was added to in order to initiate the payment. Please note that the paymentUrl must be able to invoke the same JavaScript URL from the same Payment or Payment Order as the one 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 cart or similar that has the URL of the Payment or Payment Order stored. When the JavaScript is invoked after return of the consumer, the consumer will either be redirected to the completeUrl, or, if payment failed, see an error-message, and get the option to retry the payment.

If paymentUrl is not implemented, retry of payments will not be possible in either individual payment instruments such as Vipps 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.