...
Expand | ||
---|---|---|
| ||
|
Expand | |||||
---|---|---|---|---|---|
| |||||
Example of a 3DS transactionctresponsive_ch
|
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
JSON Object – browserInfo
JSON Object – accountInfo
JSON Object – customerInfo (billToCustomer | shipToCustomer)
JSON Object – merchantRiskIndicator
|
...
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Credentials on File (CoF) – Initial Subscription Payment
Credentials on File (CoF) – Subsequent Subscription Payment
|
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Credentials on File (CoF) - Initial Recurring Payment
Credentials on File (CoF) - Subsequent Recurring Payment
|
Expand | |||||
---|---|---|---|---|---|
| |||||
Credentials on File (CoF) - Validation Request
|
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Credentials on File (CoF) - Initial Payment for Token Storage
Credentials on File (CoF) - Subsequent Payment for Token Storage
|
...
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Credentials on File (CoF) - Initial MoTo Payment
Credentials on File (CoF) - Subsequent MoTo Payment
|
...
Expand | ||
---|---|---|
| ||
The requirement of the card brands to mark recurring transactions correctly is already an older requirement; we provided information on this in January 2019. In the course of the PSD2-SCA implementation, this will become fully mandatory so that recurring transactions can be clearly identified and the downstream systems can recognize why 3D Secure was not processed in these cases. Since in those cases no end customer actively participates in the payment process, as consequence, the implementation is mandatory for all merchants. Below you will find our descriptions & details, i.e. in the first step the initial payment from the store has to be marked as CredentialOnFile and based on that the recurring batch transactions will follow. ***initial shop transaction or AccountVerification: On our application page the correct initial flagging (CredentialOnFile) is described for different use cases and the following chapter + scenario will apply to you. Chapter: 2. use cases for transaction identification ***Recurring batch submission Chapter: Batch usage of the interface In the batch request there exists the "transactionID" on the one hand and in addition the "schemeReferenceID" as well, please use for the transfer only the transactionID. Examples - Batch Versions 1.2: The Acquirer Identifier must be transferred in batch format by using the TransactionID, i.e. you will receive the schemeReferenceID (in the case of a 3DS-1.0 fallback transaction as TransactionID) for the initial 3DS-2.X transaction. This value must then be included in the batch format so that all recurring payments are correctly identified. The field cardHolder must be present but can also be submitted as an empty field. ***Token/PCN Mandate - SchemeReferenceID You can try to submit payments without using a schemeReferenceID, but we cannot prevent card transactions to be declined. |
...
3. Test 3D Secure 2.0 via Computop |
---|
Take the opportunity to test 3D Secure 2.0 now! While not all downstream systems currently offer 3D Secure for testing, you can perform a test simulation within Computop Paygate. This allows you to perform 3D Secure authentication including different return values. Please proceed as follows for testing:
|