Skip to main content

9 posts tagged with "Redsys"

View All Tags

Gateway — v25.9

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: 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 — v25.7

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.

Gateway — v25.4

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 — v25.2

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.

Gateway — v24.11

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.