10 posts tagged with "Hosted Payment Pages"

Gateway API​

Fixed​

• Transaction API: Fix an issue where callback notifications for payments using an existing customer profile did not include the customerProfileData object.
• Transaction API: Fix processing error responses to include the transaction uuid and purchaseId, and the stored API response log entry to match the response sent.

Gateway Features​

Changed​

• Transaction Processing: Improve general error mapping for declines caused by deactivated network tokens for ISO adapters.

Added​

• Post Processing Jobs: Add an optional Account Name setting to the camt.053 settlement report exporter, used as a fallback when no merchant name is available.
• Risk Profile: Add the new external risk provider Riskified. Riskified is a real-time risk management solution that uses machine learning to detect fraudulent orders and protect against chargebacks.

Fixed​

• Hosted Payment Pages: Fix an issue where the payment form did not show an error message when tokenization failed.
• Transaction Details: Fix an issue where expanding the Transaction Tree panel could show a false session-expired message and reload the page.

Gateway Adapters​

Changed​

• Klarna (KLW): Add a line item with the actual net settlement amount of each payout to the retrieved settlement data.
• PayU (PAU-E01): Add support for card payments in seven additional LATAM markets: Argentina, Chile, Panama, Costa Rica, Guatemala, Honduras, and El Salvador.
• Stripe (STRV2): Add an optional connectedAccount setting to restrict the report to a single connected account.

Fixed​

• EBANX (EBA-EP1-PIX,EBA-EP1-UPI): Fix an issue where customers were not redirected back to the shop after completing a payment and status notifications were not received.
• Klarna (KLW): Fix issues where tokenization could fail and stored customer tokens could not be used for merchant-initiated transactions.
• Nuvei (NUV-EP1): Fix an issue where merchant-initiated preauthorize transactions using stored payment data could be declined.
• Stripe (STRV2): Fix an issue where the connected account payout reconciliation report could not be generated.
• Stripe (STRV2-EP2-ACH): Fix an issue where dispute notifications for ACH Direct Debit payments were not processed.

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 an issue where the callback notification format 3-512 (JSON, SHA512-enforced) was rejected by createConnector and updateConnector requests.

Gateway Features​

Changed​

• Login: Improve error messages when adding a new multi-factor authentication method.

Added​

• Post Processing: Add a new settlement export column fees:vat:aggregation that aggregates all mapped provider VAT fees of a transaction into a single amount.

Removed​

• Network Tokenization: Remove Network Token Metadata field (to be re-introduced in a future release).

Fixed​

• Hosted Payment Pages: Fix an issue where selecting Set as preferred payment instrument did not mark the stored payment instrument as preferred in certain scenarios.
• Post Processing Jobs: Fix net and fees total amount calculations in CAMT.053 settlement exports for transactions in different currencies.
• Risk Engine: Fix an issue where the Riskified device fingerprinting script did not load for payment.js integrations.
• User Management: Fix an issue where the Invitations tab could fail to load for administrators with access to a large number of merchants.

Gateway Adapters​

Changed​

• Adyen (ADY-EP4): Add mapping of additional card data fields from webhooks for unknown transactions.
• dLocal (DLO-EP1-CC):
  • Add a new configuration setting Expose Installment Interest to include the installment interest amount in installment options responses.
  • Add a new configuration setting chargeArgentinaInUsd to process USD transactions for Argentina.
• EBANX (EBA-EP1-PIX,EBA-EP1-UPI): Add support for cancelling Pix Automático and UPI Autopay enrollments via Deregister transactions.
• EBANX (EBA-EP1-UPI): Add support for the new payment method UPI Autopay, including enrollment with an initial payment and recurring debits. UPI Autopay is a feature of India's Unified Payments Interface (UPI) that lets customers authorize automatic recurring debits from their UPI-linked bank accounts.
• NaverPay (NAV): Add support for automated settlement data retrieval and processing.
• Paynetics (PNE): Add support for the new settlement report flow covering posting, payout, and chargeback reports.
• Stripe (STRV2): Add an optional webhookSecret configuration setting to verify the signature of incoming webhooks.

Fixed​

• Adyen (ADY): Fix an issue where outgoing callback notifications for chargeback transactions contain the wrong adapter reference ID.
• Dimoco (DIM): Fix an issue where authorization rows with a matching transaction row caused duplicate reconciliation entries.
• dLocal (DLO-EP1-PIX): Fix an issue where enrollments (register) did not support both fixed and variable subscription amounts in all enrollment flows.
• PayPal (PPA):
  • Fix settlement report processing for refunds with currency conversion.
  • Fix an issue where settlement files without a bank reference ID could not be parsed.
• Redsys (RED-EP1-CC): Fix a 3DS issue where transactions failed with a repeated order number error when the 3DS method completion arrived after the challenge had started.
• Stripe (STRV2-EP2-ACH): Fix an issue with recurring debit transactions.
• VoltUnifiedGlobalPayments (VUGP): Fix an issue where callback notifications with an unexpected status format caused processing to fail.

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​

Changed​

• Post Processing Jobs: Add a credit card token type filter to Batch Less: Aggregate Transaction Values To Job Line Items strategy.
• Provisioning API: Add Network Token TRIDs to the listMerchants response.

Added​

• Hosted Payment Pages: Add possibility to manage and configure Content Security Policy (CSP) headers.
• Provider Settlement: Add automatic detection of second chargebacks when the first chargeback was already settled.
• Provisioning API: Add a new dedicated endpoint to configure and retrieve the multi-method routing configuration.

Fixed​

• Dashboard: Fix an issue where dropdowns in the dashboard did not work in Safari.
• Network Tokenization: Fix an issue where tokens stored during cross-merchant transactions with register were not marked active.
• Post processing: Fix the CAMT.053 settlement export to skip files with no reportable entries and to use fallback values for currency, account name, and booking date.
• Post processing: Fix the settlement net amount shown when the fee currency differs from the settlement currency.
• Provisioning API: Fix error responses to always return a consistent JSON format.

Gateway Adapters​

Changed​

• 2C2P (2C2P-EP1-CUP): Add UnionPay support as a dedicated UPOP payment method.
• 2C2P (2C2P-EP1-MACAU): Add support for the new payment method Macau Pass. Macau Pass is a widely used stored-value card and mobile payment service in Macau; customers complete the payment on a hosted page, with MOP as the supported currency.
• Adyen (ADY): Add support for handling chargebacks.
• Autopay (AUTO-EP1): Add handling of the scheme transaction identifier in callback notifications, storing it as the transaction's scheme reference.
• dLocal (DLO-EP1-CC): Add support for installments.
• EBANX (EBA): Improve callback notification and error handling for the Pix, Pix Automatico, and UPI payment methods with consistent status and error mapping.
• EBANX (EBA-EP1-PIX): Add support for the new payment method Pix. Pix is Brazil's instant payment system operated by the Central Bank of Brazil, allowing customers to pay in real time via QR code.
• NaverPay (NAV): Improve error mapping for failed transactions.
• Paynetics (PNE):
  • Add parsing of TRN2 transaction reports for reconciliation when the new report retrieval mode is enabled, replacing the legacy POF-based reconciliation.
  • Add support for chargeback handling.
• PayU (PAU): Add support for sending a merchant-provided tax amount with payment requests via a new configuration setting.

Fixed​

• Adyen (ADY): Fix callback handling for incremental authorizations.
• Adyen (ADY-EP2-SEP): Fixed an issue where recurring transaction were failing.
• EBANX (EBA-EP1): Fixed an issue where the adapter log captured the first partial refund ID instead of the current partial refund ID.

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​

Changed​

• Provisioning API: Add a new listRoutingConstraints endpoint that returns the available routing rules.
• Provisioning API: Add a new setConnectorRouting endpoint that allows configuring routing rules on meta-connectors.

Fixed​

• Provisioning API: Fix the routedConnectors field in the list connectors response to always return a list instead of an object.

Gateway Features​

Added​

• Admin UI: Add support to manage the Apple Pay Domain verification value.
• Business Intelligence: BDS transaction documents now include BIN metadata from persisted transaction BIN data.
• Connector Settings: Introduce a new connector setting allowing data manipulation. Refer to https://documentation.ixopay.com/manual/docs/connector/advanced-configuration/field-expression-language.
• Post Processing Jobs: Add support for making post-processing export files accessible to merchant users when jobs are split by merchant.
• UI Navigation: Add the MADA card logo to transaction views.

Fixed​

• Customer Profiles: Fix an issue where the payment token was not correctly assigned after a successful retry transaction.
• Hosted Payment Pages: Fix an issue where register transactions on the hosted payment page failed to initialize for Apple Pay and Google Pay.

Gateway Adapters​

Changed​

• Adyen (ADY-EP3-PE): Add support for the new payment method Pay-Easy Online Banking. Pay-Easy is a Japanese payment method that allows customers to pay through their internet banking portal, connecting to over 550 banks via the Multi-Payment Network.
• Dimoco (DIM-EP1-CC):
  • Add support for parsing the actual settlement amount from SAP settlement files.
  • Add support for an updated settlement file format while maintaining backwards compatibility.
• Klarna (KLW-EP1-APM): Add support for automatically cancelling the Klarna payment session when a transaction expires, enabled via the disableHppSessionOnTxExpiration configuration setting.

Fixed​

• Adyen (ADY-EP3-CC): Fix an issue where transactions without a customer object caused an error.
• HUA NAN COMMERCIAL BANK (HNCB-EP2-HBQR): Fix an issue where the payment status did not update after completing a QR-code payment following an initial Open in App interaction.
• PPRO (PPR-EP1-EPS,PPR-EP1-IDE): Fix an issue where unfunded transaction reversals caused incorrect chargeback entries and reconciliation failures.
• STUZZA (STU-EP1-EPS): Fix a caching issue where test transactions could retrieve an incorrect bank list.

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​

Changed​

• Data Export: Improve the stability and reliability of the Data Export.

Added​

• Hosted Payment Pages: Add support for installments on the Hosted Payment Page. This feature is currently available for dLocal (DLO-EP1-CC) and Adyen (ADY-EP3-CC).
• Provider Settlements and Reconciliation: Add a setting to choose whether the receipt date or the settlement date (default) should be used for unknown transactions.

Fixed​

• Callback: Fix an issue where the schedule status (scheduleData.scheduleStatus) in callback notifications was incorrect for scheduled transactions.
• Risk Profile: Fix the Forter risk check engine script (on the HPP) to use the correct version.

Gateway Adapters​

Changed​

• dLocal (DLO): Add a setting to configure how TAX_LOCAL_AMOUNT is mapped during settlement handling - either as Scheme Fee or VAT.
• dLocal (DLO-EP1-UPI): Add support for UPI. UPI is a real-time payment system in India. This integration supports the eMandate flow, enabling the processing of recurring transactions.
• EquensWorldline (EQW-EP1-CC): Add support for network tokens.
• JPMorganChase (CHA):
  • Improve the report by displaying fees and sale amounts correctly on the same line.
  • Update the column Settled Conveyed Code to Conveyed Settled Code in the settlement retrieval file.
• Nuvei (NUV-EP1-NEQ): Add support for Nequi. Nequi is a popular mobile payment solution in Colombia that allows users to send and receive money, supporting both debit and payout transactions.
• Paynetics (PNE-EP1-CC): Add support for network tokens.

Added​

• HDFC CCAvenue (CCAV): HDFC CCAvenue is a leading payment gateway in India, enabling secure and reliable Credit Card payments via redirect. The new adapter supports Debit, Preauthorize, Capture, Void, and Refund transaction types.
• VoltUnifiedGlobalPayments (VUGP-EP1-BTR): Volt Unified Global Payments is a next-generation digital payments gateway, enabling PSD2 bank-direct payment services in Europe, the UK, and Australia. The new adapter supports Bank Transfer payments for Debit and Refund transaction types.

Fixed​

• Adyen (ADY): Add error handling for unsupported currencies.
• JPMorganChase (CHA): Fix various issues in settlement parsing to ensure data is processed correctly.
• Nuvei (NUV-EP1): Fix identifier handling to ensure refunds work correctly.
• Redsys (RED-EP1-CC): Fix the use of the reference scheme transaction identifier.
• Stripe (STRV2-EP1): Improve reconciliation handling to prevent conflicts and issues with unknown transactions.
• Stripe (STRV2-EP3): Improve reconciliation handling to prevent conflicts and issues with unknown 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.