Skip to main content

6 posts tagged with "PPRO"

View All Tags

Gateway — v26.9

Gateway API

Changed

  • Transaction API: Add adapter name and brand to tracing data (includeTracing).

Added

  • Batch-upload API: Introduce Batch Upload API V2.
    • Support for deregister transactions.
    • A new lenient processing mode that skips invalid rows instead of aborting the batch.
    • A structured JSON result file.
    • Dedicated endpoints for status polling, result download, and batch listing.

Fixed

  • Push API: Fix an issue where the provider was not assigned to transactions.

Gateway Features

Added

  • Customer Profiles: Add the ability to exclude specific stored payment instruments on the payment selection page.
  • Meta connector: Add a new routing rule which allows routing to specific card networks.

Fixed

  • BI Data Source: Fix an issue where network token status changes were not reflected in the BI Data Source.
  • Post Processing Jobs: Fix an issue where the transaction count in the Transactions tab of a post-processing job could be lower than the actual number of transactions.

Gateway Adapters

Changed

  • Adyen (ADY-EP3-CC): Update response mapping documentation for AVS and CVV.
  • Autopay (AUTO): Add rolling reserve line items to settlements, distinguishing between deducted reserve amounts and payout amounts.
  • checkout.com (CHE-EP1-CC,CHE-EP2-CC): Add support for unreferenced refunds.
  • dLocal (DLO-EP1-CC): Add a configuration setting to set a default transaction indicator for register transactions.
  • dLocal (DLO-EP1-NETIN): Add support for the new payment method NetBanking. NetBanking is a popular bank transfer method in India that supports recurring payments, allowing customers to securely authorize a mandate for future subsequent transactions.
  • Klarna (KLW): Add a sendReferenceInCaptures configuration setting to include the transaction UUID in capture requests for reconciliation purposes.
  • PayPal (PPA): Add support for retrieving settlement reports from the sandbox environment when the connector is in test mode.
  • PPRO (PPR-EP1-EPS): Add support for reversal handling.
  • PPRO (PPR-EP1-IDE): Add support for reversal handling.
  • PPRO (PPR-EP1-TWI): Add support for the new payment method TWINT. TWINT is the leading mobile payment method in Switzerland, allowing users to complete transactions instantly either directly in the smartphone app or by scanning a QR code.

Fixed

  • Autopay (AUTO-EP1): Fix register requests in migration flows to inherit the transaction indicator from the original transaction.
  • HUA NAN COMMERCIAL BANK (HNCB-EP1-CCRD): Fix transactions failing due to a transaction reference exceeding the maximum field length.
  • Redsys (RED-EP2-BIZ): Fix an issue where payment cancellations were routed to the error URL instead of the cancel URL.

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, iFrame — v25.14

Gateway Features

Added

  • Provider Settlements and Reconciliation: Add ability to manually upload reconciliation files.

Fixed

  • Post Processing Setting: Fix a bug where setting a provider's adapter to - caused an error.
  • Transaction Processing: Improve handling of follow-up transactions to prevent errors after deregistration.

Gateway Adapters

Changed

  • Adyen (ADY): Improve error mapping to consider the reason value when provided.
  • Adyen (ADY-EP4): Add documentation for referenced and unreferenced Refunds.
  • Certegy (CERTE-EP1-ACH): Fix Register and Refund handling.
  • DPO Pay (PAYGA-PYGT): Add support for Partial Refunds.
  • PPRO (PPR-EP1): Update the endpoint from https://api.girogate.de to https://simpleapi.ppro.com.

Fixed

  • Adyen (ADY-EP3): Fix an issue where extra data was not forwarded for Refunds.
  • Bangkok Bank (BB): Fix handling of negative VAT values for settlements.
  • dLocal (DLO): Fix an issue with parsing settlement files.

iFrame

Added

  • UT iFrame: Export TypeScript types from main entry point for standard importsConfiguration, Authentication, HMACAuthentication, and other key types now available. Resolves issue requiring non-standard import paths from node_modules.

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.21

API

Added

  • Push API: Add transactionSubType to the /chargeback endpoint.

Features

Changed

  • Risk Profile: Add parameters to Count Chargebacks Risk Engine Strategy to include or exclude RDR transactions.

Added

  • Account Updater: Add connector setting Account Updater: Snooze Updates for Status Contact-Cardholder to skip future account updater runs for the response status Contact-Cardholder for up to 36 months.
  • BI Data Source: Add field subType to the BI Data Source enabling better transaction distinction and filtering of RDR transactions.
  • Dashboard: Add a filter for subType to Trend: Compare Chargeback Rate dashboard widget.
  • Post Processing Jobs: Add Transaction Type and Transaction Subtype columns to the exported email of the Send Reports to Merchants post-processing job strategy.
  • Risk Profile: Add Is Credit Card Prepaid and Is Credit Card Reloadable risk rules.
  • Transaction List: Add field subType to the Advanced Filter enabling better transaction distinction and filtering of RDR transactions.

Fixed

  • Transaction Details: Fix Load More button for transaction logs exceeding 100 entries.

Adapters

Changed

  • Bangkok Bank (BB): Add optional PGPPrivateKey and PGPKeyPassPhrase fields to the data fetcher's Extra Data, to support PGP-encrypted settlement file decryption.
  • checkout.com (CHE): Remove the requirement to send customer.bic or customer.extraData.bic fields and the requirement to perform a separate /options getIssuers call.
  • CMI (CMI): Add support for settlement handling.
  • Nuvei (NUV-EP1): Remove the requirement to send customer.email, this is now an optional field.
  • PayTabs (PAYT-EP01): Add connector config Enable iframe mode to support checkout via iFrame.
  • PPRO (PPR-EP1): Add a configuration option for alternative PPRO return mode.
  • Worldpay (WOR-EP1): Add support for chargeback notifications.

Added

  • Fiuu (FIUU-EP1): Add the Fiuu (formerly Razer Merchant Services) adapter with support for debit and refund transactions. Fiuu is Southeast Asia's leading payment gateway, enabling seamless payments for businesses and individuals.
  • JPMorganChase (CHA-EP2): Add the J.P.Morgan Commerce Platform adapter with support for debit, preauthorize, (partial) capture, (partial) refund, and recurring transactions. J.P. Morgan is a leader in financial services, offering solutions to clients in more than 100 countries with one of the most comprehensive global product platforms available.

Fixed

  • KakaoPay (KAKAO-EP1): Add extraData.paymentMethodType field with possible values MONEY or CARD.
  • KCP Mobile, KCP PC (KCPMO-EP1, KCPPC-EP01): Fix live endpoint.
  • PayPal Complete Payments - PPCP (PPCP-EP1):
    • Fix missing prepareCallEndpoint for the multi-method payment connector.
    • Ensure PPCP payment method availability in the multi-method payment connector.
  • SIA (SIA-E01): Fix setting transaction status to error on failed 3DS authentication, enabling follow-up THREEDSAUTHORIZATION2 call.

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.16

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.