Euro 3DS Liability Shift Checker
Evaluate explicit independently verified3DS liability-shift prerequisites by caller scheme/version/jurisdiction checklist, not authentication success alone or actual liability assignment. Missing/unknown evidence never establishes eligibility or absence of risk. Caller independently verifies edition, jurisdiction, applicability and one currency; screening does not establish legal compliance, coverage or bank approval.
Description
Authentication evidence and liability-shift conditions are separate from a successful payment.
Authentication evidence and liability-shift conditions are separate from a successful payment.1
A checklist of caller criteria records missing and unknown requirements without deciding actual liability. Use Euro 3DS Liability Shift Checker to evaluate the supplied inputs under the model explained below.
When to use Euro 3DS Liability Shift Checker
Use Euro 3DS Liability Shift Checker to evaluate the supplied inputs under the model explained below. Establish the currency and minor-unit convention, measurement period and applicable transaction or institution context.
How to use Euro 3DS Liability Shift Checker and understand its results
- Establish the currency and minor-unit convention, measurement period and applicable transaction or institution context.
- Enter Caller three ds liability criterion ids, Caller three ds liability required flags, Observed three ds liability satisfied flags, Known three ds liability evidence flags using the field table and validation rules below, then run the tool.
- Read Missing, Unknown, Complete; interpret the units, signs, ordering and unknown-value placeholders described below.
- Correct reported input errors and rerun. Apply successful results according to their specific meanings and check the assumptions before using them in a decision.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| callerThreeDsLiabilityCriterionIds | Caller three ds liability criterion ids | array of string | Required; constraints below |
| callerThreeDsLiabilityRequiredFlags | Caller three ds liability required flags | array of number | Required; constraints below |
| observedThreeDsLiabilitySatisfiedFlags | Observed three ds liability satisfied flags | array of number | Required; constraints below |
| knownThreeDsLiabilityEvidenceFlags | Known three ds liability evidence flags | array of number | Required; constraints below |
Enter unique nonblank criterion IDs and aligned binary required, observed-present and known arrays. Return required known-absent IDs as missing and required unknown IDs as unknown, in caller order. complete is true only when at least one criterion is required and neither list has entries; all-zero requirements return false. No installed 3DS/network eligibility rules or legal liability decision occurs.
complete=anyRequired AND missing.empty AND unknown.empty Use the field order, units and branch conditions described above.
| Output field | Meaning | Value type |
|---|---|---|
| missing | Missing | array |
| unknown | Unknown | array of string |
| complete | Complete | boolean |
{
"input": {
"callerThreeDsLiabilityCriterionIds": [
"criterion-a",
"criterion-b"
],
"callerThreeDsLiabilityRequiredFlags": [
1,
1
],
"observedThreeDsLiabilitySatisfiedFlags": [
1,
0
],
"knownThreeDsLiabilityEvidenceFlags": [
1,
0
]
},
"output": {
"missing": [],
"unknown": [
"criterion-b"
],
"complete": false
}
}Limitations and assumptions
A checklist of caller criteria records missing and unknown requirements without deciding actual liability. Apply the exact scope and assumptions explained above.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are explained above; extremely large inputs or outputs can also be rejected. Input errors differ from successful false results, empty match lists and unknown-evidence placeholders.
Alternative or Complementary methods
Use PSD2 SCA Exemption Thresholds Checker for a related task: Strong customer authentication exemptions combine amount limits with additional eligibility conditions.
Use PCI Dss Merchant Levels Volume Validation Requirements Lookup for a related task: Merchant validation requirements depend on the payment brand, program and reporting period.
References
-
Euro 3DS Liability Shift Checker — tool.io
Similar or alternative tools
- PSD2 SCA Exemption Thresholds Checker
Strong customer authentication exemptions combine amount limits with additional eligibility conditions.
- PCI Dss Merchant Levels Volume Validation Requirements Lookup
Merchant validation requirements depend on the payment brand, program and reporting period.