5 posts tagged with "Transaction Details"

API​

Changed​

• Provisioning API: Added the field eventNotificationUrl to merchant entities.
• Transaction API: Added field transactionSubType to the status API calls and to transaction callback bodys.

Features​

Changed​

• BIN Lookup: Updated the BIN data source.
• Pay-by-Link: Introduced a new pay-by-link-enabled permission to allow control over which API users can trigger pay-by-link transaction., The permission defaults to enabled for existing API users who have previously used pay-by-link, and disabled for all others.
• Transaction Processing: Enabled sending transaction descriptions to upstream PSPs for void and capture transaction types.

Added​

• Account Updater (Network Tokenization): Added a notification service that sends callbacks to shared merchants —those sharing a customer profile container— whenever a transaction is updated through the account updater or NTS Updates.

• Fee Management: Added a new field Transaction Subtype to Fee Constraints, including it in fee calculations; subtypes can be Chargeback Resolved, Chargeback Reversal Resolved, or - any - for no specific preference. Fee items will now be grouped by transaction type and subtype (if present).

• Job Configuration: Introduced transaction subtype filtering to the following Collecting Post Processing Job steps:

  • Collect Transactions from Related Batch
  • Collect All Transactions within a Period
  • Collect Transactions from Provider Settlements (created/settled within a period)
  • Collect Transactions by Settlement State

  Introduced transaction subtype filtering and grouping to the following Processing Post Processing Job steps:

  • Aggregate Transaction Fees to Job Line Items
  • Aggregate Transaction Values to Job Line Items
  • Calculate Rolling Reserve for Merchant
  • Count Transaction Value to Job Line Items.

• Post Processing Jobs: Added support for filtering via the transaction subtype in the transaction view for Post Processing Jobs.

• Post Processing Jobs: Added transaction subType column as possible export value for the following Post Processing Job steps

  • Export Transactions to CSV
  • Export Transactions to XLSX
  • Export Transactions to XLSX (Version 2)
  • Write customized Settlement CSV.

• Provider Settlements and Reconciliation: Added support for filtering via the transaction subtype in the Transactions in Batch and Conflicted Transactions views for Provider Settlements.

• Transaction Details & Post Processing Jobs & Provider Settlements and Reconciliation: Added subtype to the transaction Details view.

• Transaction Processing: Added a subtype field to transactions for rapid dispute resolution, with available subtypes "chargeback resolved" and "chargeback-reversal resolved".

Fixed​

• Post Processing Setting: Set a default transaction type when creating transactions derived from settlements without a transaction type.
• Transaction Details: Fixed an issue where displaying Risk Data on the Transaction Detail page could cause an error in certain cases.
• Virtual terminal: Fixed the virtual terminal view for merchant users.

Adapters​

Changed​

• Amazon Payment Services (AMAZO-EP1): Added clear error messages for transactions when errors are triggered by incoming postbacks.
• MultiSafepay (MUL-EP1): Added Content-Type: application/json to requests sent to the PSP to ensure the PSP can look-up the requests in their logs.
• Valitor (VALIT): Added support for RDR.

Added​

• Bangkok Bank (BB): Added the Bangkok Bank post processing adapter with support for settlement handling.

Fixed​

• Global Payments (GBP): Resolved a bug in the parsing of Global Payments settlements.
• GoCardless (GOC-EP1): Removed mandate callback handling for cases where the initial registration was already successful.

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​

Fixed​

• Transaction Details: Additional headers for callbacks including Content-Type, Accept and User-Agent are now added to the postback transaction logs in the transaction details view when the postback:send-test-plain-header or postback:send-useragent-header are set in the connector settings.
• Transaction Export: Fixed an issue with the export of transaction data for merchants with mult-merchant access.
• UI Navigation: The Croatian and Slovenian translations have been updated.

Adapters​

Changed​

• Braintree (BRA-EP2-CC): The connector configuration has been updated, see the documentation for more information.
• Braintree (BRA-EP1): The additionalId1 field is now mapped to the descriptor name instead of the descriptor URL.
• Cybersource (CYS-EP1-CC): Updated the description of auxiliary data in the documentation.
• DPO Pay (PAYGA-PYGT): The DPO Pay adapter now supports preauthorize, capture and void transactions for credit cards.
• Worldpay (WOR-EP1-CC): The API documentation has been updated to include information on which parameters are mandatory for the Worldpay WPG PCI adapter.

Fixed​

• ATOM (an NTT DATA Company) (ATOM-EP1-CC): Fixed an error with retrieving the settlement that was introduced in an earlier change.
• Braintree (BRA): The createdAt timestamp supplied in Braintree's postback is now used as the timestamp for PayPal chargebacks.
• DPO Pay (PAYGA): Fixed an issue that prevented settlements from being processed due to an invalid date format.
• EPG Financial Services Limited (EPG-EP01-PAYLA): If the additionalId1 field is not provided as part of the payout request, the alias of the referenced debit transaction is used as a fallback option.
• GoCardless (GOC-EP1): Fixed an issue with the server-to-server flow caused by a missing parameter.
• Valitor (VALIT-EP1-CC): Fixed an issue with settlements caused by duplicate transaction lifecycle IDs.

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.

Features​

Changed​

• API: The Transaction API has been updated to allow pay-by-link transactions to be cancelled with an API call using the URL supplied in the initial response.

Added​

• Account Updater: A new view has been added to the Account Updater, showing all merchants for the selected tenant, and permissions can now be set to view the enrollment status of merchants in the overview.

Fixed​

• Fee Management: Fixed an issue that prevented fees from being configured if no fee set had been added for the connector.
• Post Processing: Fixed an issue that caused the post-processing job to fail when settlement reports were uploaded without a header.
• Transaction Details: Fixed an issue where the payByLink and the surcharge transaction data was not copied to the new retry transaction when retrying a transaction.
• Virtual Terminal: Added support for the Montenegrin language to the virtual terminal.

Adapters​

Changed​

• Bank of America (BOFA-EP1-ACH): Added AchData return data for API results, status responses and callbacks.
• Bank of America (BOFA-EP1-ACH): Added support for register and follow up debit transactions.
• MultiSafepay (MUL): Added a new customer extraData parameter, locale, which maps directly to the MultisafePay locale parameter.
• Worldline (ING): Added support for refund transactions in 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.

Features​

Changed​

• Connector Settings: Extend connector setting "Set Customer Identification if empty" with the "Pseudo Random" option, allowing for the generation of a random ID to be assigned as the customer identification when left empty.
• Multi-method connector: Redirect the customer to the appropriate URL when a redirect payment method is used without a payment template, preventing the "Unexpected redirect to payment page" error.
• Virtual Terminal: The delayed capture interval can be set in days to add more convenience for virtual terminal users.

Added​

• Fee Management: Add GST fee support in the fee engine. Configure and map the GST (a percentage of the surcharge fee) as a fee entity and include it in a connector's fee set.
• Post Processing Setting: Enable the "Reconciliation: Use reference merchant tx id for unknown transactions" setting for remote deregister and remote refund transactions.
• Job Configuration: Introduce the ability to split jobs by cardType.
• Provider Settlements and Reconciliation: Add the bank reference number as a new column in the "Recent Settlements" and "All Settlements" view, along with a filter option for bank reference number in the "All Settlements" view.
• User Management: Simplify admin user management by adding a new filter option in the "Tenant User" view to include sub-tenant users in your filter results.

Fixed​

• Alerts: Fix an issue causing resolved alerts to remain visible to users.
• Job Configuration: Fix job configuration setting "Display a negative total sum of the initial transaction amount plus fees" in order to handle negative net settlement refund amount.
• Risk Profile: Allow users with the permission riskcheck.riskruleset.edit to edit the score card for a risk profile, resolving the limitation of requiring riskcheck.riskruleset.archive permission.
• Transaction Details: Hide capture button for pre-authorize transactions that are already fully captured.

Adapters​

Changed​

• Adyen (Settlement): Add support for skipped settlement files.
• Adyen (ADY-EP3): Add metadata merchantTxId and additionalId1 to debit and preauthorize transactions.
• Bank of America (BOFA-EP1-ACH): Remove the redundant connector setting initialTransactionState.
• Braintree (BRA-EP2-AMX, BRA-EP2-CUP, BRA-EP2-DIN, BRA-EP2-DIS, BRA-EP2-JCB, BRA-EP2-MAS, and BRA-EP2-VIS): Add support for parsing the new disbursement settlement file format.
• Six (Settlement): Add configuration options for SFTP host and root directory.
• Straight2Bank Pay (STRAI-E01): Add a new connector configuration field, pspid, to enable PSP id overwriting for cases where clients receive this parameter from the PSP.
• Straight2Bank Pay (STRAI-E01): Add new transactional fee types, markup and markup_vat, to the SCB settlement handling.
• Valitor (VALIT-EP1): Improve handling of Valitor settlements for transactions with non-unique adapter transaction IDs or lifecycle transaction IDs.
• WorldPay (WOR-EP1-CAB): Add support for CB (Carte Bleu and Carte Bancaire).
• Worldline (ING-EP6): Improve settlement data handling by implementing the configuration option "Customized REGEX Pattern" in the Settlement Data Fetcher for better distinction.
• eMerchantPay (EME-EP3): Add the orgTerminal parameter received by postback to transactions for cases of missing responses due to time-outs.

Added​

• Adyen (ADY-EP3-AMX, ADY-EP3-CAB, ADY-EP3-CAR, ADY-EP3-CUP, ADY-EP3-DIN, ADY-EP3-DIS, ADY-EP3-ELO, ADY-EP3-HIC, ADY-EP3-JCB, ADY-EP3-MAS, ADY-EP3-TRO, and ADY-EP3-VIS): Add support for the incremental authorization transaction type in the Adyen Checkout service platform.
• PayU (PAU-E01): Added PayU Colombia.

Fixed​

• ATOM (ATOM-EP1-AMX, ATOM-EP1-DIN, ATOM-EP1-JCB, ATOM-EP1-MAS, ATOM-EP1-RUPAY, and ATOM-EP1-VIS): Fix settlement fee mapping to correct the net settlement amount calculation.
• First Atlantic Commerce (FAC-EP1-MAS and FAC-EP1-VIS): Refine adapter integration in combination with customer profiles to support follow-up transactions.
• Nuvei (NUV-EP1-AMX, NUV-EP1-CUP, NUV-EP1-DIN, NUV-EP1-MAS, and NUV-EP1-VIS): Fix issue causing follow-up void transactions to fail when the initial transactions experienced timeouts, that were later marked successful.
• PPRO (PPR-EP1): Ensure accurate handling of separate settlement files by eliminating unexpected NULL value for netSettlementAmount when only submitting a fee for a transaction without a net settlement amount.
• Worldline (ING-EP2-BTR): Fix failed refunds by adding the missing accountHolderName parameter.
• Worldline (ING-EP2): Improve refund processing by adding the iban parameter to the refund payload and enabling refund 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.