Skip to main content

11 posts tagged with "Transaction Details"

View All Tags

Gateway — v25.11

Gateway Features

Added

  • Provider Settlements: Map the chargeback reason code from the settlement file to the chargeback description field if the reason code is present.
  • Transaction Details: Add checkbox to apply merchant metadata (merchantMetaData) from the initial transaction during manual capture (enabled by default).

Fixed

  • API Testing: Fix handling of nested extra data in the Simulator adapter.
  • Connector Settings: Fix postback sending for retry transactions when the connector setting Postback: Send on PENDING status is enabled.

Gateway Adapters

Changed

  • Adyen (ADY): Add info-net-credit and info-net-debit line item types to differentiate debit and credit for invoice deductions in settlements.
  • Adyen (ADY-EP4): Add support for Register.

Fixed

  • Adyen (ADY-EP3): Improve handling for invalid notifications.

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: 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.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.3

Gateway API

Added

  • Transaction API: Add the includeTracing parameter for Status API and Transaction API for debit & preauthorize requests, enabling transaction routing and cascading details in the Status API response and Transaction API callbacks.

Gateway Features

Changed

  • Audit Log: Update the User-Management report to reflect the selected user type (userType), include user descriptions (description), the merchant column (merchant) for relevant user types.

Added

  • Connector Settings: Add a new connector setting: Expire transaction with a given status after given minutes, allowing configuration of multiple statuses and expiration times. This replaces the need for separate settings for pending and automatic transaction expirations.
  • Transaction Details:
    • Allow adding custom data values to manual refunds and captures, configurable in tenant settings.
    • Introduce a new permission, frontend.transaction.add-extradata-to-manual-capture-refund, to manage access to this feature.
  • Transaction List: Restore the Copy from Standard Filter button in the advanced search.
  • User Management: Add a new field, Description, to the base data for all users, visible in the Create New User, Edit User, and User Overview views.

Removed

  • Connector Settings: Deprecate the connector settings Expires pending transactions after given minutes and Transactions: Expire automatically after (x) minutes, as their functionality is now covered by the new setting that supports expiring transactions based on specific statuses.

Gateway Adapters

Changed

  • EquensWorldline (EQW): Add ARN (Acquirer Reference Number) to settlement when parsing reconciliations.
  • JPMorganChase (CHA-EP2-CC): Improve documentation for new extraData fields (extraData["card.cardVerificationResult"], extraData["card.cardVerificationResultCode"], and extraData["card.paymentAccountReference"]).

Fixed

  • dLocal (DLO-EP1): Correct the payout country restrictions link in the adapter documentation.

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.