Skip to main content

16 posts tagged with "Stripe"

View All Tags

Gateway — v26.15

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

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 — 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 — v25.22

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.

Gateway — v25.21

Gateway Adapters

Changed

  • Adyen (ADY-EP3-WCP): Add support for WeChat Pay, a popular Chinese digital wallet allowing customers to pay directly in-app or by scanning a QR code.
  • GoCardless (GOC-EP1): Add customer’s bank name and account number ending to callback notifications, available via extraData.psp:customerBankAccount.accountNumberEnding and extraData.psp:customerBankAccount.bankName.

Added

  • Ecobank (ECO-EP1-CC): Add support for Ecobank. Ecobank is a leading pan-African bank with operations across West and Central Africa, enabling secure online credit card payments.

Fixed

  • Adyen (ADY): Fix callback notification handling to avoid card data inconsistencies.
  • PayPal Complete Payments - PPCP (PPCP-EP1): Fix item shipping cost values to correctly match the transaction currency by rounding amounts according to currency decimals.
  • Stripe (STRV2-EP1): Fix a bug preventing proper reconciliation handling.
  • Stripe (STRV2-EP3): Fix a bug preventing proper reconciliation 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.