Skip to main content
Welcome to the preview portal — This is an early release of the new Doc Hub experience, with more content coming soon.

October 2026


Production releases for the weeks ending October 2 to October 30, 2026: features, fixed issues, and known issues.

October 30, 2026

These release notes cover releases for the week ending October 30, 2026.

Bulk Actions Permissions Added for Organization Onboarding

Ticket: RM-49277

Description: A new Bulk Actions module enables resellers to onboard multiple organizations to the platform more efficiently. This enhancement reduces manual effort by supporting bulk onboarding workflows and providing visibility into submitted bulk actions. Users with the appropriate permissions can view previously submitted bulk actions or initiate new bulk onboarding actions through the Bulk Actions module.

Mandate: Does not apply.

Audience: Some resellers and portfolio managers responsible for onboarding organizations.

Technical Details: Access to the Bulk Actions module is controlled by the canViewBulkActions and canManageBulkActions derived permissions. Users receive these permissions when the Bulk Actions feature and the corresponding onboarding permissions are enabled.

Important Dates: Released on October 21, 2026.

Automated Clearing House (ACH) eCheck Follow-On Credit Eligibility Restored

Ticket: RM-49229

Description: This release corrects a defect affecting Automated Clearing House (ACH) eCheck transactions. In some cases, follow-on credits were incorrectly unavailable because the system could not accurately calculate transaction age when processing request IDs longer than 26 characters. Following this release, merchants can perform eligible follow-on credits for ACH eCheck transactions for up to 180 days after the original debit transaction, consistent with the intended processor rules.

Mandate: Does not apply.

Audience: Some merchants processing eCheck transactions through an ACH processor.

Technical Details: No API changes are required, and no merchant configuration changes are necessary to use this correction.

Important Dates: Released on October 24, 2026.

Blank Batch Response Files for Batch Upload

Ticket: EPS-43394

Description: Some merchants submitting stand-alone credits through Batch Upload might receive a blank response file even when the transaction processes successfully.

Audience: Merchants using Batch Upload through Payments 2.0 processing flows, including affected Fiserv merchants.

Technical Details: For affected Batch Upload transactions, transaction batch identifiers are not populated during processing through the Payments 2.0 REST/Kafka ingestion channel. As a result, the batch reporting process cannot associate transactions with the submitted batch and returns a blank response file. Transaction processing itself is not affected and successful transactions can continue to be processed normally.

Workaround: No known workaround.


Some Click to Pay Authentication Results Misreported

Ticket: EPS-43856

Description: Some customers using Unified Checkout Click to Pay (CtP) with Passkey authentication might receive an indication that cardholder authentication was unsuccessful even when authentication has completed successfully.

Audience: Merchants and integrators using Unified Checkout Click to Pay (CtP) through the UI.

Technical Details: For impacted transactions, the response might return cardholderAuthenticationStatus=false even though valid authentication data such as CAVV and XID values is present.

Workaround: To determine whether additional 3-D Secure authentication is required, merchants validate the presence of authentication data returned in the Click to Pay payload, including returned 3-D Secure values such as CAVV and XID.


Risk Profile Configuration Not Visible

Ticket: EPS-46325

Description: Some transactions might be rejected even though the associated risk profile configuration is not visible in the , making it difficult for affected acquirers to determine the source of the rejection or identify the merchants assigned to the profile.

Audience: Resellers and acquirers using Partner Risk Control (Parc).

Technical Details: Impacted transactions might be rejected with the error message Your aggregator or acquirer is not accepting this transaction - CARD_CATEGORY_ECI_REFUSED, triggered by a off_us_domestic_credit configuration. In affected cases, the risk profile containing the rule is not displayed in , preventing users from viewing the configuration or determining which merchant IDs (MIDs) are assigned to the profile.

Workaround: No known workaround.


Unified Checkout Customer IP Addresses Not Forwarded

Ticket: EPS-46439

Description: When a Unified Checkout transaction includes a customer's IP address, Decision Manager does not consider the IP address during evaluation.

Audience: Some merchants using Unified Checkout with Decision Manager.

Technical Details: Some transactions might bypass Decision Manager rules that rely on the customer's IP address because the deviceInformation.ipAddress value is not included in risk evaluation. No API error is returned, and non-IP-based Decision Manager rules continue to function normally.

Workaround: No known workaround.

October 23, 2026

These release notes cover releases for the week ending October 23, 2026.

No customer-facing features were released this week.

No customer-facing fixes were released this week.

There are no known issues this week.

October 16, 2026

These release notes cover releases for the week ending October 16, 2026.

Installment Data Added to Settlement Files for Peru Transactions

Ticket: RM-48077

Description: Settlement files for Peru transactions now include additional installment data to support enhanced transaction reconciliation and reporting. This enhancement enables installment-related information to be included for both Mastercard and non-Mastercard transactions and allows issuer additional-data fields to be reported together within the same settlement file when applicable.

Mandate: Does not apply.

Audience: Some merchants and acquirers processing installment transactions in Peru.

Technical Details: The enhancement adds the CP08 TCR2 record to TC33 files so that both issuer_additional_data and issuer_additional_data_response can be included simultaneously. It also generates CP01 TCR9 records for Peru transactions that contain installment data.

Important Dates: Released on October 14, 2026.

Invoice Webhook Notifications Are Now Correctly Delivered After Successful Payment Processing

Ticket: RM-49120

Description: Merchants now receive Invoice Webhook notifications after invoice payments are successfully processed.

Audience: Merchants using Invoice Webhooks.

Technical Details: An issue affecting invoice-payment event generation no longer prevents webhook notifications from being delivered.

Important Dates: Released on October 14, 2026.


Enterprise Users Are No Longer Unexpectedly Logged Out After Authentication

Ticket: RM-49846

Description: Some users were unexpectedly returned to the login page immediately after successfully signing in, including after completing one-time passcode (OTP) authentication.

Audience: Some users.

Technical Details: A client-side session-management issue incorrectly identified some active sessions as invalid and triggered an unexpected logout. Existing valid sessions now remain active when users open new browser tabs.

Important Dates: Released on October 16, 2026.

Validation and Capture Requests Return an Unexpected Response for CVN Soft Declines

Ticket: EPS-43280

Description: Some merchants using the Payments API receive an unexpected response when a combined validation and capture request encounters a card verification number (CVN) soft-decline condition. Instead of receiving the expected review status, the request returns a response indicating a CVN failure even though the transaction is authorized.

Audience: Some merchants using the Payments API.

Technical Details: Combined validation and capture requests submitted to POST /pts/v2/payments can return CV_FAILED for certain CVN soft-decline scenarios. Affected transactions can be authorized successfully while returning an unexpected response status.

Workaround: No known workaround.


Stand-Alone Credit Batch Uploads Return Incomplete Processing Information

Ticket: EPS-43394

Description: Some merchants using Stand-Alone Credit through Batch Upload receive incomplete processing information when batch uploads fail. Request IDs might not be searchable in the , Token IDs might not be displayed for affected transactions, and OLP (Offline Processing) batch response files might be blank.

Audience: Some merchants using Stand-Alone Credit through Batch Upload.

Technical Details: Failed batch uploads can return the error message invalidField_0=recurringSubscriptionInfo_subscriptionID.

Workaround: No known workaround.


Certain SDK Versions Might Return Incomplete Payment Instrument Data or Fail Capture Context Requests

Ticket: EPS-43512

Description: Occasionally, merchants experience issues after upgrading to certain SDK versions. These issues include payment instrument requests that might return incomplete data, and capture context requests that might fail with a JSON parsing error instead of returning a capture context.

Audience: Some merchants using the .NET or .NET Standard SDK.

Technical Details: In CyberSource.Rest.Client.NetStandard v0.0.1.56 and later, payment instrument requests might return null values for count, total, and state data. In CyberSource.Rest.Client v1.0.1 and later, capture context requests might fail before returning a response.

Workaround: For payment instrument requests, count values can be derived by counting the returned payment instruments. For capture context requests, remaining on CyberSource.Rest.Client v1.0.0 avoids the issue.


Customer Invoicing Webhook Events Are Not Always Dispatched for Invoice Lifecycle Events

Ticket: EPS-43859

Description: Some merchants using customer invoicing webhooks do not receive webhook notifications for invoice lifecycle events such as invoice creation, sending, payment, or cancellation. Webhook subscriptions remain active and configured correctly, but webhook events are not dispatched for affected invoices.

Audience: Some merchants using Customer Invoicing webhooks.

Technical Details: Invoice lifecycle events are not always generated for webhook processing, which prevents customer invoicing webhook notifications from being dispatched.

Workaround: No known workaround.


Invoice Webhook Notifications Are Not Always Delivered After Successful Payment Processing

Ticket: EPS-44411

Description: Some merchants using Invoice Webhooks do not receive webhook notifications after invoice payments are processed successfully. Webhook subscriptions remain active and health checks succeed, but payment-completion notifications are not delivered.

Audience: Some merchants using Invoice Webhooks.

Technical Details: Some Invoice-payment events are not generated for webhook delivery processing even though payment processing completes successfully.

Workaround: This issue has been resolved per the "Fixed Issues" entry RM-49120.


Invoice Receipts Display an Incorrect Payment Solution

Ticket: EPS-44461

Description: Some merchants find that invoice receipts display Apple Pay as the payment solution even when Apple Pay was not used to complete the transaction.

Audience: Some merchants using Invoices.

Technical Details: Certain card-brand values can be incorrectly interpreted as payment-solution values when invoice receipts are generated. As a result, some transactions can be displayed as Apple Pay even when a different payment method was used.

Workaround: No known workaround.

October 9, 2026

These release notes cover releases for the week ending October 9, 2026.

No customer-facing features were released this week.

No customer-facing fixes were released this week.

Transaction Search Requests Return Intermittent 404 Errors

Ticket: EPS-43024

Description: Some merchants receive intermittent 404 errors when submitting Transaction Search requests through the REST API. As a result, transaction details are not always returned successfully.

Audience: Merchants using the Transaction Search REST API.

Technical Details: Requests submitted to the /tss/v2/searches endpoint intermittently return a 404 response even when transaction data is available.

Workaround: Retry the request to retrieve the transaction details.


Replay Selector Creation Fails in Decision Manager

Ticket: EPS-43615

Description: Some users are unable to create replay selectors for Decision Manager profiles. When the user attempts to create a replay selector, the operation fails and displays the error message An error occurred communicating with the server. Try again later.

Audience: Decision Manager users.

Workaround: No known workaround.


Non-US Visa Platform Connect Transactions Use an Incorrect Point of Service Condition Code

Ticket: EPS-43834

Description: Some merchants find that non-US Visa Platform Connect transactions use an incorrect Point of Service (POS) Condition Code value. Transactions are submitted with a POS Condition Code of 71, which is intended for US transactions only.

Audience: Some merchants using Visa Platform Connect payment processing.

Workaround: No known workaround.

October 2, 2026

These release notes cover releases for the week ending October 2, 2026.

Estimated and Incremental Authorization Support for Eligible Processing Connections

Ticket: RM-47041

Description: now supports estimated authorizations and incremental authorizations for the FDI Global processor, enabling merchants to obtain an initial authorization for an estimated amount and increase the authorized amount when additional charges are incurred. This enhancement supports lodging, vehicle rental, cruise, healthcare, and other variable-spend industries where the final transaction amount is not known at the time of authorization. Merchants can also maintain a single authorization lifecycle that aligns with card-brand requirements for estimated and incremental authorization processing.

Mandate: Does not apply.

Audience: Merchants in North America that process transactions through FDI Global.

Technical Details: Merchants can identify an authorization as an estimate using processingInformation.authorizationOptions.authIndicator=0 and can increase a previously approved authorization by submitting an incremental authorization request through /pts/v2/payments/{id} or ccIncrementalAuthService_run=true.

Merchants can submit multiple incremental authorizations against the same original authorization while maintaining transaction linkage throughout the authorization lifecycle. This enhancement supports estimated authorization use cases such as lodging, vehicle rental, cruise, and healthcare transactions and is available for Visa, Mastercard, and Discover transactions.

Important Dates: Released on September 30, 2026


Additional Search Fields Added to the Transaction Search API

Ticket: RM-49264

Description: The Transaction Search API now supports searching for transactions using additional identifiers that enable more precise transaction identification and reconciliation. Merchants can now search using a client transaction ID, airline ticket number, or passenger name.

Mandate: Does not apply.

Audience: Merchants that use the Transaction Search API and need to identify transactions using a client transaction ID, airline ticket number, or passenger name.

Technical Details: The Transaction Search API now supports searching for transactions using the merchant_transaction_identifier, airline ticket number, and passenger name fields. These additional search criteria help merchants identify and reconcile individual transactions more accurately when multiple transactions share similar attributes.

Important Dates: Released on October 1, 2026

User Registration for Direct Merchant IDs Now Completes Successfully

Ticket: RM-47419

Description: This release resolves an issue that could prevent user registration for direct merchant IDs that do not have a parent reseller. User registration now completes successfully, and activation emails are sent as expected.

Audience: Merchants that use direct merchant IDs without a parent reseller, including legacy direct merchant IDs that have not yet migrated to Visa Acceptance Platform.

Technical Details: Previously, user registration requests for direct merchant IDs without a parent reseller failed and did not create a user account.

Important Dates: Released on September 30, 2026


Account Updater Configuration Can Now Be Saved at the Merchant Level

Ticket: RM-48214

Description: This release resolves an issue that prevented merchants from adding and configuring the Account Updater product at the merchant level in the .

Audience: Portfolios that use the Account Updater product in the .

Technical Details: Previously, the default Account Updater template loaded without configuration values, and merchant-level Account Updater settings were not saved when users selected Apply. Account Updater templates now load the expected configuration values, and merchant-level settings are saved correctly.

Important Dates: Released on September 30, 2026


Login and Session Management Improvements

Ticket: RM-49264

Description: This release resolves several issues that could affect user access and session management in . Users authenticating with OTP-based multi-factor authentication (MFA) can now successfully sign in on the first attempt when a valid One-Time Password (OTP) is entered. Users whose usernames contain a period (.) can now log in successfully. Additionally, opening a new browser tab no longer affects active sessions in other open tabs.

Audience: users.

Important Dates: Release on September 29, 2026

.NET REST Client SDK Methods Might Not Return Unified Checkout Transient Token Data

Ticket: EPS-42309

Description: Developers using the .NET REST Client SDK might find that payment details are not returned when calling methods that retrieve Unified Checkout transient token transaction data. Although the API request completes successfully, the calling application does not receive the requested billing, shipping, or masked card information.

Audience: Developers using the .NET REST Client SDK to retrieve payment details associated with Unified Checkout transient tokens.

Technical Details: The TransientTokenDataV2Api.GetTransactionForTransientTokenJTI() and TransientTokenDataV2Api.GetTransactionForTransientToken() methods might not return payment data to the calling application.

Workaround: No known workaround.


Authorization Decline Webhooks Might Omit the submitTimeUtc Field

Ticket: EPS-42702

Description: Some merchants might find that authorization decline webhook events do not include the submitTimeUtc field. This issue can occur when an authorization request is declined, resulting in webhook payloads that omit the field entirely rather than returning it with a null value.

Audience: Merchants that consume authorization decline webhooks through an affected gateway integration.

Technical Details: For some declined authorization transactions, the payload.submitTimeUtc field might be omitted from the webhook payload. This issue affects payments.authorization.rejected and payments.authorization.status.rejected events and can occur for declined transactions such as those returned with response code 51 and reason INSUFFICIENT_FUND.

Workaround: No known workaround.


Apple Pay Transactions Might Fail Due to Payment Data Decryption Errors

Ticket: EPS-42773

Description: Some Apple Pay transactions might fail during processing and return a decline response instead of being authorized successfully. This issue occurs during the decryption of Apple Pay payment data, preventing the transaction from being completed.

Audience: Merchants that accept Apple Pay payments through affected integrations.

Technical Details: Some Apple Pay transactions might fail with reason code 102 and the error message Unable to decrypt encrypted_payment_data. In affected transactions, the publicKeyHash cannot be validated, resulting in the error Invalid public key hash and preventing the Apple Pay payload from being decrypted.

Workaround: No known workaround.


American Express Transactions Might Be Declined for Non-US and Non-Canadian Billing Addresses

Ticket: EPS-42788

Description: Some merchants might experience declined American Express transactions when customers use billing addresses outside the United States or Canada. Although the billing address contains a valid postal code, the transaction might still be declined during authorization, preventing the customer from completing the purchase.

Audience: Merchants processing American Express transactions through an affected processing connection when customer billing addresses are outside the United States or Canada.

Technical Details: Some American Express transactions with non-US and non-Canadian billing addresses might be declined with reason code 236 and processor response code 19. Although the billing postal code is present in the transaction data, it might not be included in the required authorization field used during transaction processing.

Workaround: No known workaround.


Comment Field in Virtual Terminal Might Still Appear When Disabled

Ticket: EPS-42796

Description: Some merchants might see the comment field displayed on Virtual Terminal receipts even when the Comment Display feature is disabled.

Audience: Merchants using Virtual Terminal that have disabled the Comment Display feature.

Workaround: No known workaround.


Unsupported Processor Configuration Might Appear in Portfolio Management

Ticket: EPS-42942

Description: Some merchants might see an unsupported processor configuration associated with their portfolio. This issue can occur when processor settings are updated through internal management processes, resulting in a processor being associated with a portfolio that does not support it.

Audience: Some merchants using affected portfolio configurations in .

Workaround: No known workaround.


Editing a Subscription Plan Might Trigger Immediate Billing and Reset the Billing Schedule

Ticket: EPS-43012

Description: When merchants edit an existing subscription and change it to a different plan or tier, the subscription might immediately charge the customer and reset the recurring billing date. As a result, the billing cycle might change unexpectedly, and the customer can be charged sooner than intended.

Audience: Merchants using Subscription Management or Recurring Billing that modify an existing subscription by changing its plan or tier.

Technical Details: When a subscription is updated with a different plan or tier, the subscription start date might be reset, causing the billing cycle to restart. As a result, an immediate charge might be processed and the recurring billing date recalculated based on the date of the change.

Workaround: To adjust pricing without changing the billing schedule, merchants can update only the subscription amount rather than changing the plan or tier. If a plan or tier change is required, merchants can cancel the subscription and create a new one with the billing date.


Payment Requests Using Flex and Unified Checkout Transient Tokens Might Return HTTP 400 Errors

Ticket: EPS-43048

Description: Some merchants might receive an HTTP 400 response when submitting POST /pts/v2/payments requests using Flex or Unified Checkout transient tokens, even when capture context generation and transient token creation complete successfully.

Audience: Merchants without a TMS profile that submit REST API payment requests using Flex or Unified Checkout transient tokens.

Workaround: Contact your account representative to discuss temporary TMS enablement.


Confirmation Step Might Appear When Disabled in Unified Checkout

Ticket: EPS-43205

Description: Some merchants might see the confirmation step briefly appear during checkout even when showConfirmationStep=false is configured to skip it. Although the checkout flow continues as expected, the confirmation step might momentarily render before being bypassed.

Audience: Merchants using Unified Checkout that have configured checkout to skip the confirmation step.

Workaround: No known workaround.


Unified Checkout Webhooks Might Not Be Delivered Due to Documentation Configuration Issues

Ticket: EPS-43340

Description: Some merchants might not receive Unified Checkout webhooks after completing webhook configuration. This issue can occur when merchants follow webhook configuration guidance that results in an incorrect Message-Level Encryption (MLE) key configuration, preventing webhook delivery.

Audience: Merchants in the European Union that use Unified Checkout webhooks.

Technical Details: Some Unified Checkout webhooks might not be delivered when the configured MLE key does not match the values used during webhook delivery.

Workaround: No known workaround.


Debt Repayment Transactions Might Be Processed as Standard Debit Transactions

Ticket: EPS-43598

Description: Some merchants might find that debt repayment transactions are processed as standard debit transactions even when debt repayment indicators are included in the transaction request. Transactions complete successfully, but the debt repayment designation might not be recognized during transaction processing.

Audience: Merchants that process debt repayment transactions through an affected processing connection.

Workaround: No known workaround.


Google Pay Transactions Using Payer Authentication Might Fail with an Invalid XID Error

Ticket: EPS-43618

Description: Some merchants might be unable to complete Google Pay transactions when using Payer Authentication (3-D Secure). Transactions might fail with an invalid XID error even when a valid XID value is provided.

Audience: Merchants that use Google Pay with Payer Authentication (3-D Secure).

Technical Details: Some transactions might fail with the error message The field is invalid: xid even when the xid field contains a populated, correctly formatted value.

Workaround: No known workaround.

Last published: November 18, 2026

Not available for your audience

This page isn't available for your current audience selection.