Skip to main content

14 posts tagged with "Stripe"

View All Tags

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.

Gateway — v25.20

Gateway Features

Added

  • Customer Profiles: Add a new flag for the payment selection page to allow storing a payment instrument without automatically linking it to the customer profile.
  • Hosted Payment Pages: Add support for the setRequireCardHolder method in PaymentFormV2.
  • Job Configuration: Add a new filter Transaction Types to the Collect Transactions by Uploaded CSV File strategy to collect only transactions of the selected types. Not selecting any types will apply no filter.
  • Provider Settlements and Reconciliation: Add a new constraint to specify whether transactions are from a merchant of type marketplace.

Fixed

  • Job Configuration: Fix the Collect Transactions by Uploaded CSV File strategy to ignore invalid uploaded files.

Gateway Adapters

Changed

  • Adyen (ADY-EP3-P24): Add support for the Online Banking Poland payment method. This real-time bank transfer option allows customers to securely pay directly from their bank account and is widely used in Poland for e-commerce transactions.
  • checkout.com (CHE-EP1-CC): Add a configuration to enable Account Name Inquiry (ANI) for register transactions.
  • Dimoco (DIM): Add a new configuration option to select between the old and new Settlement and Reconciliation retrieval logic. By default, the old logic is used.
  • dLocal (DLO-EP1-UPI): Add support for the UPI (Unified Payments Interface) payment method. UPI is an instant real-time payment system widely used in India, enabling customers to transfer funds directly between bank accounts via mobile or web applications.
  • JPMorganChase (CHA-EP1-CC): Add support for retrieving and processing a new settlement report entity type Funded Transaction Fee Details (FTI).
  • Klarna (KLW): Add a new fee type representing the total VAT amount for settlements.
  • PayPal Complete Payments - PPCP (PPCP): Add a new setting to include customer billing and shipping details from PayPal in the callback request.

Fixed

  • DigitSecure (DS-EP1-T2P): Resolve an issue where the Transaction Details page could not be loaded.
  • Nuvei (NUV-EP1): Fix a bug where the wrong identifier was stored as the adapter transaction ID.
  • Stripe (STRV2-EP1): Fix an issue that prevented configuring reconciliation handling.
  • Stripe (STRV2-EP3): Fix an issue that prevented configuring reconciliation handling.
  • Worldline (ING-EP8-CC): Fix minor payload change for captures.

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

Gateway Features

Fixed

  • Callback: Postback notifications that previously failed due to DNS lookup issues will now be queued for retries.
  • Callback: Add additional transaction logs when callback notifications fail due to DNS lookup issues.
  • Fee Management: Adjust the default value for the fee configuration form to prevent unexpected configuration changes.
  • Provider Settlements and Reconciliation: Fix an issue where refund transactions received via settlements were not created when the connector setting Provider Settlement: Create unknown transactions was enabled.
  • Transaction List: Fix an issue where no transactions were returned when filtering by multiple UUIDs in Live mode.

Gateway Adapters

Changed

  • 2C2P (2C2P-EP1): Update test and production endpoints.
  • Adyen (ADY-EP1-CC): Map additionalData from Adyen to extraData.additionalPspResponse in API responses and callbacks (JSON-encoded) when enabled via a new connector configuration.
  • Stripe (STRV2-EP1): Add support for reconciliation.
  • Stripe (STRV2-EP3): Add support for reconciliation.

Fixed

  • dLocal (DLO): Treat adjustment lines as settlement meta data.

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.