6 posts tagged with "Network Tokenization"

Gateway Features​

Changed​

• Connector Settings: Add bracket notation for the connector setting Field Expression Operation for the target field extraData to allow dashes in the key name.
• Network Tokenization: Add an additional network token configuration to the existing setting to allow creating network tokens when processing subsequent transactions.

Fixed​

• Network Tokenization: Fix an issue where disabling network token processing also disabled network token creation.
• Transaction Details: Fix a bug where transaction logs are not properly formatted.
• Transaction Processing: Fix automatic capture to also work for failover transactions.
• UI: Fix the customer profile list view showing a wrong total number.
• Virtual Terminal: Add missing translation in the Pay-By-Link UI.

Gateway Adapters​

Changed​

• Adyen (ADY): Add handling of Merchant Advice Code from callback notifications.
• Braintree (BRA-EP1-SWI): Add support for Swish, a Swedish mobile payment method that allows customers to make real-time payments using their phone number and banking app.
• checkout.com (CHE-EP2-BIZ): Add the payment ID in the callback notification as psp:bizumPaymentId.
• dLocal (DLO-EP1): Add a new optional configuration setting which allows sending a custom X-Dlocal-Payment-Source header.
• eMerchantPay (EME-EP3-CC): Add support to automatically migrate existing recurring card subscriptions from the legacy platform to the Genesis platform without requiring cardholders to re-register.

Added​

• NaverPay (NAV-EP1): NaverPay is a South Korean digital wallet and online payment platform by Naver Corporation. It enables users to make seamless payments across e-commerce sites, apps, and offline merchants. The platform offers secure transactions, loyalty rewards, and easy integration for businesses.

Fixed​

• KCP PC (KCPPC): Add a temporary configuration setting which should fix issues with refunds.
• PayPal Complete Payments - PPCP (PPCP-EP1-PPE): Fix an issue with the wallet reference handling.
• Redsys (RED-EP2-BIAPI): Fix an issue where the authCode is not included in the callback notification.

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.

Gateway API​

Fixed​

• Transaction API: Fix an issue where card data is not returned in the API response if the transaction was processed with a network token.

Gateway Features​

Changed​

• Risk Profile: Extend Forter risk engine to support installments.

Added​

• Job Configuration: Add support to export the jobId. Supported for Write Customized Settlement CSV and Write Settlement CSV with Split Transaction Merchant.
• User Management: Add a Security Center setting to automatically disable users based on an inactivity threshold.

Fixed​

• Network Tokenization: Fix an issue where asynchronous network tokens are stuck in pending state.
• Post Processing Jobs: Fix an issue where collected transactions without a seller merchant (Marketplace) are not displayed.
• UI: Fix an issue where the tenant drop-down does not appear on the Global Routing Profile page.

Gateway Adapters​

Changed​

• 2C2P (2C2P): Add a new configuration setting to specify the region.
• dLocal (DLO-EP1-CC): Add a new configuration setting to include the selected number of installments in the callback notification.
• PayPal Complete Payments - PPCP (PPCP):
  • Add support for the locale parameter to manually override the default language of the payment button.
  • Add a new configuration setting to use the UUID instead of the Merchant Transaction ID for the invoice_id.
• PayU (PAU): Add support for LATAM settlements for the Report Type Payout Reports.

Added​

• Erste Group (EG): Erste Group is a leading financial services provider in Central and Eastern Europe, headquartered in Austria. It offers retail, corporate, and investment banking services to millions of clients across multiple countries. The group is known for its strong regional presence, digital banking solutions, and commitment to sustainable finance.

Fixed​

• 2C2P (2C2P): Fix the behaviour of the Ignore Scheme Fees setting.
• Alipay - Ant Group (ANT-EP1-ALIPL): Fix an issue when the optional configuration settlementCurrency is not set.
• Dimoco (DIM): Fix handling of the reconciliation amount.

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.

Gateway Features​

Added​

• Account Updater: Add a configurable setting to specify the update interval for expired cards. Requires the merchant.account-updater.custom-interval permission.
• Connector Settings: Add a new connector setting to disable network token processing.
• Job Configuration: Add an option to skip the SFTP upload when no matching file is found for the Upload document to SFTP server export step.
• Multi-method connector: Add a new setting to display all payment methods for transactions with withRegister=true, regardless of whether they support recurring payments. If the selected payment method does not support recurring payments, the withRegister flag will be set to false. For customer profiles, the payment instrument will not be stored in that case.
• Virtual Terminal: Add support for split transactions in the Virtual Terminal.

Removed​

• Network Tokenization: Remove transaction indicator requirement check for subsequent network token transactions.

Fixed​

• Transaction Processing: Fix an edge case where the transaction token is not properly stored.

Gateway Adapters​

Changed​

• American Express (AMX-EP1-AMX): Update the settlement parser to support the new Global Raw Data Reconciliation File (GRRCN) version 4.01 (up from 3.01).
• PayU (PAU-E01-CC):
  • Add support for installments.
  • Enable recurring transactions.
• PayU (PAU-E01-PAE): Add a default expiration date of 1 day.

Fixed​

• dLocal (DLO): Fix the private key field in the provider settlement configuration.
• GoCardless (GOC-EP1-BT): Fix handling of the transaction status in the mandate flow.
• PayPal Complete Payments - PPCP (PPCP-EP1): Add support for additional transaction update callbacks.
• Worldline (ING-EP5): Fix parsing of error codes and error messages.

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.

Gateway API​

Changed​

• Transaction API: Modify the tracingData.transactions[].status field to use an enum with predefined status values instead of a string.

Added​

• Transaction API: Add returnData.binSegment and returnData.binRawData for returnData._TYPE of cardData in the Transaction API response.

Fixed​

• Transaction API: Fix an issue where the returnData.merchantAdviceCode (MAC) was not returned when its value was zero.

Gateway Features​

Changed​

• Account Updater: Improve account updater batch processing.
• Performance: Improve performance when using a large number of routing rules.
• Transaction Details: Enable Apply Extra Data from initial transaction and Apply new Extra Data by default for manual refunds.

Added​

• BI Data Source: Add result_extra_data.googleCryptogramPresent to reflect 3DS authentication for Google Pay transactions.
• Transaction Processing: Introduce the extraData.googlePayCryptogramPresent field in the Transaction API response to indicate 3DS authentication for Google Pay transactions.

Fixed​

• Network Tokenization: Fix an issue where network tokens were not deleted after failed transactions.
• Post Processing: Fix an issue that prevented manual file uploads of MIME type application/x-ndjason.
• Transaction Processing: Fix an issue that prevented schedules from being created in certain scenarios.

Gateway Adapters​

Changed​

• Redsys (RED-EP2): Support Register transactions and add recurring functionalities for the BizumAPI payment method.

Fixed​

• PayPal (PPA): Improved settlement handling for edge cases during reconciliation.
• PXP (PXP-EP1): Fix error mapping for specific error codes.

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​

Added​

• Provisioning API: Two new fields have been added to the merchant response model: ntsEnrollmentStatus and networkTokenizationEnabled.

Features​

Changed​

• Job Configuration: Information on inherited job type templates is now displayed, informing users as to why the template cannot be edited.

Added​

• Network Tokenization:
  • Information on the status of enrollment for network tokenization is now available in the base data for a merchant. A new line, "Network Tokenization" has been added. If the merchant has a TRID assigned, the status is displayed as "enabled" when viewing the data as an admin with the permission "tokenization.networkTokenization.enrollment.show".
  • Merchants can now be filtered by their NTS status in the overview.

Fixed​

• Pay-by-Link: Fixed an issue with the virtual terminal's result page not updating correctly if the initial transaction fails. Instead of displaying transaction data from the most recent (successful) transaction, data from the first (failed) transaction continued to be displayed.
• Provider Settlements and Reconciliation: Fixed an issue that would cause chargeback reversals to be created for the debit transaction, instead of the chargeback transaction.
• Transaction List: Fixed an issue that would cause an error in the advanced search when changing the comparison operator from a range to any other operator.
• Transaction List: Fixed an issue with sorting credit card fields. Note that BIN data cannot be sorted.
• User Management: The frontend.statistics.show permissions now governs access to the pivot table as well.
• Virtual Terminal: Fixed an unhandled exception in the virtual terminal that would occur if the fee set or fee entity was not found. The exception is now handled and an empty surcharge value is returned.

Adapters​

Changed​

• Adyen (ADY): The payment reference for settlements is now saved.
• Amazon Payment Services (AMAZO): It is now possible to filter transactions by the status "Accepted".
• MultiSafepay (MUL): Added the chargeback reason for chargebacks.
• Stripe (STRV2-EP1-MAS): Additional data from the Stripe API response is now included in the postback's extraData.

Added​

• dLocal (DLO-EP1): Added support for the Sinpe payment method. This method supports bank transfers in Costa Rica.
• Worldline (ING-EP2): Added support for payments via Trustly.
• Zona Virtual SA - Zonapagos (ZONA-EP1-ZP): Added a generic payment method that redirects to the Zona Pagos payment page. The consumer can then select the desired payment method on this page to initiate the transaction.

Fixed​

• Adyen (ADY-EP3-BIZ): Fixed an issue that would cause transactions that had been processed successfully to be assigned the status error or pending.
• checkout.com (CHE): Fixed an issue that would cause an error when retrieving the session ID.
• eMerchantPay (EME-EP3-SEP): Fixed an error that would occur if the customer was not an IBAN customer.
• Mashreq (MASH): Fixed an issue when checking 3DS credentials that would cause a type error.
• Mercado Pago (MERPA-PROD): Fixed an issue with register transactions caused by the Amount For Card Verification not being included in the request to retrieve the issuer and payment method ID from the PSP.
• Skrill (SKR-EP1): Fixed an issue related to email addresses not being tied to a Skrill account when requesting a payout. This would cause the payout to fail.
• Volt (VOL): Fixed an issue caused by incorrectly handling errors in a response as a result.

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.