3 posts tagged with "3DS"

API​

Added​

• Transaction API: Added the parsedMerchantAdviceCode to transactions that contains the parsed merchant advice code for those adapters that support MAC, including the Simulator adapter.

Features​

Added​

• 3DS: The CardholderInfo field from the issuer is now returned for failed 3DS authentications. The information in this field provides additional information on why 3DS failed and can be displayed to the user.

Removed​

• Setup: Merchant and connector templates have been removed. The same functionality can now be achieved using the global settings.

Fixed​

• Callback: Fixed an issue with callbacks when the postback format was set to inherit and a follow-up transaction was using a different API version than the initial transaction.
• Post Processing: Fixed the verification of a mandatory job period setting in job schedules.
• Post Processing: Fixed an issue introduced by a recent UI update that caused some buttons to no longer work in the Post-processing configuration.
• UI Navigation: The UI has been updated to support 8-digit BINs.
• Virtual Terminal: Fixed an issue where confirmation emails were sent out incorrectly. Mails would be sent if the "vt mail on success" setting was enabled, even if the transaction was not related to the virtual terminal. Mails were also sent for all pay-by-link transactions, even if the option to send out emails for PBL was disabled.

Adapters​

Changed​

• American Express (AMX-EP1-AMX): A new setting is available for the American Express settlement data fetcher that saves the Amex payment number as the batch number, instead of using the date and time.
• Worldpay (WOR-EP1): The line item SETTLED_MISCELLANEOUS (for fees not associated with a particular transaction) is now handled without creating a conflict.

Fixed​

• 2C2P (2C2P-EP1): Fixed an issue where settlements were sometimes fetched twice.
• Adyen (ADY-EP3-APP, ADY-EP3-CC, ADY-EP3-GOP): Fixed a bug that occurred when cross-referencing a transaction at another PSP.
• Braintree (BRA-EP2): Billing address data from the initial transaction is now stored and can be used in follow-up transactions. This billing address data is now used to process debit and preauthorization transactions.
• Braintree (BRA-EP2): The field additionalId1 can now be mapped to the descriptor object, allowing the invoice number to be passed to Braintree.
• Nuvei (NUV): File names for settlements can now be entered using a new optional regular expression field.
• Volt (VOL-EP1): Fixed an issue with settlements caused by both debits and refund transactions related to the same transaction having the same ID in Volt, causing refunds to sometimes be settled instead of debits.

Please note that some of the features mentioned in the release notes may initially be available only within our sandbox environment for testing purposes. These features will be made available in the production environment upon successful testing and approval.

Features​

Changed​

• 3DS: Rolled back changes that removed 3DS postback data for merchants using external MPI.
• Transaction details: The payment token is now included in the customer profile data in callbacks and API status calls.

Added​

• Post Processing: The filter in the Collect All Transactions (in period) Post Processing collecting step now supports filtering adapter errors and internal errors by the date on which their status changed.
• Provider settlements and Reconciliation: Added a new tab to the conversion rate system settings that allows deviation tolerances to be defined for currency pairs per tenant. This is then used to verify settlements rather than the tenant's global tolerance or default tolerance (0.02%).
• Settings: Added a new project setting, Postback: Include Basic Auth header, which allows a header to be sent for basic-auth postback. This setting is also available as a global connector setting.

Fixed​

• Account Updater: Fixed an issue where only one level of sub-tenants were filtered. Fixed an issue that would cause an error when changing the master tenant in the detailed view.
• Customer profile: Fixed an issue that triggered an error when creating a customer profile via the API's customerProfileData field without setting any customer data in the transaction.
• Pay-by-Link: Fixed an issue that would result in an empty redirect URL. Fixed an issue with redirects to expired pay-by-link transactions without an error URL that would cause an exception. The correct page is now displayed.
• Pay-by-Link: Fixed an issue that caused all pay-by-link transactions to be withRegister transactions. It is now possible to choose whether the transaction should be a withRegister transaction or not using the with Register (Store Payment Instrument for Card-on-File payments) checkbox.
• Post Processing: Fixed an issue that would cause an error for sub-tenants when attempting to select job configuration templates created at the parent provider level if no fee entities were available in the template.
• Risk Engine: Fixed an issue with the Count of different credit cards of same device risk rule if no customer or browser data is available.

Adapters​

Changed​

• checkout.com (CHE-EP1-CC): The AVS and CVV results are now added to the extraData in callbacks if available in the response.
• DPO Pay (PAYGA-PYGT-PMR): Added support for the USSD payment method.
• eMerchantPay (EME): Added support for chargeback reasons, which are now forwarded to merchants.
• Nuvei (NUV): Updated the Westpac settlement handling.
• Paysafecard (PSC): Added support for payouts.
• Redsys (RED-EP2-BIZ): Added support for refund transactions.

Added​

• Nuvei (NUV-EP1-CC): Added support for chargeback notifications from Nuvei.

Removed​

• Bank of America (BOFA-EP1-ACH): The Addenda row was removed from the NACHA file when using the WEB format, as it is not required.

Fixed​

• Nuvei (NUV-EP1-CC): Fixed issues with the references to related transactions, which should either contain the Nuvei transaction ID, the transaction ID of the previous 3DS request, or the transaction ID of the authorized payment.
• Nuvei (NUV): To handle issues with settlements, a new optional configuration setting has been added for the reconciliation data fetcher ID, which checks whether the system needs to wait for the CB report for the same date when retrieving settlements.
• PPRO (PPR-EP1): Fixed an issue with settlements, that is caused by PPRO sometimes providing multiple files with the initial file only containing volume data, and subsequent files containing the actual transaction settlement data. A new option is now available in the data fetcher configuration, Only retrieve settlements if all fees and volume files are present that checks whether all settlement files are present before retrieving and processing the files.
• Valitor (VALIT-EP1-CC): Fixed an issue related to duplicate transaction IDs issued by Valitor that would cause refunds to be ignored in settlements due to another transaction having the same ID.
• Volt (VOL-EP1): Fixed an issue with Volt settlement files caused by the formatting of the CSV data.

Please note that some of the features mentioned in the release notes may initially be available only within our sandbox environment for testing purposes. These features will be made available in the production environment upon successful testing and approval.

API​

Fixed​

• Provisioning API: Fixed an issue with the Provisioning API that would prevent the creation of vault connectors under specific circumstances.

Features​

Changed​

• Fee Engine: Changed the behavior for configuring GST fees to reflect the Surcharge dependencies.

Added​

• 3DS: The highest-supported 3DS version is now used where possible (i.e. 3DS v2.2.0 is used instead of v2.1.0). For more details, see 3DS 2.1.0 EOL and Changes to 3DS in IXOPAY.
• Connector Settings: A new connector setting has been added (Postback/Status: Include isAFT in postback/status response) that includes information on whether AFT was performed using this transaction.
• Post Processing: Added the ability to check whether data fetchers are set up correctly after adding or editing the data fetcher (currently only supported with the SepaExpress v1 settlement data fetcher). Results are shown in the data fetcher edit view.
• Risk Profile: Added a filter check for all transactions with a payment instrument where the doNotResubmit flag is set for the Count of transactions using same payment instrument risk rule. Added the transaction's error status (error_adapter, error_internal, cancelled, invalid) to the transaction's status selection for the Count of transactions using same payment instrument risk rule.
• Translation: Added Croatian and Slovenian to the merchant admin interface.

Fixed​

• 3DS: When external 3DS solutions are used, the values are no longer included in the postback, as IXOPAY can neither guarantee they are correct nor complete.
• Customer profiles: Fixed an issue that resulted in an incorrect wallet reference ID being entered in customer profiles.
• Multi-method connector: Fixed an issue relating to the retrieval of customer profiles when used in combination with multi-method connector.
• Search: Fixed an issue that prevented the advanced search filters from working with certain adapters.
• Transaction List: The URL included in the transaction tree on the transactions details page not link to the transactions view.
• Transactions: Fixed an issue where sending an amount without specifying a currency would set the amount to 0 for void transactions. This resulted in a full void instead of a partial void.
• UI: Fixed the tooltips in the screens used to edit connectors.
• UI: Fixed the responsive styling for the 3DS configuration, making values easier to see.

Adapters​

Changed​

• 2C2P (2C2P, 2C2P-EP1-CC): Added the option to ignore scheme fees to the settlement data fetcher configuration.
• Braintree (BRA-EP2-CC): Added support for a new disbursement file.
• Braintree (BRA-EP2-CC): The Braintree adapter now supports the new settlement file format for Myanmar.
• Checkout.com (CHE-EP1): Added the ability to configure a private key for the Checkout.com settlement data fetcher.
• DPO Pay (PAYGA-PYGT-CC): Added a new Private key parameter that can be configured at the connector level for SFTP servers.
• EquensWorldline (EQW-EP2): Changed from v2 of the API to the new v3 API.
• Mastercard Payment Gateway Services (MPG-EP1-CC): Added support for Westpac settlement file handling.
• Trustly (TRU-EP1): The response status can now be configured and failed payouts are set to FAILED.

Added​

• Straight2Bank (STRAI-E01-MPESA): The Straight2Bank adapter now supports M-Pesa as a payment method.

Fixed​

• American Express (AMX-EP1-AMX): Fixed the handling of chargebacks and chargeback reversals in settlements for American Express.
• Bank of America (BOFA-EP1-ACH): Fixed an issue that caused export errors due to missing mandatory data.
• Bank of America (BOFA-EP1-ACH): Fixed an error regarding the export of routing number extra data in the NACHA export for Bank of America.
• DOKU (DOKU, DOKU-EP01): Added support for refund transactions ini DOKU settlements.
• DOKU (DOKU, DOKU-EP01): Fixed the mapping of settlement fees and the handling of settlement amounts for the DOKU adapter.
• DPO Pay (PAYGA-PYGT): The DPO settlement parser has been updated to handle the new CSV structure of the settlement files.
• DPO Pay (PAYGA-PYG): Fixed the SFTP login to include the mandatory private key.
• Mashreq (MASH-EP01-CCRD): The default currency for the Mashreq adapter has been changed to QAR.
• PAYONE (PASIX-EP1-CC): Updated the configration for Six settlements to allow a customer-specific key to be entered.
• Redsys (RED-EP2-BIZ): Added support for HMAC_SHA256_V1 as a signature version for merchant integrations.
• Straight2Bank (STRAI-E01): Fixed the handling of refund settlements for Straight2Bank.
• Trustly (TRU-EP1): Fixed the handling of Trustly credit notification events for payouts to update the status to error and prevent chargebacks from being created.
• Volt (VOL-EP1): The bearer token status was re-added to the status request header after it was inadvertently removed.
• Volt (VOL-EP1): Updated the handling of Volt settlement files.
• Worldline (ING-EP2): Fixed a bug regarding the handling of webhooks.
• Worldpay (WOR-EP1): Fixed an issue that caused the settlement data fetcher to retrieve multiple settlements if the same settlement file was uploaded more than once.

Please note that some of the features mentioned in the release notes may initially be available only within our sandbox environment for testing purposes. These features will be made available in the production environment upon successful testing and approval.