Skip to main content

7 posts tagged with "PayU"

View All Tags

Gateway — v25.18

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

Gateway Features

Changed

  • Audit Log: Improve audit logs sorting.
  • Risk Profile: Resolve edge-case race condition causing incorrect risk check data calculation.
  • Risk Profile: Update Forter risk engine to use Orders API V3 (v10.1) and Order Status API V2 (v10.1).

Added

  • Post Processing Jobs: Add new job settings page to manage job status, steps, and conflict states. A new permission, postprocessing.job.update-settings, has been added to enable this.

Gateway Adapters

Changed

  • ACI PAYON (PON-EP1-CC): Update provider 3-D Secure flow to support method fingerprinting.
  • Adyen (ADY):
    • Add new data fetcher setting to map Tax Charge to either Service Fee or VAT.
    • Store Auth Code and Scheme Transaction Identifier from postbacks for reuse in subsequent transactions.
  • Adyen (ADY-EP3-VIPPS): Enable partial capture for the Vipps payment method.
  • PayU (PAU-E01-PAE): Add support for the new payment method PagoEfectivo. PagoEfectivo is a Peruvian cash-based online payment service that lets customers generate a payment voucher and settle it in cash at participating banks or retail locations.
  • PayU (PAU-E01-YAPE): Add support for the new payment method Yape. Yape is a Peruvian mobile wallet that lets customers pay merchants or transfer money using their phone number or by scanning a QR code.
  • Simulator: Tweak simulated 3-D Secure challenge page.

Fixed

  • dLocal (DLO): Fix settlement handling to correct amount formatting, ensure fees are deducted from the payout sum, and store fees to their respective transactions.
  • PayPal (PPA): Prevent duplicate fees when receiving multiple callbacks for the same transaction.
  • PXP (PXP): Fix status mapping of state 13 (AuthorisedByProvider) to a successful transaction.

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.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 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 — v24.6

Features

Changed

  • Post Processing Jobs:
    • The Collect Transactions by Uploaded CSV File post-processing job now allows multiple fields (arn, uuid, and adapterTxid) to be mapped. Previously, only the arn field could be mapped.
    • A new setting has been introduced, Cascading ID Mapping. If this option is activated, IXOPAY attempts to locate related transactions for every mapped identifier (in the same order as the fields are mapped in the post-processing job). If a transaction is found, it is added to the post-processing job, while all other identifiers in the CSV are ignored for that transaction.
  • Provider Settlements and Reconciliation: Improved the error message that is displayed when a transaction cannot be found due to a missing reference in the settlement file.
  • UI Navigation: New permissions have been added that determine whether users can access the dashboard (dashboard.show and frontend.dashboard.show). Existing users and roles will automatically receive these permissions. A welcome page is now displayed as the start page for users without access to the dashboard.

Fixed

  • Fee Management: Fixed an issue that meant it was possible to save fees even when the mandatory feeStrategyParameters field did not contain a value.
  • Fee Management: Fixed an issue where the amount was incorrect in retried transactions, as the amount would include previous surcharges if the surcharge was calculated dynamically.
  • Post Processing Jobs: Fixed an issue that prevented more than 1,000 connectors from being assigned to a post-processing job schedule.
  • Provider Settlements and Reconciliation: Fixed an issue that caused the delete button to be displayed for canceled transactions. The button is now only displayed if the status of the settlement is "new".
  • Provider Settlements and Reconciliation: Fixed an issue with resolving transactions by additionalId.
  • Transaction List: Fixed an issue with sorting by card type in the Transaction List.
  • Transaction List: Fixed an issue in the Transaction List filters that would cause no results to be returned if a filter was applied to the first 8 digits of the card number.
  • UI Navigation: Fixed an issue where the red highlighting of missing reconciliations was not applied when switching pages or applying a filter.
  • Virtual Terminal: Fixed an issue with surcharge fee calculations.

Adapters

Changed

  • GoCardless (GOC-EP1): GoCardless settlements now also include payment references.

Fixed

  • Adyen (ADY): Fixed an issue caused by the Izyco settlement data fetcher configuration parameter missing the regular expression for the file name.
  • Braintree (BRA-EP1): Improved the handling of the billing address. If the extra data fields for company, first name or last name are unavailable, the company, first name and last name are taken from the Customer object.
  • checkout.com (CHE-EP1-CC, CHE-EP2-CC):
    • Fixed an issue that would cause the status of a transaction to be set to ERROR if a callback is received that is not mapped in IXOPAY.
    • The following callbacks are now handled:
      • authorization_declined
      • card_verification_declined
      • card_verified
      • authentication_started
      • authentication_approved.
    • Added the mandatory provessingChannelId parameter for the NAS platform.
  • Nexi Group (NETS): Fixed an issue with settlements caused by a missing configuration.
  • PayU (PAU-E01): Fixed an issue that would cause a backend error if the payment_id is missing in the payload during callback processing.
  • Stripe (STRV2): Fixed an issue with Stripe settlements where transactions in IXOPAY were not correctly identified.
  • Volt (VOL): Fixed an issue with retrieving settlements.

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 — v23.13

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.