PSD2 SCA Exemption Thresholds Checker

Screen transaction against caller PSD2 SCA exemption monetary AND independently verified extra eligibility policies; candidate not bank acceptance. Caller independently verifies edition, jurisdiction, applicability and one currency; screening does not establish legal compliance, coverage or bank approval.

Description

Strong customer authentication exemptions combine amount limits with additional eligibility conditions.

Strong customer authentication exemptions combine amount limits with additional eligibility conditions.1

Missing evidence can leave an exemption unresolved even when its amount limit is satisfied. Use PSD2 SCA Exemption Thresholds Checker to evaluate the supplied inputs under the model explained below.

When to use PSD2 SCA Exemption Thresholds Checker

Use PSD2 SCA Exemption Thresholds 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 PSD2 SCA Exemption Thresholds Checker and understand its results

  1. Establish the currency and minor-unit convention, measurement period and applicable transaction or institution context.
  2. Enter Transaction minor, Caller sca exemption ids, Caller exemption maximum minor, Caller additional eligibility required flags, Observed eligibility satisfied flags, Known eligibility evidence flags using the field table and validation rules below, then run the tool.
  3. Read Caller sca exemption candidate ids, Unresolved exemption ids; interpret the units, signs, ordering and unknown-value placeholders described below.
  4. 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 fieldMeaningValue typeRequirement
transactionMinorTransaction minornumberRequired; constraints below
callerScaExemptionIdsCaller sca exemption idsarray of stringRequired; constraints below
callerExemptionMaximumMinorCaller exemption maximum minorarray of numberRequired; constraints below
callerAdditionalEligibilityRequiredFlagsCaller additional eligibility required flagsarray of arrayRequired; constraints below
observedEligibilitySatisfiedFlagsObserved eligibility satisfied flagsarray of numberRequired; constraints below
knownEligibilityEvidenceFlagsKnown eligibility evidence flagsarray of numberRequired; constraints below

Enter transaction and exemption limits as nonnegative integer minor units up to 1000000000000, unique nonblank exemption IDs and a rectangular binary matrix of additional required criteria. Rows align with exemptions; columns align with binary satisfied and known arrays. An amount above a limit or a known absent required criterion excludes that exemption. Other exemptions with any required unknown evidence are unresolved; the rest are candidates, in caller order. A row of all zeros has no additional evidence requirements. No statutory limits, live fraud rate, coverage or actual authentication exemption is determined.

candidate=amount≤limit AND all required criteria known positive; unresolved=no contradiction AND required unknown

Use the field order, units and branch conditions described above.

Output fieldMeaningValue type
callerScaExemptionCandidateIdsCaller sca exemption candidate idsarray of string
unresolvedExemptionIdsUnresolved exemption idsarray
json
{
  "input": {
    "transactionMinor": 1000,
    "callerScaExemptionIds": [
      "low-value",
      "tra"
    ],
    "callerExemptionMaximumMinor": [
      2000,
      5000
    ],
    "callerAdditionalEligibilityRequiredFlags": [
      [
        1,
        0
      ],
      [
        1,
        1
      ]
    ],
    "observedEligibilitySatisfiedFlags": [
      1,
      0
    ],
    "knownEligibilityEvidenceFlags": [
      1,
      1
    ]
  },
  "output": {
    "callerScaExemptionCandidateIds": [
      "low-value"
    ],
    "unresolvedExemptionIds": []
  }
}

Limitations and assumptions

Missing evidence can leave an exemption unresolved even when its amount limit is satisfied. 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 Euro 3DS Liability Shift Checker for a related task: Authentication evidence and liability-shift conditions are separate from a successful payment.

Use Durbin Exemption Small Issuers Under$10B Note Lookup for a related task: Issuer exemptions depend on the applicable rule, assets and effective context.

References

  1. PSD2 SCA Exemption Thresholds Checker — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies