11 posts tagged with "Transaction Processing"

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 Features​

Changed​

• Provider Settlements and Reconciliation: Rename Reconciliation Conflicts page to Provider Reconciliations.
• Risk Profile: Rename Cumulative Score column to Total Score.

Added​

• Connector Settings: Add a new connector setting Postback: Defer sending until after the API response has been returned.

Fixed​

• Transaction Processing: Fix an issue that could cause a Token not found error in certain circumstances.

Gateway Adapters​

Changed​

• dLocal (DLO-EP1-MP): Add support for the new payment method MultiPago. MultiPago is a cash-based payment method in Latin America that allows customers to pay for online purchases using payment slips at convenience stores or banks.
• Nuvei (NUV-EP1-ALIUN): Add support for the new payment method Alipay+ Unified Payment. Alipay+ Unified Payment is a cross-border digital payment solution that allows customers to pay with various supported e-wallets and other payment methods across multiple regions.
• Nuvei (NUV-EP1-RAKUT): Add support for RakutenPay, a Japanese e-wallet that lets customers pay online or in-store via the app or by scanning a QR code.
• PayPal Complete Payments - PPCP (PPCP): Add support for sending transaction context if data is provided.
• PayPal Complete Payments - PPCP (PPCP-EP1-PPE): Add a new setting useProvidedMerchantUrls to fix mobile payment processing for merchants using PayPal's iOS/Android SDK.

Fixed​

• Cybersource (CYS-EP1-CC): Fix mapping of transaction indicators to the commerceIndicator.
• JCC Payment Systems (JCC-EP1-CC): Fix mapping and handling of callback notifications.
• KakaoPay (KAKAO-EP1-KAKAO): Fix refund handling to ensure each refund is correctly matched and settled.
• Worldpay (WOR): Ensure correct behavior for debit transactions by setting delay capture to 0.

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​

• Provider Settlements and Reconciliation: Add ability to manually upload reconciliation files.

Fixed​

• Post Processing Setting: Fix a bug where setting a provider's adapter to - caused an error.
• Transaction Processing: Improve handling of follow-up transactions to prevent errors after deregistration.

Gateway Adapters​

Changed​

• Adyen (ADY): Improve error mapping to consider the reason value when provided.
• Adyen (ADY-EP4): Add documentation for referenced and unreferenced Refunds.
• Certegy (CERTE-EP1-ACH): Fix Register and Refund handling.
• DPO Pay (PAYGA-PYGT): Add support for Partial Refunds.
• PPRO (PPR-EP1): Update the endpoint from https://api.girogate.de to https://simpleapi.ppro.com.

Fixed​

• Adyen (ADY-EP3): Fix an issue where extra data was not forwarded for Refunds.
• Bangkok Bank (BB): Fix handling of negative VAT values for settlements.
• dLocal (DLO): Fix an issue with parsing settlement files.

iFrame​

Added​

• UT iFrame: Export TypeScript types from main entry point for standard importsConfiguration, Authentication, HMACAuthentication, and other key types now available. Resolves issue requiring non-standard import paths from node_modules.

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​

Changed​

• Meta connector: Remove the option to change the type of an existing meta-connector (routing / multi-method) to prevent unexpected behavior and ensure consistent functionality.

Added​

• Connector Settings: Add a new connector setting Add Hard Decline Error Codes which allows specifying additional error codes that prevent failover transactions.

Fixed​

• Connector Settings: The connector setting Accept postbacks from other connectors will now properly ignore meta-connectors if provided in the list.
• Provider Settlements and Reconciliation: Fix an issue where a transaction was not settled correctly if a fee-only settlement in a different currency was received before the actual transaction settlement.
• Transaction Processing: Transactions with an expired or non-existent transaction token will no longer be retried.
• User Management: Fix a minor display inconsistency in the permissions list when configuring roles.

Gateway Adapters​

Changed​

• Adyen (ADY-EP4-CC): Add additional data mappings and documentation.
• Amazon Payment Services (AMAZO): Add settlement handling.
• Amazon Payment Services (AMAZO-EP1-NAP,AMAZO-EP2-NAP): Add support for the new payment method NAPS. NAPS is Qatar's national debit card network which offers a convenient, card-independent local payment method, enabling seamless, real-time transactions between businesses and Qatari shoppers across participating Qatari banks.
• Bangkok Bank (BB): Adjust settlement handling to support a new VAT format with VAT provided once per file instead of per transaction.
• Nuvei (NUV-EP1-PSE): Add support for the new payment method PSE. PSE (Pagos Seguros en Línea) is a popular real-time online bank transfer payment method in Colombia that allows users to pay directly from their bank accounts.
• Worldpay (WOR-EP1-KLAPN): Use a default Order Line Item if none is provided, to meet mandatory requirements by Worldpay for Klarna.

Added​

• Digit Secure (DS-EP1-T2P): New push adapter with payment method Tap2Pay.

Fixed​

• Cybersource (CYS): Fix parameter typo from extraData.reconciliationId to extraData.reconciliationID (captialize D in ID).
• KakaoPay (KAKAO-EP1-KAKAO): Fix incorrect mapping of error responses.
• KCP Mobile (KCPMO): Fix issue with settlement handling for refund transactions.
• KCP PC (KCPPC): Fix issue with settlement handling for refund transactions.
• Simulator: Fix issue where payment.js did not work with the Simulator adapter.

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​

• BIN Lookup: Add the BIN segment to the transaction details view in the admin and merchant portals.
• Connector Settings: Add the Copy Description to Chargeback Reversal connector setting. When enabled, the description from the original transaction will be copied to the chargeback reversal.
• Connector Settings: Add the Copy Merchant Meta Data to Chargeback and Copy Merchant Meta Data to Chargeback Reversal connector settings. These settings enable the copying of merchant metadata to newly created chargebacks or chargeback reversals initiated through Settlements or Reconciliations.
• Transaction Processing: Add Japanese translations for the loading screen that appears after a customer submits the payment or 3DS form for transactions requiring additional processing time.

Gateway Adapters​

Changed​

• checkout.com (CHE-EP2): Add documentation for the extraData.recipientDateOfBirth and extraData.senderDateOfBirth parameters in the AFT section of the connector documentation.
• Nexi Group (NETS-EP2): Improve the description of error messages for the connector.
• Paymob (PMO-EP2-CCRD): Add the bank_installments_integration_id and bank_installments_enabled connector settings. When both settings are configured, the bank_installments_integration_id will be included in the PSP payload, allowing users to select installments as a payment option in the payment modal for credit card redirects.
• Worldline (ING-EP2, ING-EP7): Add the shouldBeFinishedWhenCapturedSofort connector setting. When enabled, Sofort debit transactions will be marked as successful when the status changes to captured.

Fixed​

• DPO Pay (PAYGA-PYGT): Fix an issue where the transaction status in the adpater could be incorrect after a timeout by the PSP. The platform now polls the status API to ensure the correct transaction status is set.
• Redsys (RED-EP2-BIAPI): Maintain and update the payment service provider's transaction ID from the initial transaction in subsequent transactions.

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.