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.

September 2026


Production releases for the weeks ending September 4 to September 25, 2026: features, fixed issues, and known issues.

September 25, 2026

These release notes cover releases for the week ending September 25, 2026.

No customer-facing features were released this week.

Follow-On Credit Transactions Now Progress Correctly after RTC Flag Updates

Ticket: RM-47953

Description: This release fixes an issue that could cause follow-on credit transactions to remain in a Pending status after the Real-Time Clearing (RTC) flag changed from N to Y.

Audience: Merchants processing follow-on credit transactions through an affected processing connection.

Technical Details: Previously, some follow-on credit transactions remained in a Pending status after the RTC flag was updated. Transaction status now progresses correctly when the RTC flag changes to Y.

Important Dates: Released on September 23, 2026.


TRN Is Now Retained across Credit Transactions

Ticket: RM-48424

Description: This release resolves an issue that could cause Transaction Reference Number (TRN) inconsistencies for follow-on and standalone credit transactions when a merchant did not provide a TRN in the credit request. now retains the original authorization TRN throughout the transaction lifecycle, providing consistent transaction linking and simplifying reconciliation.

Audience: Some merchants processing credit transactions through any impacted processing connection.

Technical Details: Previously, when a merchant did not provide a TRN in a credit request, the processor received a different TRN than the one associated with the original authorization. The TRN sent to the processor now matches the original authorization TRN, and merchants can view the original authorization TRN in the P74V-prefixed online message for the credit authorization request.

Important Dates: Released on September 24, 2026

There are no known issues this week.

September 18, 2026

These release notes cover releases for the week ending September 18, 2026.

Support for issuerInformation.discretionaryData on FTT Processor

Ticket: RM-47810

Description: added merchant support for the issuerInformation.discretionaryData field when processing transactions through the FTT processor on the CTPV4 Gateway.

Mandate: Does not apply.

Audience: Merchants processing transactions through the FTT processor on the CTPV4 Gateway.

Technical Details:

  • Feature: Support for issuerInformation.discretionaryData
    • Products: FTT processor, CTPV4 Gateway
    • Tech Details: Added support for the issuerInformation.discretionaryData field when processing transactions through FTT processor connections. This feature is now supported in this locale:
      • Latin America and Caribbean (LAC)

Important Dates: Released on September 15, 2026.

Session Handling Improvements for SSO Merchant Switching and OTP Login

Ticket: RM-47464

Description: Two session-handling issues have been resolved:

  • Users using Single Sign-On (SSO) merchant switching can now successfully return to Portfolio Management after selecting Exit View. Previously, users could be returned to the previously selected merchant account immediately after exiting the switched session.
  • Users authenticating with one-time password (OTP) no longer experience intermittent login failures that require a second authentication attempt. Previously, some users were redirected to the sign-on page after successfully entering a valid OTP.

Audience: users.

Technical Details:

  • The fix introduces a one-time cookie that prevents the previous organization context from being reapplied following a successful switch-back operation.
  • A stale local storage value was not being cleared during session initialization. As a result, the application bootstrap process incorrectly treated newly authenticated OTP sessions as invalid and removed them. The fix clears the stale flag during session cleanup and adds safeguards to ensure the application initializes successfully.

Important Dates: Released on September 16, 2026.


ECP Transactions Now Return the Correct Response Code and Message for Smartpay Code 772

Ticket: RM-47510

Description: A defect was resolved that caused Electronic Check Processing (ECP) transactions processed through Smartpay to return an incorrect response when the processor returned code 772. Previously, mapped the processor response to code 150, resulting in the message Unknown error. now correctly maps the response to code 231 with the message Reason: Invalid DFI account number.

Audience: Merchants processing ECP transactions through the Smartpay processor.

Technical Details:

  • Processor Response Code: 772
  • Previous Response Code: 150
    • Message: Unknown error.
  • Updated Response Code: 231
    • Message: Reason: Invalid DFI account number.

Important Dates: Released on September 16, 2026.

Transaction History Might Not Display in Alternative Payments

Ticket: EPS-42339

Description: When merchants view the details of an authorization or captured payment transaction for Alternative Payments, the transaction history might not display any related credits that have been processed against the transaction. Additionally, the transaction history displays only the related capture and does not show associated transactions.

Audience: Merchants who use Alternative Payments.

Technical Details: None.

Workaround: Use an alternative transaction identifier, such as the Merchant Reference Number (MRN), to find related transactions.


BIN Data Unavailable for Follow-On Transactions in Reporting

Ticket: EPS-42464

Description: Merchants are unable to view Bank Identification Number (BIN) data for follow-on transactions in Reports. In the Transaction Request Report (TRR) and Payment Batch Detail Report (PBDR), BIN data is not displayed for settlements, credits, and other follow-on transactions.

Audience: Merchants who reference BIN number data in reports.

Technical Details: Follow-on transactions do not store or carry card number information. As a result, BIN data is unavailable for these transactions.

Workaround: No known workaround.


Some Account Updater Batches Remain in Processing State

Ticket: EPS-42645

Description: For merchants using Account Updater, some batches submitted on August 20, 2026, might remain in a Processing state and not complete automatically. As a result, batch results might be delayed until someone manually intervenes.

Audience: Merchants who use Account Updater.

Technical Details: None.

Workaround: No known workaround.


Transaction Search REST API Returns Empty installmentInformation Field

Ticket: EPS-42700

Description: When merchants use the Transaction Search REST API, the installmentInformation field is returned as empty, even when installment data exists for the transaction. As a result, merchants cannot retrieve installment information through Transaction Search.

Audience: Merchants who use the Transaction Search REST API.

Technical Details: The data source referenced by the Transaction Search REST API does not capture installment information. As a result, the installmentInformation field is always returned as empty. A change to the underlying data source is required to make this data available.

Workaround: Use the Transaction Details REST API, which correctly returns installmentInformation data.


Incorrect Merchant Country in Checkout Sessions Might Affect Apple Pay Availability

Ticket: EPS-42780

Description: When a merchant uses Invoicing or Pay By Link with Unified Checkout, the checkout session is generated with the merchant country set to US, even when the merchant is located in another country. As a result, non-US merchants might experience missing or unavailable Apple Pay payment options during checkout.

Audience: Non-US merchants who use Invoicing or Pay By Link with Unified Checkout.

Technical Details: The Unified Checkout Capture Context generated through Invoicing or PayByLink always populates the merchant country as US.

Workaround: Use a direct Unified Checkout (UC) or Flex session integration that supplies the correct merchant country when generating the session, rather than relying on the Invoicing or Pay By Link Capture Context generation path.


Acceptance Device List Cannot Be Exported to CSV

Ticket: EPS-42803

Description: When attempting to export the list of Acceptance Devices to a CSV file, merchants receive the error message Error: CSV not available and the export does not complete.

Audience: Merchants that use Acceptance Devices.

Technical Details: A front-end JavaScript issue prevents the CSV export from being generated successfully.

Workaround: No known workaround.


Intermittent Tap-to-Phone Payments Might Fail Before Reaching Transaction Processing Systems

Ticket: EPS-42847

Description: Some merchants located within the Democratic Republic of the Congo might experience intermittent Tap-to-Phone payment failures on their production Acceptance device fleets. Affected payments terminate before reaching , the acquirer, or the issuer. As a result, the transaction is not processed and does not appear in for investigation or reconciliation.

Audience: Merchants operating in the Democratic Republic of the Congo.

Technical Details: None.

Workaround: No known workaround.


Report Downloads API Returns Error When Using REST Client Java SDK v0.0.91 with P12 Certificates

Ticket: EPS-43139

Description: Merchants using JWT authentication with the /reporting/v3/report-downloads GET endpoint might receive a 401 UNAUTHORIZED_USER response when using the REST Client Java SDK v0.0.91 with a P12 certificate. As a result, report downloads cannot be retrieved through the API.

Audience: Merchants who upgrade to or use the REST Client Java SDK v0.0.91.

Technical Details: The issue occurs when using JWT authentication with the /reporting/v3/report-downloads GET endpoint in the REST Client Java SDK v0.0.91 and a P12 certificate.

Workaround: Revert to a previous version of the REST Client Java SDK. A fix is planned for a future release.

September 11, 2026

These release notes cover releases for the week ending September 11, 2026.

Boarding Page updates for the Chase Paymentech Processor

Ticket: RM-45908

Description: Boarding page enhancements provide greater flexibility for merchants using the Chase Paymentech processor, improving setup options.

Mandate: Does not apply.

Audience: Portfolio users onboarding merchants using the Chase Paymentech processor.

Benefit: Portfolio users can now access an additional terminalIds section on the Boarding Page when onboarding merchants for the Chase Paymentech processor with acceptanceType set to CardPresent or Both.

Important Dates: Released on September 10, 2026.

No customer-facing fixes were released this week.

There are no known issues this week.

September 4, 2026

These release notes cover releases for the week ending September 4, 2026.

No customer-facing features were released this week.

No customer-facing fixes were released this week.

Incorrect Invoicing Status Displayed in UI

Ticket: EPS-41938

Description: In some instances, an issue in the post-payment invoice update process prevents the invoice status from being committed to the database following successful payment authorization and processing. As a result, invoices remain in a Sent status instead of updating to Paid/Completed within the Invoicing UI.

Audience: Some merchants in CEMEA.

Technical Details: This issue occurs during post-payment invoice status persistence. Under specific conditions, a database deadlock can cause the invoice status update transaction to be rolled back, preventing the updated status from being committed.

Workaround: No known workaround.


Ticket: EPS-42410

Description: Receipt emails generated for Invoicing and Pay By Link transactions might occasionally display an incorrect merchant phone number. As a result, customers might be presented with inaccurate merchant contact information on receipt communications.

Audience: Some invoicing and Pay By Link merchants.

Technical Details: While payment pages display the merchant's intended customer contact information, receipt emails might display an incorrect merchant phone number due to the use of an unintended merchant contact record during receipt generation.

Workaround: Until a permanent fix is available, merchants can update the phone number associated with their Business Contact to match the customer-facing phone number configured in their merchant profile. This will help ensure consistent contact information is displayed in receipt emails.


Credit/Refund Action Causing Incorrect Transaction Status

Ticket: EPS-42369

Description: In certain cases, transactions that successfully complete a void operation after an initial timeout might not be accurately reflected in the transaction status. This issue might cause refund actions to be unavailable in the Transaction Details page, preventing merchants from initiating a refund through the user interface.

Audience: Some merchants and cardholders attempting void requests.

Technical Details: A transaction status synchronization issue might occur when a void request encounters a communication timeout during processing. As a result, the transaction record might not be updated to reflect its final state in some cases, even when the void is completed successfully.

Workaround: If refund options are unavailable for the affected transaction, merchants can issue a standalone credit to return funds to the customer.


Intermittent Token Management Service Failure for Recurring Billing

Ticket: EPS-42500

Description: Some merchants might experience intermittent failures when setting up recurring billing if a payment method is associated with a legacy Instrument Identifier that was created while nullable Instrument Identifiers were allowed in the TMS (Token Management Service) vault. These failures might occur when the legacy Instrument Identifier does not contain the card details required by the current vault configuration.

Audience: Merchants with legacy Instrument Identifiers created while nullable Instrument Identifiers were allowed in TMS.

Technical Details: None.

Workaround: No known workaround.


Invoicing Payment Receipts Sent to Business Contact Instead of Configured Email Address

Ticket: EPS-42538

Description: Merchants can configure Invoicing to send payment receipts to an alternative email address. However, payment receipts are currently sent to the business contact associated with the merchant account, even when an alternative recipient email is configured.

Audience: Merchants using Invoicing who have configured payment receipts to be sent to an alternative email address.

Technical Details: None.

Workaround: No known workaround.

Last published: November 18, 2026

Not available for your audience

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