7 posts tagged with "Redsys"

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.

Gateway API​

Changed​

• Transaction API: Extend the callbackUrl length for refund requests (Refund) from 255 to 4096 characters.

Added​

• Customer profiles API: Add the fields associatedTokenType and networkTokenStatus to the /api/v3/customerProfiles/:apiKey/getProfile response for payment instruments of type card.

Gateway Features​

Added​

• Transaction Details: Add an Associated Tokens column (Network Token with Status, Google Pay Token, and Apple Pay Token) to the Customer Profile credit card payment instruments in the admin and merchant views.
• User Management: Add a new acl.roles.show permission for a read-only view of roles.

Fixed​

• Transaction List: Fix the advanced transaction list filter for Retrieval Reference Number (RRN).

Gateway Adapters​

Changed​

• EPG Financial Services Limited (EPG-EP01): Allow passing the extraData.ext_client_id parameter for Premium Partner solution participants to link Paylado accounts with player accounts.
• JPMorganChase (CHA): Add support for settlement handling.
• JPMorganChase (CHA-EP2-CC): Adds extraData["card.cardVerificationResult"], extraData["card.cardVerificationResultCode"], and extraData["card.paymentAccountReference"] to the response and callback payloads.
• KakaoPay (KAKAO): Updated default behavior to fetch settlement files from yesterday instead of looking back 30 days on the first fetch.
• PayPal (PPA): Map actual-net-settlement-amount settlement line item for reconciliation.
• Redsys (RED-EP2-BIZ): Add support for the new payment method Bizum. Bizum is a service promoted by Spanish banks that connects customers' current bank accounts by linking them to their cell phone number.
• Worldpay (WOR): Change the chargeback creation date from the webhook receipt date to the date_post provided in the postback request.
• Worldpay (WOR-EP1-CC): Add a recommendation to the adapter documentation to enable the connector setting Postback: Send After Each Notification for online refund notifications.

Added​

• Paymob (PMO-EP2-CCRD): Add the Paymob adapter with support for redirect credit card payments. Paymob (formerly known as WeAccept) is a payment service provider and payment aggregator that empowers businesses to get paid wherever their customers are.

Fixed​

• KCP Mobile (KCPMO-EP1): Fix encoding issue on the Hosted Payment Page.
• Mashreq (MASH): Fixed an issue with postback sharing where transactions were not processed correctly when postback sharing was enabled via the setting Accept postbacks from other connectors (list GUIDs comma-separated).
• PXP (PXP-EP1-INST): Add mapping for payment state 15 to “Transaction Declined” error.

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​

• Account Updater: The information on when a customer's card was last updated only displays the date, not date and time. The documentation has been updated accordingly.

• Meta connector (Multi-method connector): A number of changes have been implemented:

  Routing rules view:

  • Disabled and archived connectors are now only displayed if they are used in the routing rule. If such adapters are used, the adapter is displayed with the "(DISABLED)" prefix.
  • If a connector used in a routing rule is disabled or archived, the rule can no longer be saved. A suitable error message is displayed.

  Connector configuration:

  • When a connector is disabled or archived, the system first checks whether the connector is used in any routing rules. If the connector is in use, a warning is displayed that connectors can only be disabled or archived if they are not used by any routing rules. A list of the routing profiles using the connector is also displayed.

  Meta-connector configuration:

  • When unarchiving a meta-connector, its status is automatically set to disabled.
  • When enabling a meta-connector, the system checks whether the meta-connector uses any disabled or archived connectors. A corresponding message is displayed if the meta-connector cannot be enabled due to it referencing disabled/archived connectors.

Fixed​

• Virtual Terminal: The merchant transaction ID is now a mandatory field in the virtual terminal.

Adapters​

Changed​

• ATOM (an NTT DATA Company) (ATOM-EP1-CC): Added post-processing logs.
• Braintree (BRA-EP2-CC): Added support for chargeback and chargeback reversals for disbursement and fee settlements.
• Redsys (RED):
  • Updated the documentation to include information on the new configuration and parameter mapping.
  • Added a merchant descriptor configuration to DS_MERCHANT_MERCHANTDESCRIPTOR
  • Mapped the description to DS_MERCHANT_MERCHANTDESCRIPTOR.
• Silverflow, Stripe (SIL-SEP-VIS, STRV2-EP1-VIS): Updated the documentation with information that final captures are supported by the adapter.
• Worldline (ING-EP1-CC): Increased the timeout to 60 seconds when retrieving settlement files.

Added​

• CMI (CMI): The payment acquirer CMI has been a trusted partner of Moroccan merchants since 2004. The CMI adapter supports payment via credit card.

Fixed​

• eMerchantPay (EME-EP3-SEP): Fixed a bug which caused partial refunds to be declined by the gateway, even though this transaction type is supported.
• HypYaad (HYP-EP1-CC): Fixed a bug that caused transactions with an amount higher than 999.99 to be ignored in settlements.
• PayPal (PPA, SHO): Fixed an issue that would occur when configuring a data fetcher for either PayPal or Shopify PayPal without the necessary required parameters. The user name and password in the configuration are now also shown as required.
• Worldline (ING-EP5): Updated the way transactions are voided to include additional information on the payment amount and currency. The status handling was also reworked to improve error handling and the accuracy of responses.

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​

• Transaction API: Added cardUpdateStatus and cardUpdatedAt to returnData for cardData responses when account updater is enabled.

Features​

Added​

• Account Updater: The Payment Instruments section of Customer Profiles now shows the Status and Last Update columns for Credit Cards.
• Meta connector: Added support for tokenizing Google Pay and Apple Pay payment information and routing these transactions to PSPs.

Fixed​

• Post Processing Jobs: Fixed an issue with the option to pause the execution of post-processing jobs. Previously, setting the job to wait until a specific time that included seconds meant that the next strategy job was never executed.
• Provider Settlements and Reconciliation: Settlement conflicts are now resolved as a result of the transaction being set to successful.

Adapters​

Changed​

• Adyen (ADY-EP3-CC): Added support for post-processing Adyen settlements and reconciliation via GlobalPayments.

• Braintree (BRA-EP1-BLI): Added support for the Blik payment method. This is a popular bank transfer payment method in Poland.

• Redsys (RED-EP1): Added a new setting for the Redsys Bizum payment method that allows users to include an error URL in the transaction data. If the URL is specified, the system will send this URL if the payment fails, improving error handling and the user experience.

• Worldline (ING-EP5): PostFinancePay is now available as a payment method. The following countries are supported:

  • Switzerland
  • Belgium
  • France
  • Germany
  • Netherlands
  • United Kingdom
  • Additional EU countries

  Supported currencies include CHF and EUR.

Added​

• AllSecure (ALLSE): AllSecure is a global payment service provider that provides tailor-made online payment solutions. The adapter supports credit card payments.
• PayPal Complete Platform (PPCP-EP1-PPE): Added a new PayPal Commerce Platform adapter. The adapter supports:
  • All transactions types using hosted payment pages
  • All transaction types by integrating PayPal directly on the merchant's website
  • PayLater capability
  • PayPal vaulting.

Fixed​

• Adyen (ADY): Fixed an issue where lines marked as a merchant payout were not correctly mapped to the paymentReference field.
• checkout.com (CHE-EP1-IDE, CHE-EP2-IDE): Added BIC support for transactions not involving an IBAN customer.
• Neteller (NET-EP1): Fixed an issue where the transaction status failed to update to ERROR after receiving a postback indicating an error.
• Worldline (ING-EP2-MAS): Fixed an issue with unformatted chargeback amounts. Due to the lack of formatting, the result was increased by a factor of 100.

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.