Integration into a web page
The use of the Payline Payment Web Page interface is the simplest and fastest solution, Payline takes care of all the complexity related to authentication and the impact on the payment request.
Payline provides no impact for merchant integration:
- authentication with or without challenge ;
- the fallback to 3DS V1 if necessary.
3DS V2 incompatible avec PWP V1
It is not possible to initiate a 3DS V2 payment from the V1 Payment Web Pages.
There is no merchant impact at the level of server-to-server exchanges between the merchant and Payline.
- The merchant: calls the doWebPayment service ;
- The merchant instantiates the widget on his payment pages (in In-shop mode) ;
- The merchant calls getWebPaymentDetails.
Process for V2 payment pages:
Valuation of web services
No modification of the web service is necessary.
We present below the new functions brought by 3DS V2.
None of these functions are mandatory.
The merchant must use a Payline web service version greater than or equal to 21 to benefit from the new functions linked to 3DS V2.
The merchant can specify the authentication mode it wishes to see applied to this transaction.
|threeDSInfo.threeDSReqPriorAuthMethod||Highly recommended to promote firctionless. 3DS authentication method of the last payment.|
|threeDSInfo.threeDSReqPriorAuthTimestamp||Datetime||Highly recommended to promote frictionless. Date and time of the last payment.|
|merchantScore||Score calculated by the merchant and sent to CB (check with CB for more details)||Retrieving the type of authentication actually performed.|
|authentication3DSecure.resultContainer||object Json encoded base64||Retrieving a character string containing the result set of authentication parameters.|
|authentication3DSecure.authenticationResult||PARES or CRES|