9 posts tagged with "Fee Management"

Gateway API​

Added​

• Transaction API: Add the schemeLifecycleIdentifier and referenceSchemeLifecycleIdentifier parameters to support transaction lifecycle mandates (e.g., Mastercard TLID).

Fixed​

• Push API: Fix an issue handling an empty firstSixDigits field.

Gateway Features​

Changed​

• 3-D Secure: Add scheme logos (Visa Secure, Mastercard Identity Check, American Express SafeKey, Discover ProtectBuy, and CB FAST'R) to the 3D Secure device fingerprinting loading screen.
• Connector Settings: Allow dashes in the Target Field for the Field Expression Language connector setting.
• Meta connector: Extend the CreditcardType routing rule to support co-branded MADA subbrand cards.
• Risk Profile: Extend Forter risk engine to include additional 3DS related data.

Added​

• Connector Settings: Add new connector setting Provider Settlement: Accept from other provider GUIDs to allow transactions from different providers to be included in the same settlement.

Fixed​

• Fee Management: Fix fee calculations which are based on card region for captures and voids.
• Post Processing Jobs: Fix the display of seller names in Transaction Reports for split payments.
• Transaction List: Fix an issue where some transactions were not displayed in the transaction list.
• UI Navigation: Fix an issue that prevented filtering Admin Users when pressing the Enter key.

Gateway Adapters​

Changed​

• Adyen (ADY-EP3-MOPAY): Add support for the new payment method MobilePay, a widely used mobile wallet in Denmark and Finland that allows customers to pay using their mobile phone.
• American Express (AMX): Add a setting to map the fee type based on the discountRate: negative rate to markup-vat, positive rate to standard markup.
• Autopay (AUTO): Add support for settlement handling.
• checkout.com (CHE-EP1-CC,CHE-EP2-CC):
  • Add support for additional parameters for digital currency transactions.
  • Add a TransactionIndicatorMode setting to specify transaction indicator inference when none is provided.
• checkout.com (CHE-not-CC): Add support for Net settlements. The settlement type can now be configured as Net or Gross.
• Dimoco (DIM): Fix the settlement datetime to 12:00 PM to ensure consistent settlement timing across time zones and daylight saving changes.
• dLocal (DLO-EP1-CC): Add support for Deregisters.
• dLocal (DLO-EP1-PIX): Add support for the new payment method Pix Automático for dLocal, a Brazil‑based instant recurring payment solution that lets merchants automate authorized Pix transactions without requiring customers to approve each payment.
• HDFC CCAvenue (CCAV): Add support for settlement and reconciliation handling.
• PayPal Complete Payments - PPCP (PPCP):
  • Add support for the disableMaxWidth parameter in the SDK.
  • Include the invoice_id in Capture requests to ensure it is available in chargeback details.
• VoltUnifiedGlobalPayments (VUGP): Add support for beneficiary account identifiers (BSB, account number, and BIC) for payments in Australian Dollars (AUD).

Fixed​

• checkout.com (CHE-EP1-GOP,CHE-EP2-GOP): Fix an issue where Google Pay (PAN_ONLY) tokens processed with a provider 3DS challenge could not be used for subsequent transactions.
• DPO Pay (PAYGA-PYGT): Fix an issue where the transaction status is not updated.
• HDFC CCAvenue (CCAV): Fix an issue with response parsing.
• PayPal Complete Payments - PPCP (PPCP-EP1): Fix handling of STC (Set Transaction Context).
• VoltUnifiedGlobalPayments (VUGP):
  • Fix an issue with handling callback notifications.
  • Fix an issue with payment redirects and notification URLs.

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

Fixed​

• Callback: Postback notifications that previously failed due to DNS lookup issues will now be queued for retries.
• Callback: Add additional transaction logs when callback notifications fail due to DNS lookup issues.
• Fee Management: Adjust the default value for the fee configuration form to prevent unexpected configuration changes.
• Provider Settlements and Reconciliation: Fix an issue where refund transactions received via settlements were not created when the connector setting Provider Settlement: Create unknown transactions was enabled.
• Transaction List: Fix an issue where no transactions were returned when filtering by multiple UUIDs in Live mode.

Gateway Adapters​

Changed​

• 2C2P (2C2P-EP1): Update test and production endpoints.
• Adyen (ADY-EP1-CC): Map additionalData from Adyen to extraData.additionalPspResponse in API responses and callbacks (JSON-encoded) when enabled via a new connector configuration.
• Stripe (STRV2-EP1): Add support for reconciliation.
• Stripe (STRV2-EP3): Add support for reconciliation.

Fixed​

• dLocal (DLO): Treat adjustment lines as settlement meta 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.

Gateway API​

Fixed​

• Provisioning API: Fix bug where an auto-generated shared secret on connector creation returned a value longer than the actual stored one.

Gateway Features​

Changed​

• Risk Profile: Update Forter risk engine to use Dispute API (v10.1).
• Risk Profile: Add configurable Forter risk engine 3DS recommendations with an option to adjust 3DS requirements for transactions based on those recommendations.

Added​

• Fee Management: Add new fee constraint 3DS (options: any or inhouse) which allows setting fees based on the 3DS environment used for a transaction.
• Fee Management: Improve the transactionSubType constraint by showing any as the default option.
• Transaction Details: Add viewing of fraud tags in the Transaction Details page for merchant users. Enable with the frontend.transaction.tag.show permission. Admin users have the transaction.tag.show permission enabled by default.
• Transaction List: Add the Advanced Filter with a simplified set of filter options for merchant users in the Transactions view. It can be enabled with the frontend.transaction.advanced-search permission.

Fixed​

• Risk Profile: Fix an edge case where transaction risk data couldn't be stored.

Gateway Adapters​

Changed​

• dLocal (DLO-EP1-VPAY): Enable V Pay for Paraguay.
• JPMorganChase (CHA):
  • Add new setting to select report type: Funded Transaction Fee Details (FTI) or Settlement Details (PE).
  • Add new setting to specify settlement retrieval type: Polling-Based Retrieval or Notification-Based Retrieval.
• Nuvei (NUV-EP1-PSE): Update documentation for payment method PSE.

Fixed​

• JPMorganChase (CHA): Fix several issues with notification handling and settlement file retrieval.
• MultiSafepay (MUL-EP1-CC): Attempt to retrieve the scheme reference identifier from the initial MultiSafePay transaction if it was missing in order to facilitate recurring transactions.

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.

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.

API​

Changed​

• BI Data Source: BREAKING CHANGE BI Data Source API v1 is deprecated and will be removed in a future release. We strongly recommend migrating to v2 as soon as possible.

Fixed​

• Pay-by-Link API: Fixed an issue that would prevent a pay-by-link transaction from being canceled if a failover occurred for the transaction.
• Push API: Fixed an issue that would cause a type error if an empty body request was submitted in a Push API request.
• Transaction API: Fixed an issue where invalid 3DS values (browserColorDepth, browserTimezone) sent to the API in transaction data would cause an error. These invalid values are now ignored.

Features​

Changed​

• Connector Settings: The "Postback: Include 3DS Data" connector setting is now also available in the global settings.
• Post Processing Jobs: Optimized the process of collecting transactions in post-processing jobs.
• UI Navigation: Improved the parent tenant selection when creating a new tenant. By default, the current tenant is set as the parent tenant and the drop-down is now searchable.
• UI Navigation: Updated risk logs so that they are loaded asynchronously. This improves the initial load time for the transaction details view. Risk data is now only loaded when expanding the view.

Added​

• Connector Configuration: Added audit logs for the "Additional Configs" in the connector view.

Fixed​

• Audit Log: Fixed an issue that would cause an error when accessing the audit log if the corresponding merchant cannot be found when checking access permissions.
• Fee Management: Fixed an issue that would cause an error when changing the mapping to a different fee entity. The mapping for the old fee entity is now removed, and the mapping is set to the new fee entity.
• Post Processing Setting: Fixed an issue with the "Create unknown transaction on connector with GUID" option for settlements that prevented unknown transactions in a settlement file from being added to the platform.
• Provider: Fixed an issue that would occur when saving a connector configuration. Previously configured connectors that were assigned to the same provider were removed when the configuration was saved, with only the new configuration linked to the provider.
• Provider Settlements and Reconciliation: Fixed an issue that would cause an error when trying to sort missing reconciliation data by merchant.
• Risk Profile: Fixed an issue where saving a risk rule without entering parameter values would result in a type error.
• Risk Profile: Fixed an issue that would cause an error when opening risk rules if the risk rule set ID referenced a risk rule set that does not exist. A 404 error is now displayed instead.
• Transaction Processing: Fixed an issue caused by the platform attempting to collect 3DS information for Apple Pay transactions. The system now checks whether a transaction uses Apple Pay before collecting additional 3DS information.
• UI Navigation: The loading page displayed for the collectMissing3DSecureData connector configuration was only displayed in English. The page is now displayed in the language of the transaction where available, with English as the fallback language.

Adapters​

Changed​

• American Express (AMX-EP1-AMX): Added a new gateway connector configuration option, "Force System Generated STAN". This option can be used to force the system trace audit number (stan) to be generated by the IXOPAY platform and stored in the additionalId1 field. The following options are available to determine the format of the STAN:
  • "Yes - Uppercase characters only"
  • "Yes - Upper- and lowercase characters".
• Banca Intesa (BAI-EP1): If the PSP includes the TRACEID in a transaction response, it is now included in the postback.
• Braintree (BRA-EP1-BLI): Added support for partial refunds for the Blik non-redirect payment method.
• Braintree (BRA-EP1-PPE): Added support for line items and a corresponding option, includeLineItems has been added to the connector configuration.
• dLocal (DLO-EP1-CC): The merchantTransactionId is now passed to the vault, in order to pass it on to the PSP in refund requests.
• HypYaad (HYP): Removed the mapping of payment references in settlement files, as this could lead to a single settlement file being split into multiple settlements.
• Mastercard Payment Gateway Services (MPG, BAMI): Added support for the scheme transaction ID.
• Nexi Group (NETS-EP1): Added support for specifying the language in the checkout payload for transactions. This ensures that the language field is included in the payload if it is included in the transaction's extra data.
• PayPal (PPA-EP1-PPE): Added the isFinalCapture flag for capture transactions. If set to true, the capture is marked as final on the PayPal side and no further captures are possible.
• Simulator: Added support for incremental authorization for simulated credit card transactions.

Added​

• WavePay (WAV): The WavePay push adapter allows cash collection payments to be pushed to the IXOPAY platform to ensure that these transactions are also available within the system.

Fixed​

• Afterpay (AFT): Fixed an issue with retrieving the minimum/maximum price, caused by a missing interface.
• American Express (AMX-EP1-AMX): Fixed an issue that would cause an error if settlement files are not formatted correctly.
• Braintree (BRA): If rows in a settlement file did not include a settlement date, the settlement date was previously taken from the first value found in the "Settlement Date" column of the file. However, this could result in the settlement date being incorrect. The behavior has therefore been changed to set the settlement date to the transaction's disbursement date instead.
• Braintree (BRA-EP1-PPE): The merchantAccountId is now only passed to Braintree's JavaScript SDK if a value is present.
• iyzico (IYZ):
  • Fixed an issue with that would cause the batch number to be set to the entire file name of the settlement file, rather than the initial numerical portion of the file name. This was caused by empty rows in the settlement file.
  • Fixed an issue that would cause some settlement files to be parsed incorrectly.
• Khipu (KHI): Fixed an issue with retrieving the bank list, caused by a missing interface.
• Klarna (KLW): Fixed an issue that would result in the error "Invalid Response" being returned for transaction without a body. An empty body is now handled correctly, with the HTTP error code being checked prior to parsing the response.
• Mashreq (MASH-EP01): Fixed an issue where the status of successful transactions was not set correctly due to the status in the response not being formatted as expected.
• Payabl (P21): Fixed an issue caused by the error code parameter being evaluated incorrectly.
• Paymee (PAYME-EP1-CCRD): Fixed an issue where refund amounts would be sent with a varying number of decimal places, which could sometimes lead to errors. Refund amounts are now formatted consistently.
• Trustly (TRU): Fixed an issue that would cause a generic payment error if the private key required to generate the signature was missing. The system now checks for its presence.

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.