Every payment-authority claim, classified and traceable.
A control-by-control map of what deterministically blocks, what only advises review, and what remains an external gateway responsibility.
EVIDENCE CONTRACT
Readable by people. Downloadable by machines.
Each row names the production behavior, canonical reason codes, current conformance vectors, source documents and limits of the claim. Vector IDs are drawn directly from the published vendor profile.
Registered mandate authorityDETERMINISTIC · Live verification loads immutable account-registered limits instead of trusting policy supplied by the agent.BLOCK
Exact fiat amount representationDETERMINISTIC · Currency-aware integer minor units prevent silent rounding and contradictory major/minor representations.BLOCK
Fiat amount, currency and merchant scopeDETERMINISTIC · The final amount, ISO currency and stable merchant identifier must remain inside the registered mandate.BLOCK
Exact atomic-asset scopeDETERMINISTIC · Atomic units, decimal exponent, asset, network and paid resource are compared exactly.BLOCK
Consent and authority expiryDETERMINISTIC · Explicit consent and a finite, current authority window are required for production.BLOCK
Signature and account-pinned key trustDETERMINISTIC · Signature math is combined with an account-pinned RFC 7638 thumbprint, issuer, audience and protocol match.BLOCK
Signed final-purchase bindingDETERMINISTIC · Signed authority must bind the canonical final purchase digest or the required TAP content digest.BLOCK
One-time challenge and signed freshnessDETERMINISTIC · Production evidence is bound to a server-issued, five-minute, consume-once challenge and signed time window.BLOCK
AP2 and TAP evidence-profile checksDETERMINISTIC · Supported AP2 SD-JWT+KB and normalized TAP HTTP-signature projections have protocol-specific binding requirements.BLOCK
Account-wide replay and persistenceDETERMINISTIC · A durable account-wide idempotency tombstone coordinates retries, concurrency and API-key rotation.BLOCK
Cumulative budget and execution stateDETERMINISTIC · Qualifying ALLOW decisions atomically reserve configured lifetime, UTC-day and UTC-month headroom.BLOCK
Signed receipt consistencyDETERMINISTIC · Receipt verification binds the decision core, canonical digest and top-level execution claims.BLOCK
Unknown strict constraint handlingDETERMINISTIC · Strict production refuses to approve a constraint field that the active verifier does not evaluate.BLOCK
Prompt-injection pattern signalADVISORY · Pattern matches can flag possible instruction override language but are not treated as proof of compromise.REVIEW
Privacy-thresholded community signalADVISORY · Cross-account observations provide contextual threat evidence only after the published privacy threshold.REVIEW
Processor-gateway enforcementEXTERNAL · The customer's trusted gateway must make CONSUME a hard precondition for its one provider submission.EXTERNAL
METHODOLOGY
How a row earns its classification
Deterministic means a normalized fact, cryptographic binding or durable state transition has a reproducible fail-closed outcome. Advisory means a contextual or heuristic signal may require REVIEW but cannot create authority. External means the control is a required customer integration responsibility outside the boundary MandateShield can enforce.
A conformance vector is cited only when its current canonical ID directly exercises the stated behavior. An empty vector list means the claim is derived from the published product contract, not that a portable test result has been invented. This matrix was reviewed on .
DETERMINISTIC · BLOCK
Registered mandate authority
Strict v2 withholds an executable reservation when no matching active registered mandate exists.
Evidence basis: The production invariant and public API contract require an active mandate version before authority can be established.
Machine identifiers
Reason codes: REGISTERED_MANDATE_REQUIRED
Conformance vectors: No directly corresponding portable vector is claimed.
Limits
The customer remains responsible for obtaining lawful user authority and registering the correct mandate.
Registration does not establish payment credential validity or settlement.
Exact retries recover the committed result; conflicting or concurrent reuse fails closed.
Evidence basis: One executable offline vector rejects an unsafe key; one stateful contract vector specifies account-wide recovery and conflicting reuse.
It does not establish an independent audit, accredited certification or correct customer deployment.
MandateShield does not process payments, validate payment credentials, screen sanctions or provide fraud insurance.
An authorization result does not prove every aspect of a transaction is legitimate.
Customer gateway enforcement, provider submission and settlement remain outside the hosted verification boundary.
PRIMARY SOURCES
Contracts and official specifications
First-party MandateShield contracts define shipped behavior. External protocol statements link to their primary official publishers. Accessing an external specification may be subject to its publisher's terms.