You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+31Lines changed: 31 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,34 @@
1
+
## [2.3.0]
2
+
3
+
## Added
4
+
5
+
### On demand feature for 3DSv2
6
+
7
+
> **This on-demand feature is for testing purposes only and will not be available in production**
8
+
9
+
#### Request
10
+
11
+
We've added a new parameter `Requested3DSVersion` (not mandatory) that allows you to choose between versions of 3DS protocols (managed by the parameter `SecureMode`). Two values are available:
12
+
*`V1`
13
+
*`V2_1`
14
+
15
+
If nothing is sent, the flow will be 3DS V1.
16
+
17
+
The `Requested3DSVersion` may be included on all calls to the following endpoints:
18
+
*`/preauthorizations/card/direct`
19
+
*`/payins/card/direct`
20
+
21
+
#### Response
22
+
23
+
In the API response, the `Requested3DSVersion` will show the value you requested:
24
+
*`V1`
25
+
*`V2_1`
26
+
*`null` – indicates that nothing was requested
27
+
28
+
The parameter `Applied3DSVersion` shows you the version of the 3DS protocol used. Two values are possible:
29
+
*`V1`
30
+
*`V2_1`
31
+
1
32
## [2.2.0]
2
33
- 3DS2 integration with Shipping and Billing objects, including FirstName and LastName fields
3
34
The objects Billing and Shipping may be included on all calls to the following endpoints:
0 commit comments