Release Notes

SmartPay is continually improved and further developed with the aim to provide new features, improvements and bugfixes in a timely manner.

Currently, we aim to release a new version every 6-8 weeks.

Every release is tested for backward compatibility so that you do not need to change your integration, unless you want to use the newly released features.

ApplePay:
ApplePay is now a supported payment option in SmartPay solution.

Fail-Safe enhancement
Introduction of a the new optional field "partnerReference" in the chekout APIs for CIT & MIT as well as the Get Payment Status API response.
This field can be populated by the Merchant, to include their internal transaction identifier in the checkout request; this would enable SmartPay in case of duplicate identical requests/retries, to block any potential double booking.

Additional case of handling 3DS for the API-only integrations
This is covering the Frictioneless case on 3DS v2 for API-Only integrations, where the response of Create Tokenized Payment API would be including a creq (instead of PaReq).

Ancillary Services
SmartPay solution is now offering standalone APIs for:

• Address Validation
• Compliance Checks
• Risk Checks

Hosted Payment Page:
Success and failure pages are now optional, so as a Merchant you can redirect your end-consumer to your own pages in both scenarios.

The SmartPay default page is now displaying the "transactionReference" field in case of payments done through 'Pre-payment' or 'Pay upon invoice'. For more information please refer to this page.

The same field "transactionReference" is now returned in the response of "Get Payment Status" API, when the payment is processed through 'Pre-payment' or 'Pay upon invoice'. (Please refer to Response sample #3)

Security improvements and bugfixes
This release contains further internal improvements, optimizations and security improvements.

Network Token
SmartPay solution offers now the provisioning of Network Tokens for MC and Visa.
For more information please refer to this section.

Security improvements and bugfixes
This release contains further internal improvements, optimizations and security improvements.

Hosted Payment Page: Default success and failure pages

For Merchants integrating the Hosted Payment Page, providing the success and failure endpoints is now optional, as we fo provide default success and failure pages as part of the feauture.

Security improvements and bugfixes
This release contains further internal improvements, optimizations and security improvements.

PCI Certified Merchants support

PCI-Certified merchants, who collect credit card data, are now able to initiate and process payments.

Security improvements and bugfixes
This release contains further internal improvements, optimizations and security improvements.

Pre-payment notifications

Pre-Payment method processing has been enriched by the set of additional web-hook notifications provided by SmartPay to the merchant shopping platforms:

• Payment Recognized
• Payment Reminder
• Underpaid Transaction Expiration
• Unpaid Transaction Expiration
• Overpayment

Please refer to this section for futher information.

Hosted Payment Page (Pay-by-link / Pay-by-QR )

Support hosted payment page integration journey for SmartPay. Entire payment process handled on hosted payment page - merchant submits checkout information and SmartPay provides a link for payment option selection and payment completion. Hosted page can also be accessed by scanning the QR code provided as a link. QR code can be easily sent in the email html-body or published on the web-sites as a regular image.

Security improvements and bugfixes
This release contains further internal improvements, optimizations and security improvements.

Strong API Authentication
SmartPay now supports basic authentication, Please refer to this section for more details.

Security improvements and bugfixes
This release contains further internal improvements, optimizations and security improvements.

[WebAPI] Error Details added to SmartPay error property

In case of payment processing failure, SmartPay provides an error-property providing additional information on the kind of error occurred - see response model and error handling documentation. With this change, we have added additional errorDetails to this error property providing further information on the kind of error occured (e.g payment_provider_card_invalid or payment_provider_card_stolen)

[WebAPI]   Provide modificationID in response of MIT authorize API

MIT authorize API now also supports a modificationID to distinguish between retried and newly created authorize requests. Please always make sure to use modificationID to keep your requests to SmartPay idempotent.

Security improvements and bugfixes

This release contains further internal improvements, optimizations and security improvements.

[WebAPI] IDKit Token support

Added Identity Kit token authentication in SmartPay WebAPI. 

[WebAPI]   Get & Delete Stored Payment option

Two new API methods introduced for managing consumer's stored payment options.

Security improvements and bugfixes

This release contains additional improvements and optimizations, also some security improvements.

[WebSDK] Support of multi-page checkout journeys

Support of the multi-page journeys enables Merchants / Dealers, to use a sales outlet / web-shop system distributing the checkout journey among multiple pages

[WebSDK] Clients browser cache control improvements

Fix for the cache issue on the Safari browser

Security improvements and Bugfixes

This release contains additional improvements and optimizations, also some security improvements.

[WebSDK] “Continue” Buttons Containers 

SmartPay Web Widget “Continue” button containers are separated between the selection view and the view of adding a new SPO. Title for each button can be specified separately. 

[WebSDK]  Control the deletion of SPO linked to subscription(s)

If the consumer decides to delete a stored payment option, SmartPay performs the check if the deleting SPO is in use by one or more subscription. Then the merchant receives the OnBeforeDeleteSPO callback enriched by the subscriptions list where SPO is in use, if any.  Based on the received information on this callback, the merchant decides to continue or prevent the payment option deletion.

[WebApi] New API to Close customer account

Enabling the feature of closing an existing customer acoount by calling this API "Close Account"

Security improvements and Bugfixes

This release contains additional improvements and optimizations, also some security improvements.

SEPA 'Direct' Connector Integration

SmartPay supports 'SEPA Direct' Kontocloud connector.

[MIT] Merchant manage-able Registered Payment Option selection

Enables merchants using SmartPay direct MIT flow to pre-select the payment option used for an existing subscription, based on the storedPaymentOptionReference they manage in their backend.

Consumer's culture specific amount formatting

When amount is placed on the Pay button of the SmartPay Widget, it is formatted according to the payment culture (provided into Checkout API or read from consumer's browser.

Bugfixes and improvements

This release contains additional improvements and optimizations, also some security improvements.

B2B and Split payments in SmartPay

Added split payments of marketplace and reseller model support.

Bugfixes and improvements

This release contains additional improvements and optimizations, also some security improvements.

Kontocloud Refund notification handling

Regardless of the source initiates the refund (Kontocloud API, Merchant Panel, or BackOffice), SmartPay is now able to handle the Refund notifications received from Kontocloud, creates a linked SmartPay Refund entry for it as well as sends a notification to the merchant. 

Bugfixes and improvements

This release contains additional improvements and optimizations, also some security improvements.

SMP Notification Engine

SmartPay is now able to notify the integrated systems and platforms about certain events occured to the payments in process by sending the web-requests to the provided end-point. Please refer to this section for more details.

Consumer & BillingAddress update in MIT

Consumer and billing address information is taken into consideration also in the MIT payment processing. The customer account in Kontocloud platform is updated accordingly.

User experience improvements

This release contains some improvements made to the SmartPay WebSDK:

• 'default' mention and preselection of the stored payment gets disabled when 'defaultSpoEnabled' flag set to false. 
• Any combination of transaction amount, currency code or sign together with static text can used as label of the 'Pay Now' button (resource-id 3.3). 
• When stored option is selected by the user, 'Continue' (resource-id 3.1) button is replaced by 'Pay Now' (resource-id 3.3) button.
• New instruction text can be shown during the payment option registration on the pop-up screen. Default value is empty. To customize the text, please update resource-id 6.1.

Please refer this section for more information about strings localization.

Refund for PayU

Refund operation for PayU payment method is now available.

"Stored payment option only” flow for CIT

In “Stored payment option only” flow the guest payment option selection is not shown (based on the merchant configuration). First the registration would take place to store the card (challenge). And second challenge would be triggered to authorize the CIT as per current flow.

Bugfixes and improvements

This release contains additional improvements and optimizations, also some security improvements.

SmartPay WebSDK redesign

SmartPay WebSDK has been cleaned-up and redesigned to improve user experience and to meet the latest VW group style guides. The update journey can be found here. 

IMPORTANT:

This change is backward compatible to your journey - however it will change the look & feel of the payment process. Therefore, please check the journey on your test systems and reach out to your rollout manager in case of any concern.

Merchant specific localization

Any merchant now has the option to update existing language files and/or add custom languages to be used in SmartPay. The section localization contains all instructions and guidelines on how to use this feature.

Payment method selection handler "onSelectionChanged"

The "onSelectionChanged" handler provides call back for any payment option selection change made by your consumer. See webSDK documentation for further details.

PayPal button styling

Within webSDK widget rendering a paypalButtonStyle object can be passed to customize the PayPal checkout / payment button. See webSDK documentation for further details.

Bugfixes and improvements

This release contains additional improvements and optimizations.

Payment form redirection improved

Payment form redirection endpoints have been optimized and moved to Lambda@edge to increase performance and stability.

Settlement and chargeback synchronization

SmartPay GetPaymentStatus API supports now settlement and chargeback updates and will return the respective transaction status in accordance with our payment status model.

SmartPay Widget Stored Payment Option Handling - "set default" and "delete" configurable

In some scenarios, the options to "set default" payment option or to "delete" a payment option might be misleading. Therefore, the two Boolean settings changeDefaultSpoEnabled and deleteSpoEnabled have been added into the widget render config object. By default, both are set to true, so that existing integrations do not change.

Klarna

"Merchant reference 2", which can be used in Klarna Merchant Portal to query transactions has been changed to become the related KontoCloud unique reference instead of the SmartPay transaction reference. This way, the payment can be found in KontoCloud and Klarna using the same SmartPay "reconciliationReference".

Bugfixes and improvements

This release contains additional improvements and optimizations.

WebSDK error handler simplified

Number of error codes had been reduced to six to simplify handling on merchant side, details can be found in WebSDK and WebSDK handler sections.

Your existing integration do not need to be changed; discontinued error codes will not be used going forward.

Languages added

Localizations added for French, Spanish, Italian, Polish, Swedish and Finnish language.

Bugfixes and improvements

This release contains several improvements and optimizations to WebSDK and internal processing.

Merchant initiated transactions

Support for merchant initiated transactions to manage recurring payments added. See merchant initiated transactions integration journey.

Please note: This service requires you as merchant to manage your consumer's payment options and payment schedule. If you want us to manage your subscriptions, please wait for our subscription module. It will be released later this year.

Payment provider

Alternative credit card payment service connector added to support Mobility Payments Solutions tokenization service.

Bugfixes and improvements

Performance improvements and bug fixes.

Additional Payment Options

SmartPay now supports pre-payment and pay on invoice for merchants using the KontoCloud order processing engine.

Klarna integration enhancement

Klarna integration allows settlement through Mobility Payments Solutions eWallet accounts.

Modification APIs

Field "Description" added to all modification APIs. It can be used to add a custom reference to a modification, which will be presented in merchant panel and reporting as well as on the consumer's account statement selected payment options.

WebSDK

Success and error handler updated. See WebSDK

Bugfixes and improvements

Several performance improvements and bug fixes.

Additional Payment Options

SmartPay now supports AMEX, JCB, Card Bancaire in guest and CIT flows. See PaymentOptions documentation.

CancelOrRefund API

New cancelOrRefund API might be used to cancel a transaction regardless of the state. See cancelOrRefund API.

Unified API Responses

Our modification API responses have been redesigned to report the status of all modifications related to a SmartPay checkout transaction. See response model documentation. Please note: All modification API documentations are update accordingly. Current response model is enhanced by additional fields, request model is not changed and backward compatible.

Payment Form

Payment form has been updated to improve usability. No changes to integration.

Checkout API Validation

Checkout API validations updated to support validation against existing documentation.

Klarna Direct Integration

Support of Klarna pay later and Klarna pay over time added. Please note: Use of Klarna requires a direct contract between merchant and Klarna. Please contact your Payment Solutions Specialist for further details. Payment options updated.

Refund API

Support of API initiated full and partial refunds. See refund API.

Checkout API structure updated

Checkout API structure is updated, to receive information regarding purchased products (required for Klarna Payments). See created checkout and data model.

Bugfixes and improvements

Update to capture API and auto-capture process to prevent concurrency issues and failed capture requests.

Mobile SKDs added

SmartPay now provides mobile SDKs for iOS and Android. Please contact your Payment Solutions Specialist for further details.

Capture-API

SmartPay now supports authorization only / authorization and merchant triggered captured process flow. See capture API.

Cancel-API

SmartPay now supports merchant triggered cancellation of an authorized transaction. See cancel API.

Hosted payment form

Payment form is now hosted by SmartPay, to address CSP issues, avoid "insecure" messages by some browser and to reduce risk of 3rd party scripts changing the iframe.

Bugfixes and improvements

SmartPay 1.5 contains several bugfixes and improvements under the hood. Covered topics among others: reinitialization of widget in react flows, compatibility issues with Microsoft EDGE browser, modal window loading issues.

Document version - 2021-06-09 - Release Notes 2.4 added