FILTER BY TAG

Fixed Issues

Follow-On Credit Transactions Now Progress Correctly after RTC Flag Updates
| 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

Account Updater Configuration Can Now Be Saved at the Merchant Level
| 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 Business Center. Previously, when users selected the default Account Updater template, the template loaded without configuration values, and merchant-level Account Updater settings were not saved after users selected
Apply
. Account Updater configurations can now be applied and saved correctly.
Audience
Portfolios that use the Account Updater product in the Business Center.
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 23, 2026

TRN Is Now Retained across Credit Transactions
| 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. Cybersource 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