4 posts tagged with "Fee Management"

Features​

Changed​

• Post Processing Jobs:
  • The Collect Transactions by Uploaded CSV File post-processing job now allows multiple fields (arn, uuid, and adapterTxid) to be mapped. Previously, only the arn field could be mapped.
  • A new setting has been introduced, Cascading ID Mapping. If this option is activated, IXOPAY attempts to locate related transactions for every mapped identifier (in the same order as the fields are mapped in the post-processing job). If a transaction is found, it is added to the post-processing job, while all other identifiers in the CSV are ignored for that transaction.
• Provider Settlements: Improved the error message that is displayed when a transaction cannot be found due to a missing reference in the settlement file.
• UI Navigation: New permissions have been added that determine whether users can access the dashboard (dashboard.show and frontend.dashboard.show). Existing users and roles will automatically receive these permissions. A welcome page is now displayed as the start page for users without access to the dashboard.

Fixed​

• Fee Management: Fixed an issue that meant it was possible to save fees even when the mandatory feeStrategyParameters field did not contain a value.
• Fee Management: Fixed an issue where the amount was incorrect in retried transactions, as the amount would include previous surcharges if the surcharge was calculated dynamically.
• Post Processing Jobs: Fixed an issue that prevented more than 1,000 connectors from being assigned to a post-processing job schedule.
• Provider Settlements: Fixed an issue that caused the delete button to be displayed for canceled transactions. The button is now only displayed if the status of the settlement is "new".
• Provider Settlements: Fixed an issue with resolving transactions by additionalId.
• Transaction List: Fixed an issue with sorting by card type in the Transaction List.
• Transaction List: Fixed an issue in the Transaction List filters that would cause no results to be returned if a filter was applied to the first 8 digits of the card number.
• UI Navigation: Fixed an issue where the red highlighting of missing reconciliations was not applied when switching pages or applying a filter.
• Virtual Terminal: Fixed an issue with surcharge fee calculations.

Adapters​

Changed​

• GoCardless (GOC-EP1): GoCardless settlements now also include payment references.

Fixed​

• Adyen (ADY): Fixed an issue caused by the Izyco settlement data fetcher configuration parameter missing the regular expression for the file name.
• Braintree (BRA-EP1): Improved the handling of the billing address. If the extra data fields for company, first name or last name are unavailable, the company, first name and last name are taken from the Customer object.
• checkout.com (CHE-EP1-CC, CHE-EP2-CC):
  • Fixed an issue that would cause the status of a transaction to be set to ERROR if a callback is received that is not mapped in IXOPAY.
  • The following callbacks are now handled:
    • authorization_declined
    • card_verification_declined
    • card_verified
    • authentication_started
    • authentication_approved.
  • Added the mandatory provessingChannelId parameter for the NAS platform.
• Nexi Group (NETS): Fixed an issue with settlements caused by a missing configuration.
• PayU (PAU-E01): Fixed an issue that would cause a backend error if the payment_id is missing in the payload during callback processing.
• Stripe (STRV2): Fixed an issue with Stripe settlements where transactions in IXOPAY were not correctly identified.
• Volt (VOL): Fixed an issue with retrieving 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​

• UI Navigation:
  • If the user only has access to a single connector, it is now automatically selected in the virtual terminal.
  • The last selected connector is stored locally to prevent having to re-select it for future transactions.

Added​

• BI Data Source: Scheme IDs are now available for data exports and post-processing.
• Connector Configuration: Added a new project setting, Manipulation: Field Operation that can be used to manipulate data at the connector level prior to sending the data to the PSP. It is currently possible to truncate the data after a defined number of characters using this option. More operations will be added in the future.
• Fee Management: Added the ability to specify the customer's billing state for fees.
• UI Navigation: Added information on the deployed version to both the gateway and documentation.

Fixed​

• Fee Management: Fixed an issue that would result in an error if no target fee set has been specified and the source fee set is assigned to a sub-tenant.
• UI Navigation: Fixed an issue that prevented archived jobs from being restored when in the table view.
• Virtual Terminal: Fixed an error that could occur when calculating surcharges if no credit card number has been entered.

Adapters​

Changed​

• American Express (AMX-EP1-AMX): Added support for Apple Pay.
• China UMS (UMS-EP1): Added the optional expireTime parameter to the payload. The value of this parameter is taken from the extraData field. If the parameter is not provided there, it is taken from the project settings.
• Cybersource (CYS-EP1-CC): The forwardedAcquirerCode field is now available for postback notifications.
• HypYaad (HYP-EP1-CC): Added support for settlements in CSV format and stored on an SFTP server.
• Klarna (KLW-EP1): The customer.birthDate field has been changed from required to optional.
• PXP (PXP-EP1-CC): The SchemeTransactionIdentifier, SchemeSettlementDate and DinersRetrievalReferenceNumber in callbacks are now stored for use in recurring transactions.
• SIA (SIA-E01): Added support for void and partial captures.

Added​

• Paymee (PAYME-EP1-CCRD): Paymee is a Tunisian payment gateway that accepts credit card payments via a redirect link.
• Sampath Bank (SAMPA-SVNP1-BTR): Sampath is a secure Sri Lankan online payment platform. The adapter supports bank transfers.

Fixed​

• Adyen (ADY):
  • When submitting a transaction using a hosted payment page, clicking on the back button caused the transaction to be resubmitted. This caused two transactions to be sent to the PSP, but IXOPAY only counts this as a single transaction. The duplicate transaction is automatically closed by the PSP, which can overwrite the correct transaction ID of the transaction in IXOPAY.
  • Fixed an issue with settlement notifications that caused settlements to be ignored.
• Amazon Payment Services (AMAZO):
  • A new option has been added that supports SHA-512 alongside the previously supported SHA-256 encryption. This setting should be configured in IXOPAY to match the one configured in the Amazon settings.
  • Fixed an issue generating settlement reports that would only occur when an existing settlement report was re-generated.
• China UMS (UMS): Fixed an issue that prevented the status of pending transactions from being polled correctly.
• China UMS (UMS-EP1): A refund order ID has been added, which now allows multiple refunds.
• Klarna (KLW-EP1): Fixed a number of issues that could occur in cases where the customer's birthdate is missing.
• NMI (NMI-EP1): Fixed an issue where a type error would occur if no related transaction is present and no extra data is set for a credit card connector. The expected data type is an array; if no data is available, an empty array is now used.
• Worldline (ING-EP6): Fixed an issue that could cause successful refunds to remain stuck in a pending state.

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