Skip to main content

9 posts tagged with "PayU"

View All Tags

Gateway — v26.4

Gateway API

Fixed

  • Transaction API: Fix an issue where card data is not returned in the API response if the transaction was processed with a network token.

Gateway Features

Changed

  • Risk Profile: Extend Forter risk engine to support installments.

Added

  • Job Configuration: Add support to export the jobId. Supported for Write Customized Settlement CSV and Write Settlement CSV with Split Transaction Merchant.
  • User Management: Add a Security Center setting to automatically disable users based on an inactivity threshold.

Fixed

  • Network Tokenization: Fix an issue where asynchronous network tokens are stuck in pending state.
  • Post Processing Jobs: Fix an issue where collected transactions without a seller merchant (Marketplace) are not displayed.
  • UI: Fix an issue where the tenant drop-down does not appear on the Global Routing Profile page.

Gateway Adapters

Changed

  • 2C2P (2C2P): Add a new configuration setting to specify the region.
  • dLocal (DLO-EP1-CC): Add a new configuration setting to include the selected number of installments in the callback notification.
  • PayPal Complete Payments - PPCP (PPCP):
    • Add support for the locale parameter to manually override the default language of the payment button.
    • Add a new configuration setting to use the UUID instead of the Merchant Transaction ID for the invoice_id.
  • PayU (PAU): Add support for LATAM settlements for the Report Type Payout Reports.

Added

  • Erste Group (EG): Erste Group is a leading financial services provider in Central and Eastern Europe, headquartered in Austria. It offers retail, corporate, and investment banking services to millions of clients across multiple countries. The group is known for its strong regional presence, digital banking solutions, and commitment to sustainable finance.

Fixed

  • 2C2P (2C2P): Fix the behaviour of the Ignore Scheme Fees setting.
  • Alipay - Ant Group (ANT-EP1-ALIPL): Fix an issue when the optional configuration settlementCurrency is not set.
  • Dimoco (DIM): Fix handling of the reconciliation amount.

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

Gateway Features

Changed

  • Transaction Details: Enable merchant users to view the complete transaction tree for a transaction on the Transaction Details page.

Added

  • Connector Settings: Add a new connector setting Connector custom variables which allows defining custom parameters which can be accessed on the Hosted Payment Page.

Gateway Adapters

Changed

  • Adyen (ADY): Update documentation to include AdyenCheckoutPci for the merchantAdviceCode mapping.
  • Braintree (BRA-EP1-SAT): Add support for the new payment method Satispay. Satispay is a popular Italian mobile e-wallet that allows customers to pay securely online directly from their linked bank accounts using a smartphone app.
  • dLocal (DLO-EP1): Add support for the new withholding tax column (WHT) in settlement files.
  • JPMorganChase (CHA):
    • Update amount fields to use raw, non-aggregated values.
    • Remove chargeback adjustments from settlement reports.
  • PayU (PAU-EP1): Add support for Payout Report settlement retrieval with the new Report Type setting.

Fixed

  • 2C2P (2C2P-EP1): Fix settlement retrieval to prevent duplicates.
  • Adyen (ADY-EP3-RIV): Fix missing customer data.
  • HDFC CCAvenue (CCAV):
    • Fix response handling.
    • Fix refunds for captures.
  • Klarna (KLW): Fix VAT and fee calculations for settlements.
  • Paymob (PMO):
    • Add handling to properly cancel transactions when they are abandoned by the user.
    • Fix error mapping 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 — 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.