Skip to main content

3 posts tagged with "Hosted Payment Pages"

View All Tags

Gateway — v.24.20

API

Changed

  • Transaction API: Fix an issue where invalid browserScreenHeight or browserScreenWidth values caused errors. Now, any invalid values are properly handled to ensure smooth processing.

Features

Changed

  • Transaction Processing: Remove the billing country restriction for the iDeal payment method, allowing values beyond NL and BE.

Added

  • Hosted Payment Pages: Add data attributes to the Google Pay button for easier configuration on the Hosted Payment Page (HPP). Supported attributes include data-button-color, data-button-type, data-button-radius, data-button-size-mode, and data-button-locale.

Fixed

  • Customer Profiles:
    • Fix an issue where the action buttons for Payment Instruments in the Customer Profile merchant view were not displayed.
    • Fix a bug where deregistering via the action button in the Customer Profile merchant view did not work properly.
    • Fix a bug where the detach and deregister actions for Payment Instruments in the Customer Profile merchant view did not reset the preferred payment method.
  • Pay-by-Link: Fix an issue where Pay-by-Link (PBL) data failed to display when customer information was missing from the transaction; it will now display correctly even if customer data is absent.
  • Provider Settlements: Fix an issue when settling preauthorize and void transaction fees.
  • Provider Settlements and Reconciliation: Fix an issue in settlement processing where refunds referencing pre-authorized transactions were not correctly matched to their capture transactions.
  • Transaction Processing: Fix surcharge calculation for direct PCI API requests.

Adapters

Changed

  • HUA NAN COMMERCIAL BANK (HNCB-EP2-HBQR): Update the encryption process for the HNCB QR payment method to use the PSP’s encryption endpoint instead of local encryption.
  • Volt (VOL-EP1):
    • Add pay-by-link capability.
    • Add JWT signature support for refunds to ensure strong customer authentication (SCA) compliance.

Fixed

  • dLocal (DLO): Fix issue with postback handling by using the correct transaction ID from the currently processing refund transaction, instead of the order ID from the debit.
  • PXP (PXP-EP1-CC): Fix the handling of transactionSubType in PSP callbacks to ensure proper support for Rapid Dispute Resolution (RDR).

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

API

Fixed

  • Provisioning API: Resolved an error in the Provisioning API by adding null checks when building response objects for meta connectors without a default connector.
  • Push API: Fixed handling of request bodies with invalid JSON.

Features

Changed

  • Customer Profiles: Made the action column in the customer profile payment instruments table non-sortable.
  • Transaction List: Increased the number of displayed connectors in the advanced search form from 100 to 700.

Added

  • Post Processing Jobs: Added the ability to export transaction extra data in post-processing export strategies, including "Write customized Settlement CSV", "Export Transactions to XLSX (Version 2)", "Export Transactions to XLSX", and "Export Transactions to CSV". Also, added "key" and "default" column configurations to "Export Transactions to XLSX (Version 2)", "Export Transactions to XLSX", and "Export Transactions to CSV".

Fixed

  • Account Updater: Improved the account updater to consider BIN lookup results alongside the card type for more accurate processing.
  • Account Updater: Fixed an issue in the Account Updater that caused cards to appear as updated twice in the batch for clients.
  • Connector Settings: Fixed a bug that caused the connector settings "Transactions: Expire automatically after (x) minutes" and "Expires pending transactions after given minutes" to not work when added as Global Settings.
  • Customer Profiles: Use the correct customer profile container for meta connectors.
  • Dashboard: Fixed an issue where the pivot table couldn’t resolve the connector list, causing multiple selections to show as ‘n/a’.
  • Dashboard: Fixed a dashboard issue where GUIDs were displayed instead of merchant names.
  • Hosted Payment Pages: Removed async from Google Pay JS on hosted payment pages to enable synchronous loading, ensuring the Google Pay button displays reliably.
  • Transaction List: Updated transaction list links to ensure they work correctly by including a default status, preventing 404 errors.
  • Virtual Terminal: Fixed issues in the Virtual Terminal for direct debit transactions by preventing mandate date validation when the field is empty and correcting format validation to display proper error messages instead of "unknown error".

Adapters

Changed

  • Klarna (KLW-EP1): Added a connector setting "treat the BACK status from klarna as CANCELLED".
  • Mashreq (MASH-EP01): Added support for debit auto-capture.
  • PAYONE (PASIX): Add new mappings for settlements:
    • Markup fee (condCode 701)
    • Dispute fee (condCode 55).
  • PXP (PXP-EP1-INST): Added support for the in-store card deposit payment method.
  • Sepa Express (SEP-EP3-SEP): Added support for settlement handling.
  • Worldline (ING-EP2): Always store the adapter transaction identifier if present to properly handle subsequent transactions.

Fixed

  • American Express (AMX-EP1-AMX): Fixed system trace audit number (STAN) issue by using a modulus operation on the transaction ID to ensure it fits within base36 encoding limits.
  • iyzico (IYZ): Fixed settlement handling for Iyzico to correctly parse the batch number for all settlement objects.
  • Spreedly (SPR-EP1-CC): Fixed date parsing to correctly handle microseconds included by the PSP.
  • Transbank (TRANS-TSB1): Fixed handling of empty responses.

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

Features

Changed

  • Hosted Payment Pages: Include the surcharge amount placeholder on the hosted payment pages.
  • Post Processing Jobs: Enable the ability to trigger a job on Account Update and include it in the CSV report of the Export Transactions to CSV exporting job.

Added

  • Post Processing Jobs: Add post processing Job Type Templates, allowing creation of templates based on existing job types. Templates can be enabled/disabled and cascaded to subtenants, with options for editing and deleting available in the template list view.
  • Post Processing Jobs: Add the new field netSettlementAmountUnsigned to the Job Configuration > Exporting step - Write customized Settlement CSV. This field calculates the net settlement amount as abs(settlement amount) - abs(fee sum), independent of the input settlement.
  • UI Navigation: Prepare for the upcoming menu rework by displaying information about the new Navigation Section "Tokenization." This section will house existing platform features such as Customer Profiles and Account Updater.

Adapters

Changed

  • Adyen (ADY-EP3-CC): Enhance security by adding HMAC signatures to protect the server from unauthorized webhook events in the AdyenCheckout configuration.
  • Beem (BEEM-EP1-BEEMW): Replace the certificate and key connector configuration fields with the pre-shared EFTPOS certificate and key.
  • checkout.com (CHE-EP1-CC): Rework the Connector Configuration for Payouts based on the platform being used.
  • eMerchantPay (EME-EP3-SEP): Changed storing of initial UUID to handle follow-up transactions on the initial transaction or any other connector.
  • Volt (VOL-EP1): Add settlements for Volt adapter.

Fixed

  • Sepa Express (SEP-EP3-SEP): Change the AIS flow according to PSP changes.
  • Valitor (VALIT-EP1-CC): Correct grouping of error code 07 – Pickup card.

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.