Skip to main content

11 posts tagged with "Stripe"

View All Tags

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.
  • 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.
  • EquensWorldline (EQW-EP1-CC): Add a new configuration option to select between the old and new Settlement and Reconciliation retrieval logic. By default, the old logic is used.
  • 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.

Gateway, Portal — v25.6

Gateway API

Fixed

  • Transaction Processing: Fixes the validation for follow-up transactions to consider failover transactions.

Gateway Features

Fixed

  • Dashboard: Fixes an edge case where a successful manual refund results in an error page.
  • Risk Profile: Improves the handling of invalid configurations for the Credit card PAN Check risk check.
  • Transaction List: Fixes the functionality of the delete button in the advanced search filter.

Gateway Adapters

Changed

  • Stripe (STRV2): A new option is made available in the Descriptor configuration to utilize the value provided in extraData.statement_descriptor.
  • Worldpay (WOR-EP1): Add support for the new payment method Klarna. Klarna is a service pioneered by Swedish innovators that redefines the online shopping experience by offering flexible payment options. It provides consumers with versatile and convenient ways to pay, making shopping more adaptable to individual needs.

Added

  • Adyen (ADY-EP4-CC): Add the Adyen POS adapter with added support for processing transactions using Point of Sale terminals. Adyen is a global payment service provider and technology platform that empowers businesses with secure and versatile payment solutions.

Portal

Added

  • Proxy Tokenization Page:
    • Add Proxy filter. This allows you to filter results for a specific proxy profile
      • Explicit identifier of proxy filter
      • Filter is always present
      • Returns matching vault and filters non matched proxy profiles
        • Profile Name
        • Profile Description
        • Profile URL
        • Profile ID
        • Profile Alias
    • Brand Vault filter. This provides clarification to what values can be filtered
      • Explicit identifier of proxy filter
      • Filter is always present
    • Delete Proxy Profile. This enables users to delete proxy profiles
      • Removes proxy
    • Create Proxy Alias. This enables users to create proxy alias without a support ticket
      • Adds new Alias.

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.

API v2, Gateway, Payment Services v2 — v25.1

Gateway Features

Fixed

  • Job Configuration: Fix a bug in the post-processing job configuration where endpoint URL validation in the Send document to endpoint exporting configuration incorrectly restricted URL paths to lowercase only.

Gateway Adapters

Changed

  • KCP Mobile, KCP PC (KCPMO-EP1, KCPPC-EP01): Add extra data to callback and API response, including card acquirer code (extraData.acqu_cd), card issuer code (extraData.card_cd), payment method (extraData.pay_method), truncated PAN (extraData.card_no), and bank code (extraData.bank_code).
  • PayPal Complete Payments - PPCP (PPCP-EP1): Add chargeback protection details to API response, including seller protection status (extraData.seller_protection_status), dispute categories (extraData.seller_protection_dispute_categories), and PayPal account status (extraData.paypal_account_status).
  • Stripe (STRV2): Add support for account funding transactions (AFT).
  • Worldpay (WOR-EP1-CC): Add documentation about the extraData.refundAuthorisationReference parameter returned in callbacks.

Fixed

  • PXP (PXP-EP1-INST): Fix a typo in an error message.
  • Worldline (ING-EP1, ING-EP2, ING-EP3, ING-EP4, ING-EP7): Fix chargeback handling in the settlement and reconciliation parser.

API v2

Added

  • APIv2’s NetworkToken endpoints now return an error if multiple Network Tokens exist for a single token, requiring the new tokenReferenceId parameter to specify which one to use.

Payment Services v2

Added

  • Add Merchant Advice and Brand Auth Response code mappings to AdyenDirect, FirstDataIPG, and Orbital gateways for additional insights on how to handle failed 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.0

Gateway API

Fixed

  • Provisioning API: Fix an error that occurred when attempting to update merchant users with apiUserSettings configured.

Gateway Features

Changed

  • Connector Configuration: Change save message of connector configuration to display multiple validation errors simultaneously, instead of just one.
  • Risk Profile:
    • Applied cosmetic changes for consistency, including button renaming and layout adjustments.
    • Restricted Audit Log access with the Admin User Permission misc.show-public-audit-log.

Added

  • API Testing: Add a Clear CC Token button to the API Testing view to reset credit card fields without refreshing the page.
  • Risk Profile: Add a new risk rule to validate the presence of both the transaction indicator and reference scheme ID.
  • Risk Profile: Add support for BIN segments (Consumer, Business, Commercial, Government, Unknown) and add a new risk rule BIN segment of credit card is [in, not in] [list of segments] to replace the previous BIN level of credit card is [in, not in] [list of levels] rule in the future, allowing checks for specific BIN segments.

Fixed

  • Connector Settings: Fix compatibility of the Manipulation: Always set withRegister connector setting on meta-connectors with Customer Profiles to ensure payment instruments are properly stored.
  • Provider Settlements and Reconciliation: Fix an issue where the upload button remained in the uploading state after a manual file upload error.

Gateway Adapters

Changed

  • dLocal (DLO-EP1):
    • Add /options/installmentsPlan endpoint to retrieve installment plans.
    • Add extra data parameters to debit and preauthorize transactions to enable installements (extraData.installments and extraData.installments_plan_id).
    • Change required status of customer.nationalId from mandatory to optional.
  • JPMorganChase (CHA-EP2): Add support for partial void transactions.
  • KakaoPay (KAKAO-EP1): Add support for settlement and reconciliation handling.
  • Nuvei (NUV-EP1):
    • Change required status of customer.email from mandatory to optional.
    • Change sFTP retrieval to no longer require permissions to rename the file on the remote server for settlement and reconciliation handling.
  • PayPal Complete Payments - PPCP (PPCP-EP1): Add chargeback protection details to postback response, including seller protection status (extraData.seller_protection_status), dispute categories (extraData.seller_protection_dispute_categories), and PayPal account status (extraData.paypal_account_status).
  • Worldpay (WOR-EP1): Add postback handling for online refunds. Merchants will receive the Refund Authorisation Reference number in extraData.refundAuthorisationReference via postback.

Added

  • Banco Popular Dominicano (BPD-EP1): Add the Banco Popular Dominicano adapter with support for debit transactions. Banco Popular Dominicano is the first privately owned bank in the Dominican Republic and is the leader in a wide range of banking and financial services in the country. It is the principal company of Grupo Popular.

Fixed

  • Global Payments (GBP): Prevent duplicate settlement errors by using more specific settlement batch numbers.
  • JPMorganChase (CHA-EP2):
    • Fix handling of partial void followed by capture.
    • Update extraData.totalAuthAmount after partial void.
  • PayPal Complete Payments - PPCP (PPCP-EP1-PPE):
    • Enable partial capture and void capabilities for the PayPal payment method via the PayPalCompletePlatform adapter.
    • Ensure that the PayPal Partner Attribution ID is set for transactions processed through multi-method connectors.
  • PXP (PXP-EP1): Fix mapping of error code 100(77).
  • Stripe (STRV2-EP1): Use net amount instead of gross amount when parsing Line Items and Rolling Reserve for the Stripe Settlement Report.

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.