5 posts tagged with "Redsys"

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.

API​

Fixed​

• Provisioning API: Fixed an issue with the Provisioning API that would prevent the creation of vault connectors under specific circumstances.

Features​

Changed​

• Fee Engine: Changed the behavior for configuring GST fees to reflect the Surcharge dependencies.

Added​

• 3DS: The highest-supported 3DS version is now used where possible (i.e. 3DS v2.2.0 is used instead of v2.1.0). For more details, see 3DS 2.1.0 EOL and Changes to 3DS in IXOPAY.
• Connector Settings: A new connector setting has been added (Postback/Status: Include isAFT in postback/status response) that includes information on whether AFT was performed using this transaction.
• Post Processing: Added the ability to check whether data fetchers are set up correctly after adding or editing the data fetcher (currently only supported with the SepaExpress v1 settlement data fetcher). Results are shown in the data fetcher edit view.
• Risk Profile: Added a filter check for all transactions with a payment instrument where the doNotResubmit flag is set for the Count of transactions using same payment instrument risk rule. Added the transaction's error status (error_adapter, error_internal, cancelled, invalid) to the transaction's status selection for the Count of transactions using same payment instrument risk rule.
• Translation: Added Croatian and Slovenian to the merchant admin interface.

Fixed​

• 3DS: When external 3DS solutions are used, the values are no longer included in the postback, as IXOPAY can neither guarantee they are correct nor complete.
• Customer profiles: Fixed an issue that resulted in an incorrect wallet reference ID being entered in customer profiles.
• Multi-method connector: Fixed an issue relating to the retrieval of customer profiles when used in combination with multi-method connector.
• Search: Fixed an issue that prevented the advanced search filters from working with certain adapters.
• Transaction List: The URL included in the transaction tree on the transactions details page not link to the transactions view.
• Transactions: Fixed an issue where sending an amount without specifying a currency would set the amount to 0 for void transactions. This resulted in a full void instead of a partial void.
• UI: Fixed the tooltips in the screens used to edit connectors.
• UI: Fixed the responsive styling for the 3DS configuration, making values easier to see.

Adapters​

Changed​

• 2C2P (2C2P, 2C2P-EP1-CC): Added the option to ignore scheme fees to the settlement data fetcher configuration.
• Braintree (BRA-EP2-CC): Added support for a new disbursement file.
• Braintree (BRA-EP2-CC): The Braintree adapter now supports the new settlement file format for Myanmar.
• Checkout.com (CHE-EP1): Added the ability to configure a private key for the Checkout.com settlement data fetcher.
• DPO Pay (PAYGA-PYGT-CC): Added a new Private key parameter that can be configured at the connector level for SFTP servers.
• EquensWorldline (EQW-EP2): Changed from v2 of the API to the new v3 API.
• Mastercard Payment Gateway Services (MPG-EP1-CC): Added support for Westpac settlement file handling.
• Trustly (TRU-EP1): The response status can now be configured and failed payouts are set to FAILED.

Added​

• Straight2Bank (STRAI-E01-MPESA): The Straight2Bank adapter now supports M-Pesa as a payment method.

Fixed​

• American Express (AMX-EP1-AMX): Fixed the handling of chargebacks and chargeback reversals in settlements for American Express.
• Bank of America (BOFA-EP1-ACH): Fixed an issue that caused export errors due to missing mandatory data.
• Bank of America (BOFA-EP1-ACH): Fixed an error regarding the export of routing number extra data in the NACHA export for Bank of America.
• DOKU (DOKU, DOKU-EP01): Added support for refund transactions ini DOKU settlements.
• DOKU (DOKU, DOKU-EP01): Fixed the mapping of settlement fees and the handling of settlement amounts for the DOKU adapter.
• DPO Pay (PAYGA-PYGT): The DPO settlement parser has been updated to handle the new CSV structure of the settlement files.
• DPO Pay (PAYGA-PYG): Fixed the SFTP login to include the mandatory private key.
• Mashreq (MASH-EP01-CCRD): The default currency for the Mashreq adapter has been changed to QAR.
• PAYONE (PASIX-EP1-CC): Updated the configration for Six settlements to allow a customer-specific key to be entered.
• Redsys (RED-EP2-BIZ): Added support for HMAC_SHA256_V1 as a signature version for merchant integrations.
• Straight2Bank (STRAI-E01): Fixed the handling of refund settlements for Straight2Bank.
• Trustly (TRU-EP1): Fixed the handling of Trustly credit notification events for payouts to update the status to error and prevent chargebacks from being created.
• Volt (VOL-EP1): The bearer token status was re-added to the status request header after it was inadvertently removed.
• Volt (VOL-EP1): Updated the handling of Volt settlement files.
• Worldline (ING-EP2): Fixed a bug regarding the handling of webhooks.
• Worldpay (WOR-EP1): Fixed an issue that caused the settlement data fetcher to retrieve multiple settlements if the same settlement file was uploaded more than once.

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​

Added​

• Post Processing Jobs: Added a new configuration option in the job configuration Processing Step: Copy Line Items from related batch - Do not aggregate line items with the same name that allows two line items with the same name.
• Provider Settlements and Reconciliation: Added a new Provider Setting - Reconciliation: Create Provider Settlement with Conflict Log to handle settlements provided via reconciliation (e.g. PayPal) in cases where the transaction is missing or unknown.
• UI Navigation: The Customer Profiles and Account Updater have been moved to the Tokenization menu.

Adapters​

Changed​

• checkout.com (CHE-EP1): Aggregated payout information is now represented as line items in settlements. This includes interchange fees, scheme and network fees, provider fees, gateway fees and chargeback fees.
• DPO Pay (PAYGA-PYGT-PMR): Updated the parser to handle the updated structure in newer settlement files.
• eMerchantPay (EME-EP3): Removed the check that data has been entered in mandatory fields in EMPGenesis, as these mandatory fields can be disabled for the merchant by the PSP.

Added​

• Braintree (BRA-EP1-PPE): Added support for additional data (STC, AID, BN) required by Braintree for airlines and travel merchants when using PayPal as the payment method.
• Braintree (BRA-EP1-PPE): Added support for tenant-specific BN code which are included with pre-authorization and debit transactions.
• Braintree (BRA-EP2-CC): Added support for level 2/3 data for Visa and Mastercard transactions via Braintree.
• Mashreq (MASH-EP01-CCRD): Added a new adapter for Mashreq. Mashreq a leading financial institutions in the UAE that provides banking and financial services. The adapter supports credit card transactions and settlements.
• MultiSafepay (MUL-EP1): Added support for reconciliation and settlements for the Multisafepay adapter.
• PayPal (PPA-EP1-PPE): Wallet data (first name and last name) is now exposed under Additional Info for payouts and debits.
• Worldpay (ING-EP2): Added the option to configure an SFTP host and SFTP private key with optional SFTP passphrase instead of an SFTP password.

Fixed​

• BDO (BDO-EP1-GCASH): Risk check are now correctly applied to the BDO adapter.
• DPO Pay (PAYGA-PYGT-CC): Added a check for a mandatory description in refunds.
• PayPal (PPA-EP1-PPE): Fixed an issue handling the refund amount in partial refunds received via postback.
• PayU (PAU-E01-CC): Implemented a method for tokenizing cards using debit and refund transaction for Colombia, as authorization and register transactions are not supported.
• Redsys (RED-EP1-CC): Fixed an issue with the key length in the paramsKey extraData parameter.
• Volt (VOL-EP1): Fixed error handling during Volt settlement notification handling.
• Volt (VOL-EP1): By default the full list of banks is now retrieved for Volt. A subset of banks can be retrieved using parameters.page and parameters.limit.
• Worldline (ING-EP3-CC): Fixed Worldline Ogone TWINT settlement refund fee 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.