Dual Authorization Wire Threshold Checker
Audit actual distinct wire approval identities against caller inclusive amount threshold, counting repeated same-actor records once; identity authenticity, role authority, chronology and full payment authorization remain external.
Description
Dual authorization counts distinct approval identities rather than approval records.
Dual authorization counts distinct approval identities rather than approval records. An inclusive amount threshold determines the required count.1
The returned values include Dual approval required by caller policy, Distinct observed approval actor count, Satisfies caller distinct approval count. The How section below explains the calculation, input rules and interpretation.
When to use Dual Authorization Wire Threshold Checker
Use Dual Authorization Wire Threshold Checker when you need to evaluate the supplied records under the calculation and evidence rules below. No identity authenticity, authority, chronology or full payment authorization is supplied.
Prepare observed financial records and verified caller terms. Use one currency for integer minor-unit money and preserve leading zeros in identifier text. One basis point is 0.01 percentage points. Resolve dates, local clocks, counting rules and evidence flags as specified.
How to use Dual Authorization Wire Threshold Checker and understand its results
- Prepare observed financial records and verified caller terms. Use one currency for integer minor-unit money and preserve leading zeros in identifier text. One basis point is 0.01 percentage points. Resolve dates, local clocks, counting rules and evidence flags as specified.
- Enter wireAmountMinor, callerDualApprovalThresholdMinor, observedApprovalActorIds using the field table and calculation rules, then run the tool.
- Read dualApprovalRequiredByCallerPolicy, distinctObservedApprovalActorCount, satisfiesCallerDistinctApprovalCount. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| wireAmountMinor | Wire amount minor | number | Required |
| callerDualApprovalThresholdMinor | Caller dual approval threshold minor | number | Required |
| observedApprovalActorIds | Observed approval actor ids | list of string | Required |
Enter nonnegative safe-integer wire amount and threshold plus nonblank actor IDs, which may repeat or form an empty list. Preserve exact case and whitespace when counting identities. Return requirement flag, distinct count and count-sufficiency flag. Below threshold still requires one actor.
dual=amount≥threshold; count=number of distinct exact actorIDs; satisfied=count≥(dual?2:1) Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| dualApprovalRequiredByCallerPolicy | Dual approval required by caller policy | boolean |
| distinctObservedApprovalActorCount | Distinct observed approval actor count | number |
| satisfiesCallerDistinctApprovalCount | Satisfies caller distinct approval count | boolean |
{
"input": {
"wireAmountMinor": 1000,
"callerDualApprovalThresholdMinor": 1000,
"observedApprovalActorIds": [
"alice",
"alice"
]
},
"output": {
"dualApprovalRequiredByCallerPolicy": true,
"distinctObservedApprovalActorCount": 1,
"satisfiesCallerDistinctApprovalCount": false
}
} Limitations and assumptions
No identity authenticity, authority, chronology or full payment authorization is supplied.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Numeric lists are limited to 10,000 entries; string lists to 128 strings of at most 128 characters each. The rules above may impose smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.
Alternative or Complementary methods
Use Payment Fraud Velocity Rules Card Hour Tool: Transaction velocity counts events within a declared trailing interval for each card ID. The interval excludes its lower boundary and includes the as-of time. For a complementary task, use Positive Pay Issue Mismatch Checker: Positive-pay matching compares check ID, amount and payee against the issue ledger. Distinct mismatch witnesses explain a failed aggregate match.
References
Similar or alternative tools
- Payment Fraud Velocity Rules Card Hour Tool
Transaction velocity counts events within a declared trailing interval for each card ID. The interval excludes its lower boundary and includes the as-of time.
- Positive Pay Issue Mismatch Checker
Positive-pay matching compares check ID, amount and payee against the issue ledger. Distinct mismatch witnesses explain a failed aggregate match.