Release note 21.3
To search in the page use Ctrl+F on your keyboard
- Payment in instalment
- Authentication amount
Thank you for your return. To give us more details you can contact us at this address : firstname.lastname@example.org
This release note gives you an overview of the functional content of the WL Sips 21R3 release.
It is separated in two parts:
- new additions in the WL Sips Solution, where are listed the modifications of new functionalities added to our offer
- regulatory changes
If you want to benefit of those new functionalities, please get in touch with your usual Sips contact if you are one of our client. Or, send us a message at the following email address: email@example.com.
Deliveries in production : from the 3 th of May until the 21nd of May 2021.
New features of the WL Sips Solution for merchants
The Sips Office Batch connectors now allow you to know whether the card used for payment is an Ecard or not. The information is returned in the virtualCardIndicator response field.
Card scan via mobile phone camera
With the bank card scan, WL Sips facilitates mobile payment. Your customer will no longer have to go through the tedious and error-prone step of entering their bank details on their mobile: they can scan them directly using their mobile camera. With this feature, natively supported by a majority of Android & iOS mobile environments, you significantly improve your conversion rate.
Management of the payment in instalments case via the Sips Office connector
In order to comply with the GIECB regulations in the context of instalment payments made via the Sips Office connector, you can now:
- value this payment case using the paymentPattern field in the authentication and authorisation request
- value the details of the payment staggering thanks to new input fields in the request (in a new recurringData container)
For the moment, this only pertains to card payments.
You will find all the details in the Office connector documentation once it has been updated.
Management of the authentication amount
In order to be in compliance with PSD2, merchants will now have the possibility of carrying out the cardholder authentication on an amount different from the amount to be authorised. This may be necessary for payments in instalments, multiple payments or even subscriptions.
This results in the introduction of a new field to be populated in the request, namely the "authentAmount" field.
You will find the details of this field in the 3-D Secure Guide documentation once it has been updated.
|Ref.||Appli.||Defect type||Solution summary||Priority|
|49833||SOE||Functional defect||Implementation of a verification of the format of the signature date when creating a paper mandate via SOE in order not to end up with an inconsistent date.||Important|
|50807||Paypage||Functional defect||Make the streetNumber field optional for the Oney 3X4X means of payment.||Important|
|51049||SOB (CSV)||Regression defect||Allow double quotes in empty fields of the Sips Office request file Batch in csv format so that its processing is not rejected due to an invalid file format (processingResponseCode = ).||Critical|
|51571||SOB||Regression bug||Delivery of a fix to allow the call to Paypal during duplication operations via Sips Office Batch.||Blocking|