Skip to main content

14 posts tagged with "UI Navigation"

View All Tags

Gateway — v26.7

Gateway Features​

Changed​

  • Post Processing Jobs: Improve resilience for data retrieval in specific error scenarios.
  • Post Processing Jobs: Improve performance for collecting strategies based on uploaded files.
  • Transaction Processing: Improve handling of doNotResubmit flags for Merchant Advice Codes.
  • UI Navigation: Improve session handling to prevent unexpected logouts while navigating the gateway platform.

Added​

  • Provider Settlements and Reconciliation: Add a new functionality to amend provider settlement metadata on the Provider Settlements page.

Gateway Adapters​

Changed​

  • Adyen (ADY-EP3): Add support for additional parameters for splits, platform chargeback logic, and store ID.
  • Adyen (ADY-EP3-CC): Add a new setting to include provider 3DS challenge related information in the callback notification.
  • Adyen (ADY-EP4-INST): Add a new setting which allows automatically creating transactions that were completed directly at the terminal.
  • American Express (AMX): Add documentation for AVS and CVV support.
  • Autopay (AUTO-EP1): Add support for live TraceID migration to improve cross-adapter compatibility.
  • checkout.com (CHE-EP1-CC,CHE-EP2-CC):
    • Include additional BIN data from CheckoutCom in the callback notification.
    • Add support for ramp provider affiliate parameters.
  • NaverPay (NAV-EP1): Add additional configurations for default item category type and default item category id.
  • Paynetics (PNE): Add support for SFTP configuration for settlements and reconciliations.
  • Redsys (RED-EP1-CC): Add a new setting to include provider 3DS challenge related information in the callback notification.

Fixed​

  • Bank of America (BOFA): Remove hidden whitespaces in the account number and routing number for callback notifications.
  • Worldline (ING): Fix settlement handling with zero decimal currency amounts.

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 — v26.3

Gateway Features​

Added​

  • BI Data Source: Improve the management of BDS settings by allowing the definition of default profiles at the Merchant and Connector levels for more consistent and simplified configurations.
  • Job Configuration: Add support for the customerProfileIdentification and customerProfileGuid fields in export strategies (CSV, XLSX, XLSX v2).
  • Job Configuration: Add a new line item grouping card Country (buyer Country as a fallback) for the Aggregate Transaction Values To Job Line Items strategy.

Fixed​

  • Audit Log: Fix Audit Log Export which sometimes produced duplicate or incomplete export results.
  • Risk Profile: Adjust Forter risk engine to validate ECI values to avoid formatting errors.
  • Transaction Details: Fix Resend postback functionality.
  • Transaction Processing: Add missing support for Auto-Capture for failover transactions.
  • UI Navigation: Fix an issue in the customer profile view when loading a large number of profiles.

Gateway Adapters​

Changed​

  • Stripe (STRV2): Add support to match transactions with a latest_charge for post processing purposes.

Added​

  • Kueski (KUE-EP1-KP): Kueski is a leading provider of consumer credit in Mexico, enabling flexible "Buy Now, Pay Later" installment-based payments for customers without traditional credit cards. The new adapter supports the Kueski Pay payment method for Debit and Refund transaction types.

Fixed​

  • Adyen (ADY): Fix handling of settlement files with unexpected file names.
  • Dimoco (DIM): Fix reconciliation parsing of AUT/TRX fields and fees.
  • Redsys (RED-EP2-BIZ): Improve error 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.

Gateway — v26.0

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 — v24.13

API​

Changed​

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.

Gateway — v24.10

API​

Added​

  • payment.js: In addition to styling the CVV and card number fields on checkout pages, it is now also possible to apply styles to their placeholder text.

Features​

Changed​

  • Provider Settlements and Reconciliation: Updated the data fetcher to:
    • Validate input data
    • Inform users when the data fetcher is saved with missing or invalid data
    • Allow the data fetcher's interval to be set to 0 (no retrieval). This is now also the default value for new data fetchers.

Added​

  • Audit Log: Added the ability to export user management audit logs that includes information on users, such as the date the user was added, modified or deleted, their last login and the tenant the user is assigned to. These export logs can be found under Security Center on the Audit Log Export tab.

Fixed​

  • Documentation: Updated the Schedule API documentation to address incorrect information.
  • Documentation: Fixed an issue with the signature testing tool that would cause it to generate an incorrect signature due to a difference in how the URL path is generated compared to the IXOPAY gateway.
  • Provider Settlements and Reconciliation: Fixed an issue with chargeback reversals that would result in an error that the chargeback could not be found. This was caused by postback notifications that contain the same reference ID for both capture and preauthorization transactions.
  • Risk Profile: Fixed an issue that would prevent Starter and Growth users from editing the risk ruleset. When attempting to edit the ruleset, an error message was displayed that only one risk profile is allowed.
  • UI Navigation: Fixed an issue with Apple Pay and Google Pay transactions showing the incorrect icon for the token type.

Adapters​

Changed​

  • PAYONE (PASIX):
    • Fixed an issue with mapping fees for SIX via the E-Link adapter. New mappings have been added for the scheme fees and interchange fees to address this.
    • Updated the handling of settlements to use the current date and time as the fallback value for the payment date and settlement number if this value is not present. This was the case if the refunded amount was larger than the captured amount. Furthermore, if a payment number is available, this is used as the payment reference.

Fixed​

  • China UMS (UMS-EP1-H5): Fixed an issue with missing adapter-related data in the postback notification.
  • Paysafecard (PSC-EP1): Fixed an issue that would cause refunds to fail due to the adapter transaction ID being truncated.

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.