This repository has been archived by the owner on Mar 19, 2024. It is now read-only.
Releases: Ingenico-ePayments/connect-sdk-client-js
Releases · Ingenico-ePayments/connect-sdk-client-js
3.19.1
- Changed:
- The default value for the Google Pay field
gateway
is now changed toglobalcollect
.
- The default value for the Google Pay field
- Security:
- Upgraded
ini
dependency version to fix a security vulnerability.
- Upgraded
3.19.0
- Added:
- Added property
acquirerCountry
toBasicPaymentProduct
andBasicPaymentProductGroup
.
- Added property
- Security:
- Upgraded
gulp
dependency version to fix a security vulnerability inyargs-parser
dependency.
- Upgraded
3.18.1
- Changed:
- Updated
node-forge
version.
- Updated
- Fixed:
- Updated files in the
dist
folder. These were not up-to-date for version 3.18.0.
- Updated files in the
3.18.0
- Added:
- Added property
allowsInstallments
to classBasicPaymentProduct
.
- Added property
- Changed:
- The
getBasicPaymentProductGroups
,getPaymentProductGroup
andgetPaymentProductNetworks
functions ofC2SCommunicator
now use the response JSON as rejection reason if an error occurs. - The
getPaymentProductIdByCreditCardNumber
function ofC2SCommunicator
now adds the response JSON to the rejection reason as fieldjson
. session
now propagates the rejection reason it receives from theC2SCommunicator
to its caller.
- The
- Fixed:
- ApplePay payments that failed previously did not properly complete the payment flow. This has been fixed.
3.17.0
- Added:
- Support for Apple Pay was added to the SDK. When retrieving Payment Product(s), the SDK will use the Apple Pay
canMakePayment
API to determine whether Apple Pay is available. If thecanMakePayment
check fails, Apple Pay is not returned.
- Support for Apple Pay was added to the SDK. When retrieving Payment Product(s), the SDK will use the Apple Pay
3.16.0
- Added:
- Added
createPaymentProductSession
call for creating a payment product session.
- Added
3.15.0
- Changed:
- The IIN Details call will now send up to 8 digits of the provided Credit Card number to the Connect REST API. Providing 8 digits (or more), instead of 6, may result in receiving more detailed information about the Credit Card, such as (extra) cobrands.
- Security:
- Updated some dependencies which raised security vulnerabilities alerts from GitHub.
3.14.0
- Added:
- Added a new validator for the new
residentIdNumber
validation rule.
- Added a new validator for the new
- Security:
- Replaced
eval()
with a lookup for validation rules.
- Replaced
3.13.3
- Security:
- Fixed several security issues by removing unused dependencies or updating used ones.
3.13.2
- Fixed:
- Fixed a bug when unmasked credit card numbers were sent to the SDK when calling the encryption method.
- Fixed a bug in the
BoletoBancarioRequirednessValidator
if no fiscal number was provided.