API Changelog - 2026-07-28: Summary
The threedsPassThrough.version field for Visa, Mastercard, and Maestro payment
methods no longer restricts accepted 3-D Secure versions to the enum 2.1.0 /
2.2.0 — any 2.x.x version string is now accepted.
POST /v1/payments — Create Payment
The threedsPassThrough.version field for Visa, Mastercard, and Maestro
payment methods has been updated to accept any 3-D Secure 2.x.x version.
Previously, only 2.1.0 and 2.2.0 were valid values (enforced as an enum).
The field now validates against the pattern ^2\.\d+\.\d+$, meaning versions
such as 2.3.0 or 2.3.1 are also valid. This is a non-breaking, additive
change — existing integrations sending 2.1.0 or 2.2.0 continue to work
without modification.
| Property | Details |
|---|
| Name | paymentMethod.visa.threedsPassThrough.version |
| Location | Request body (Visa) |
| Type | string |
| Required | Yes |
| Format | Pattern ^2\.\d+\.\d+$ — enum removed, pattern added |
| Example | "2.2.0" |
| Property | Details |
|---|
| Name | paymentMethod.mastercard.threedsPassThrough.version |
| Location | Request body (Mastercard) |
| Type | string |
| Required | Yes |
| Format | Pattern ^2\.\d+\.\d+$ — enum removed, pattern added |
| Example | "2.2.0" |
| Property | Details |
|---|
| Name | paymentMethod.maestro.threedsPassThrough.version |
| Location | Request body (Maestro) |
| Type | string |
| Required | Yes |
| Format | Pattern ^2\.\d+\.\d+$ — enum removed, pattern added |
| Example | "2.2.0" |