12 posts tagged with "Redsys"

Gateway Features​

Added​

• BI Data Source: Improve the management of BDS settings by allowing the definition of default profiles at the Merchant and Connector levels for more consistent and simplified configurations.
• Job Configuration: Add support for the customerProfileIdentification and customerProfileGuid fields in export strategies (CSV, XLSX, XLSX v2).
• Job Configuration: Add a new line item grouping card Country (buyer Country as a fallback) for the Aggregate Transaction Values To Job Line Items strategy.

Fixed​

• Audit Log: Fix Audit Log Export which sometimes produced duplicate or incomplete export results.
• Risk Profile: Adjust Forter risk engine to validate ECI values to avoid formatting errors.
• Transaction Details: Fix Resend postback functionality.
• Transaction Processing: Add missing support for Auto-Capture for failover transactions.
• UI Navigation: Fix an issue in the customer profile view when loading a large number of profiles.

Gateway Adapters​

Changed​

• Stripe (STRV2): Add support to match transactions with a latest_charge for post processing purposes.

Added​

• Kueski (KUE-EP1-KP): Kueski is a leading provider of consumer credit in Mexico, enabling flexible "Buy Now, Pay Later" installment-based payments for customers without traditional credit cards. The new adapter supports the Kueski Pay payment method for Debit and Refund transaction types.

Fixed​

• Adyen (ADY): Fix handling of settlement files with unexpected file names.
• Dimoco (DIM): Fix reconciliation parsing of AUT/TRX fields and fees.
• Redsys (RED-EP2-BIZ): Improve error handling.

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​

• Data Export: Improve the stability and reliability of the Data Export.

Added​

• Hosted Payment Pages: Add support for installments on the Hosted Payment Page. This feature is currently available for dLocal (DLO-EP1-CC) and Adyen (ADY-EP3-CC).
• Provider Settlements and Reconciliation: Add a setting to choose whether the receipt date or the settlement date (default) should be used for unknown transactions.

Fixed​

• Callback: Fix an issue where the schedule status (scheduleData.scheduleStatus) in callback notifications was incorrect for scheduled transactions.
• Risk Profile: Fix the Forter risk check engine script (on the HPP) to use the correct version.

Gateway Adapters​

Changed​

• dLocal (DLO): Add a setting to configure how TAX_LOCAL_AMOUNT is mapped during settlement handling - either as Scheme Fee or VAT.
• dLocal (DLO-EP1-UPI): Add support for UPI. UPI is a real-time payment system in India. This integration supports the eMandate flow, enabling the processing of recurring transactions.
• EquensWorldline (EQW-EP1-CC): Add support for network tokens.
• JPMorganChase (CHA):
  • Improve the report by displaying fees and sale amounts correctly on the same line.
  • Update the column Settled Conveyed Code to Conveyed Settled Code in the settlement retrieval file.
• Nuvei (NUV-EP1-NEQ): Add support for Nequi. Nequi is a popular mobile payment solution in Colombia that allows users to send and receive money, supporting both debit and payout transactions.
• Paynetics (PNE-EP1-CC): Add support for network tokens.

Added​

• HDFC CCAvenue (CCAV): HDFC CCAvenue is a leading payment gateway in India, enabling secure and reliable Credit Card payments via redirect. The new adapter supports Debit, Preauthorize, Capture, Void, and Refund transaction types.
• VoltUnifiedGlobalPayments (VUGP-EP1-BTR): Volt Unified Global Payments is a next-generation digital payments gateway, enabling PSD2 bank-direct payment services in Europe, the UK, and Australia. The new adapter supports Bank Transfer payments for Debit and Refund transaction types.

Fixed​

• Adyen (ADY): Add error handling for unsupported currencies.
• JPMorganChase (CHA): Fix various issues in settlement parsing to ensure data is processed correctly.
• Nuvei (NUV-EP1): Fix identifier handling to ensure refunds work correctly.
• Redsys (RED-EP1-CC): Fix the use of the reference scheme transaction identifier.
• Stripe (STRV2-EP1): Improve reconciliation handling to prevent conflicts and issues with unknown transactions.
• Stripe (STRV2-EP3): Improve reconciliation handling to prevent conflicts and issues with unknown 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.

Gateway API​

Fixed​

• BI Data Source API: Fix wrong HTTP response header for the BI Data Source API. The response header now returns a proper Content-type: application/json; charset=UTF-8 header.

Gateway Features​

Changed​

• Connector settings: Rename the Pay By Link tab in connector settings to Templates. This tab now consolidates email template configurations, including those for Pay By Link and the new general transaction success confirmations.

Added​

• Connector settings: Enhance transaction confirmation emails: You can now enable automated emails for merchants and/or customers upon any successful transaction, extending beyond Pay By Link. Control this using the new settings Send Success Mail to customer and Send Success Mail to merchant, located in the Templates tab (availability of this feature is subject to user permissions).

Fixed​

• Dashboard: Fix dashboard visualization issue when no time range is provided.
• Risk Profile: Fix a column sorting issue for the representment table.

Gateway Adapters​

Changed​

• Cybersource (CYS-EP1): Add option to provide a reconciliation ID via extra data.
• DPO Pay (PAYGA-PYGT): Add status retrieval to determine actual status of failed transactions.
• Redsys (RED-EP2): Add mapping for the Auth-Code when available.

Fixed​

• Adyen (ADY-EP3-PAYPA): Fix postback handling issue.
• dLocal (DLO): Add handling for missing customer 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.

Gateway Features​

Changed​

• Transaction Details: Extend the Create Manual Chargeback and Create Manual Chargeback Reversal action to allow setting the settlement amount, settlement currency and settlement date.

Added​

• Transaction Details: Add support to manually create a second chargeback.

Fixed​

• Connector Configuration: Fix an issue for the connector setting Accept postbacks from other connectors where postbacks were processed through the wrong connector.
• Provider Settlements and Reconciliation: Fix an issue handling settlements for transactions sharing the same ARN.
• Transaction Details: Fix incorrect status display for subsequent transactions on the transaction detail page.

Gateway Adapters​

Changed​

• Adyen (ADY-EP3-PAYPA): Add support for the new payment method PayPay. PayPay is a Japanese e-wallet allowing customers to either pay directly in the app or by scanning a QR code.
• Adyen (ADY-EP4-CC): Add support for Refund and Payout.
• DPO Pay (PAYGA-PYGT-CC): Add status retrieval for transaction communication errors (previously only for timeouts).
• PPRO (PPR-EP1-TRU): Map the customer.email parameter to PPRO's useremail request parameter.
• Redsys (RED-EP2): Add a new configuration to enable or disable sending Merchant Card-on-File transaction indicators for register transactions (DS_MERCHANT_COF_TYPE = R, DS_MERCHANT_COF_INI = S).
• Worldline (ING-EP2-IDE): Add documentation for the payment method iDeal.

Fixed​

• American Express (AMX-EP1): Fix chargeback settlement amounts where wrongly saved negative values were leading to conflicts.
• PayU (PAU-E01-MAS): Fix an issue when using customer profile tokens for subsequent transactions.
• PPRO (PPR): Update the postback validation to support SHA-256 hashing.

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.