JSON Object
threeDSPolicy
threeDSPolicy
| Key | Format | Condition | Description |
| skipThreeDS | string | O | Indicates whether and under which conditions authentication should be skipped or performed as data share only (dataOnly). By default, all transactions and SCA exemptions will be requested through EMV 3DS if not specified otherwise. Values accepted: · thisTransaction · outOfScope · dataOnly |
| threeDSExemption | object | O | Object detailing requested SCA exemptions. |
| challengePreference | string | C | Indicates the merchant’s challenge preference for this transaction during 3DS authentication. Mandatory only after a Soft Decline to re-trigger the transaction with 3DS and challenge mandated. Default value noPreference. Values accepted: noPreference noChallenge requestChallenge mandateChallenge Note: This parameter is ignored when SCA Exemption requested (threeDSExemption parameter is present). |
threeDSExemption
| Key | Format | Condition | Description |
| exemptionReason | string | M | Designates the type of SCA exemption (e.g. Acquirer TRA or MIT) to be applied. Values accepted: · transactionRiskAnalysis · delegatedAuthority · merchantInitiatedTransaction · lowValue Note: Acquirer exemptions and Merchant Initiated Transactions (MIT) may be also requested through an authorization without authentication (i.e. EMV 3DS or EMV 3DS Data Only). Note: merchantInitiatedTransactionis only valid in combination with credentialOnFile. |
| merchantFraudRate | integer | O | Merchant fraud rate in bps taking into account all Merchant sites and card volumes, calculated as per PSD2 RTS Article 19. The merchant fraud rate is optional and has to be calculated by the Acquirer. The submission of this data point might be beneficial to increase the level of confidence of the ACS/issuer into the ongoing transaction. Also, Issuers may use it to decide if a merchant should be eligible for the white listing exemption. |
Schema
{
“$schema”: “http://json-schema.org/draft-07/schema#”,
“$id”: “https://www.computop-paygate.com/schemas/threeDSPolicy.json”,
“title”: “threeDSPolicy”,
“description”: “3DS Policy”,
“type”: “object”,
“properties”: {
“skipThreeDS”: {
“type”: “string”,
“enum”: [“thisTransaction”, “outOfScope”, “dataOnly”]
},
“threeDSExemption”: {
“type”: “object”,
“properties”: {
“exemptionReason”: {
“type”: “string”,
“enum”: [“transactionRiskAnalysis”, “delegatedAuthority”, “merchantInitiatedTransaction”, “lowValue”]
},
“merchantFraudRate”: {
“type”: “integer”,
“minimum”: 1,
“maximum”: 99
}
},
“required”: [“exemptionReason”],
“additionalProperties”: false
}
},
“additionalProperties”: false
}
Beispiel – Anforderung SCA-Ausnahme
{
“skipThreeDS”: “outOfScope”,
“threeDSExemption”: {
“exemptionReason”: “merchantInitiatedTransaction”,
“merchantFraudRate”: 4
}
}
Beispiel – neue Auslösung nach Soft Decline
{
“challengePreference”: “mandateChallenge”
}
