| Release Version |
Release Date |
Summary |
| 2.46 |
2024-10-30 |
- Payment Facilitators are now able to provide all acceptor location data under the sponsoredMerchantData object
- The parameter sourceOfFunds is now supported for PushFunds
- Added support for Transaction Link Data - currently only available for Mastercard
- The parameter cardHolderData->email in the CardVerification endpoint is now validated for a proper email address
- Various documentation updates
|
| 2.45 |
2024-09-26 |
- Independent Sales Organizations (ISO) are now able to provide their isoId as an input parameter under the schemeData object
- Payroll is now supported as a transactionType in the PushFunds endpoint
- The accepted currencies for Amex are: ISK, EUR, USD and GBP
- Various documentation updates
|
| 2.44 |
2024-08-19 |
- Payment Facilitators are now able to provide their Payment Facilitator Id to the schemes in the field schemeData->PaymentFacilitatorId
- It is now possible to make multiple captures when using authType->PreAuthorization
- Multiple documentation and example updates
|
| 2.43 |
2024-07-16 |
- Unsupported card types will now return an error message to the user
- The timeout value of the CardPayment endpoint has been reduced from 100 seconds to 30 seconds
- Various technical improvements
|
| 2.42 |
2024-06-20 |
- The parameter eci is now available in the CardVerification response message as part of the frictionlessData object
- The parameter transStatusReason is now available in the CardVerification response message
- Links to the Implementation Guide from the API have been updated
|
| 2.41 |
2024-05-13 |
- Refund with correlationID examples have been added to the Implementation Guide
- CardVerification example card numbers have been updated in the API
- Multiple documentation and example updates
|
| 2.40 |
2024-04-11 |
- Merchants are now able to provide their own MessageID through the field acquirerReferenceNumber in CardPayment and WalletPayment endpoints when the operation is either Sale or Auth
|
| 2.39 |
2024-04-05 |
- Merchant Advice Codes are now available in the GetBatchReport response
- CardholderRelatedData can now be supplied in cases where the merchant wants to use Account Name Inquiry
- Various documentation improvements
|
| 2.38 |
2024-03-21 |
- Payment Account Reference (PAR) is now available in the transactionReports of GetBatchReport
- The WhenToClear parameter has been updated to include more information regarding when this value will be used
- The authorization expiry date is now available in the response for CardPayment, VirtualCardPayment and WalletPayment
- Partial authorizations are now supported for PullFunds
- AuthorizationIdentifier is now available in PullFunds response
- Updated examples for Google Pay payments
- Various documentation updates
|
| 2.37 |
2024-03-11 |
- Changes to the mandatory fields in 3DSecure (only one phone number OR email address is required and cardholder billing address information is no longer required but highly recommended)
- Full merchant reference data may now be provided in Create virtual card payment batch
- Card VR (CVC validity) is now available in the response for Card payment, Pull Funds, and Create virtual card
- MerchantCountryOfOrigin no longer accepts numerical values
|
| 2.36 |
2024-03-01 |
|
| 2.35 |
2024-02-20 |
- Users may now provide merchantCountryOfOrigin within sponsoredMerchantData in requests
- PAR is now being provided in all responses when it is provided from the issuer
|
| 2.34 |
2024-01-31 |
- Merchants may now indicate if a PullFunds transaction is related to cryptocurrency using the SpecialConditionIndicator.
- Merchants may now provide the Electronic Commerce Indicator (ECI) received when decrypting the payment token in WalletPayments.
- The ECI is now provided in WalletPayment, CardPayment and VirtualCardPayment responses.
|
| 2.33 |
2024-01-19 |
- Any updated masked card numbers are now available in the batch report as updatedMaskedCardNumber.
- The transaction ID of the original transaction is now available in the Refund response as OriginalTransactionID.
|
| 2.32 |
2023-12-13 |
- Masked token data is now available in the GetBatchReport response (when available)
- Cardholder data, billing data and browser data became mandatory in the CardVerification endpoint
- Zero amount transactions are now possible in the WalletPayment endpoint
- Added support for sending URLs within the MerchantReferenceData
- Updated examples for Apple Pay/Google Pay payments, PullFunds and Refund with Correlation ID are now available
- The BinRange endpoint has become deprecated and is no longer supported
|
| 2.31 |
2023-11-09 |
- Marketplace support added
- Masked schema token displayed in responses
- Making refund with correlationId possible
- CardCheck feature in card payment
|
| 2.30 |
2023-10-18 |
- Marketplace support added
- Masked schema token displayed in responses
- Making refund with correlationId possible
- CardCheck feature in card payment
|
| 2.29 |
2023-09-28 |
- Pull funds added
- SCA exemptions changed
|
| 2.28 |
2023-09-13 |
- Remove version 1.0
- Some small bugfixes
|
| 2.27 |
2023-08-29 |
- Improve Push funds
- Google Pay - new parameter to return decrypted token without payment
- Improve first/subsequent transaction in Walletpayment
- Return MerchantAdviceCode and MerchantAdviseDescription in payment endpoints
- Specifications improvements
|
| 2.26 |
2023-07-20 |
- Address verification data added to CardPayment
- Allow 1-8 digits in TriplegInformation/Array/FareBasisCode
- Remove Xid from CardVerificationdata
- Display response code information
|
| 2.25 |
2023-07-04 |
- Remove restrictions for MailOrder and TelephoneOrder trans types
- Add sponsored Merchant data to Push Funds
- Support First transaction in MTP WalletPayment
- Add the field tripLegDepartureDate to Airlinedata
- Let Merchant know if refund operation was performed as refund or reversal
- Add required information to Mastercard Pushfunds endpoint
|