8 posts tagged with "Provider Settlements"

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: 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​

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

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