Release Notes

These release notes cover all releases to the production server for the week ending

February 20, 2026

.

Announcements

These are the announcements for

February 20, 2026

.

Webhooks version 1 will be decommissioned in April 2026. See Webhooks version 2 in the Developer Center.

Description: This release enhances the custom rules capability in Partner Risk Controls (PaRC) to include the below mentioned fields. This improvement will help us to better perform risk and fraud management using PaRC.

ICS_Credit Service
(Credit Type): contains
Standalone_refund
and
Followon_credit
.
Country Checks: Acquirer, Merchant, and Issuer country codes.
AFT: 24 Fields related to Account funding transactions, to set rules that restrict AFT transactions using PaRC
Mandate: Does not apply.
Audience: Users of PaRC.
Benefit: Customers and acquirers can now be better prepared against merchant and transaction frauds performed using stand-alone credit and AFTs.
Technical Details: None.
Important Dates: Released to production February 17, 2026.

Description: This release fixes minor, intermittent errors in velocity aggregation that were the result of a discrepancy in foreign exchange currency conversion.
Audience: Users of Partner Risk Controls.
Technical Details: None.
Important Dates: Released to production February 17, 2026.

Description: For Pay by Link, if a payment link is set to Inactive
status, customers who already paid using that payment link can no longer view their receipts. The receipt URL returns red banner error with HTTP 500
.
Audience: Customers paying merchants that use Pay by Link.
Technical Details: None.
Workaround: Merchant can set the payment link back to Active
status to allow the receipt page to load successfully, however, that also activates the payment link again.

Description: In the Visa Platform Connect card processing setting, portfolio users cannot manage the aggregator ID information because the placeholders are disabled.
Audience: Portfolio users who manage merchants processing transactions from third-party vendors.
Technical Details: None.
Workaround: Merchants can use the following API field to send the aggregator ID in the transaction requests.

REST API Field
:
aggregatorInformation.aggregatorId

Simple Order API Fields
:

ccAuthService_aggregatorID

ccCaptureService_aggregatorID

ccCreditService_aggregatorID

octService_aggregatorID