eSuite v166.0

Strong Customer Authentication (SCA): 3D Secure

Following the recent updates & advice published by the European Banking Authority (EBA), MPP Global announced in July that it has broadened the scope for the development project to cater for both the introduction of the planned 3D Secure version 2.0 service as well as extending the current version 1 service to include all CIT scenarios.

The EBA document indicates that the current 3D Secure version 1.0 service, which has been available since 2001, does satisfy the compliance requirement for SCA, albeit not as dynamically or extensively as the version 2 service allows.

While work on 3D Secure 2.0 continues, Within this release, the majority of developed for 3D Secure 1.0 will be available for clients to comply with the SCA deadline. A summary of key updates to support 3D Secure 1.0 include:

• Ability to trigger the 3D Secure v1.0 process when updating a card against an account
• Ability to complete the 3D Secure v1.0 process when updating a card against an account
• Ability to trigger a 3D Secure v1.0 flow when upgrading a subscription immediately
• Ability to complete a move subscription following the completion of the 3D Secure Process
• Within eSuite HQ, an isMoto flag (set to true) has been added to Virtual Terminal (legacy) so that 3D Secure is not triggered during a MOTO transaction
• Within eSuite HQ, an isMoto flag (set to true) has been added when requiring a charge on Move Subscription so that 3D Secure is not triggered during a MOTO transaction (166.1)
• Ability to trigger a 3D Secure v1.0 flow even if the charge is zero (166.1)
•  via iShop, the ability to trigger a 3D Secure Process when updating a card in self-care (166.1)

Additionally, within this release we have introduced several new changes within eSuite HQ to support our continued development for 3D Secure version 2.0. This includes:

• Within eSuite HQ, an isMoto flag (set to true) has been added to Virtual Terminal (new) so that 3D Secure is not triggered during a MOTO transaction
• Within eSuite HQ, when updating an account and adding a new card to payment details, an isMoto flag (set to true) has been added so that 3D Secure is not triggered

Card on File (CoF)

To comply with with Visa & Mastercard global regulations on recurring purchases, we have introduced some foundational work include a card-on-file indicator for those transactions which are are performed using stored payment details. Additionally, the Credit Debit Transaction report has been updated to include CoF flags.

Surfacing Enhanced Error Response Codes for Global Pay

Over the past few releases, a change was introduced to surface Enhanced Response Codes received from Global Pay (Realex) for supported Acquirer connections. We have now added the ability for these response codes to appear within standard eSuite reporting such as the CreditDebitTransaction Report.

Release Service Pack

• When creating a new redirection using the Delivery Calendar,  can now use the date pickers to select dates during periods where existing redirections are already configured
• When creating a new redirection using the Delivery Calendar, dates now followed region date formatting dependent on the language selected upon eSuite HQ login
• When creating a new redirection using the Delivery Calendar, additional validation has been adding to include mandatory fields prior to saving
• When creating a new redirection using the Delivery Calendar, the date pickers will now reset when adding a new redirection or stop notice
• When attempting to update or retrieve a delivery pattern using REST API, if there is no pattern configured against an existing subscription, a 204 response code will now be returned
• Within the order fulfillment page in eSuite HQ, users will now be able to save an edited supplier notification date
• Within eSuite HQ, upon updating a fulfilment by setting a new date or status, the revised data will be translated into supported languages
• Additional styling improvements to eSuite HQ when configuring or view delivery calendar data
• When updating an existing redirection using the Delivery Calendar, there will be no console errors triggered upon successful save
• Within eSuite HQ, when using Virtual Terminal, users will be able to specify a start date for bundle purchases
• Within eSuite HQ, when a bundle subscription is purchased and auto renew is enabled, all delivery patterns and redirections will be visible if configured
• Fixed an issue that could prevent an order refund in some cases where there are duplicate order parameters
• Improved reporting of offline order activity
• Improved recording of error details returned by Realex (Global Payments) payment provider when a card payment fails
• The payment reference field is now populated on the Credit/Debit Transaction Report when there is an error with a transaction
• Non-superusers of eSuite HQ will now be able to create a service type of Bundle Purchase