Skip to main content

2 posts tagged with "payment.js"

View All Tags

Gateway — v.24.12

API

Changed

  • payment.js: Updated the version of jQuery used in payment.js to 3.7.1.

Added

  • BI Data Source: Introduced BI Data Source API v2 built on OpenSearch for improved performance and functionality.

Features

Changed

  • Job Configuration: A new column has been added to the "Write customized Settlement CSV" export step, relatedFirstTransactionUuid.

Added

  • Audit Log: Audit logs are now available for providers. These logs include changes to the provider ID, data fetcher and configuration changes.

Fixed

  • Callback: Fixed an issue where notifications for partial refunds were sometimes mapped to the wrong refund transaction.
  • Post Processing Jobs: The "Write customized Settlement CSV" job step included two columns that accessed the UUID of the related transaction (referenceTxUuid and referenceUuid). referenceTxUuid has therefore been removed.
  • Post Processing Jobs: Fixed an issue that would cause an error if no provider was entered in a connector.
  • Provider Settlements and Reconciliation: When processing a settlement file, the meta-connector for a transaction is now set correctly if a meta-connector is used by the related transaction.
  • Provider Settlements and Reconciliation: Fixed an issue that would occur when creating new transactions from a settlement.
  • Provider Settlements and Reconciliation: Fixed an issue caused by restricting the allowed ports in the SFTP receiver.
  • Virtual Terminal: Fixed an issue that could occur if surcharge and GST fee calculation permissions were granted, but only surcharges were configured in the virtual terminal.

Adapters

Changed

  • Braintree (BRA-EP1): The merchant account ID has been added to the configuration used in the setup process to improve the integration. This ensures that transactions are correctly associated with the relevant merchant account.
  • Klarna (KLW-EP1-APM): Added support for the following countries:
    • Czechia
    • France
    • Greece
    • Hungary
    • Ireland
    • Italy
    • Poland
    • Portugal
    • Slovakia
    • Romania
    • Spain.
  • PXP (PXP-EP1):
    • Added support for the Aircash and Aircash Abon payment methods.
    • Added support for payout with redirect.
  • Simulator: Updated the documentation to cover overriding the outcome.

Fixed

  • Alignet (ALI-EP01-VIS): The phoneCode and phoneSubscriber fields are no longer mandatory.
  • Klarna (KLW-EP1):
    • Fixed an issue in the documentation regarding the shipping email and total discount amount. customer.shippingEmail has been corrected to customer.extraData.shippingEmail and items.item.totalDiscountAmount has been changed to items.item.extraData.totalDiscountAmount.
    • Fixed an error that would occur if a request timed out. This was caused by the empty response not being handled correctly.
  • Mashreq (MASH): Fixed an error caused by unknown transactions in the postback.
  • Sepa Express (SEP-EP3): Fixed an issue that would cause an error if the connectorId is missing when creating a mandate. The system now checks that this required value is present.
  • Worldline (ING): The SFTP password is no longer mandatory, as the setup is switching over to using a private key.

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 — v.24.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.