Resolve exact authority
Send the final purchase plus signed authority evidence. The engine verifies identity, bindings, budgets, consent, expiry and replay outside the model.
Bind a supported signed final approval to the exact Stripe PaymentIntent request your executor is about to send—and keep authority locked until MandateShield checks the resulting PaymentIntent. The exclusive executor still makes an idempotent provider operation; MandateShield does not move money or replace native provider controls.
First commercial profile: supported signed approval → Stripe PaymentIntent. Exclusive credential routing is required. The public lifecycle is test-only and contacts no provider.
EXECUTION INTEGRITY TRACE
#ms_interactive
Provider call attempts
$1,499.00Exactly $124.00 at Rail Merchant, bound to one provider request.
The provider request changed after approval. Amount, payee and request digest no longer match.Attempted payee: Unknown Seller
BINDING_MISMATCHExact boundary implemented today
THE GAP
A policy engine may allow “$124 at Rail Merchant.” A changed checkout, compromised tool, concurrent worker or retry can still present a different request—or attempt the approved request again.
MandateShield rechecks exact bindings before granting one fresh permit claim and then checks supported terminal evidence without trusting the caller's result. The exclusive executor and provider idempotency remain required for the downstream operation.
BEST FIT TODAY
MandateShield is deliberately narrow. It is useful when a signed approval and the final provider call are produced by different components, so neither artifact alone proves that the approved checkout is the request the executor actually attempted.
For teams translating a supported signed closed-payment approval into Stripe: bind the approval facts, connected account, payee, amount, currency and exact form body before the executor attempts the idempotent request.
Inspect the exact boundary →REQUEST SUBSTITUTIONFor changed carts, tool compromise and concurrent workers: the permit binds the exact provider account, operation and body digest. A changed request cannot reuse the approved handoff.
Inspect the exact boundary →AMBIGUOUS PROVIDER RESULTSFor timeouts and conflicting reports: do not restore spendable authority or authorize a blind retry until MandateShield checks the configured Stripe record or canonical x402 chain evidence.
Inspect the exact boundary →Do not buy it for generic guardrails. Native budgets, seller scopes, fraud controls and payment credentials stay with their providers. MandateShield is for the remaining signed-approval to exact-provider-request gap on the explicitly supported path.
ACCOUNT EMERGENCY STOP
Once PAUSE commits, no competing strict reservation, PROCESSOR CONSUME or execution-permit redemption can win afterward on a correctly integrated MandateShield-mediated path.
Evidence does not go dark during an incident. Receipt verification, provider outcome reporting and reconciliation remain available so already-submitted attempts can reach a truthful final state.
Deployment boundary: provider credentials must be absent from the agent runtime and alternate provider egress must be blocked. MandateShield cannot stop a bypass path or recall an execution step that committed before PAUSE.Open the execution control center →CHOOSE THE REAL EXECUTION PATH
The primary integration path is supported signed approval to Stripe. The x402 profile is retained for compatibility and evidence testing; it is not presented as a replacement for x402's native authorization, nonce, idempotency or settlement controls.
Carry the approved checkout facts into the connected account, payee, amount, currency and exact Stripe form-body digest without giving the agent a payment credential.
Send the final purchase plus signed authority evidence. The engine verifies identity, bindings, budgets, consent, expiry and replay outside the model.
Reserve the approved authority, consume it once and redeem a provider-bound permit at the credential-isolated execution edge. Only the fresh atomic winner receives MandateShield permission; the executor must still make one idempotent provider operation.
MandateShield checks the configured provider API or canonical chain evidence without relying on the caller's asserted result. Final state and evidence are bound into a portable ES256-signed execution receipt verifiable with published keys.
WHAT CHANGES
FREE LIVE VALIDATOR
Change the money or permissions with plain controls, then attack the same mandate five ways. The results come from the live public analysis API—not a recorded animation. Sandbox results are never executable.
Live policy engine · no account · no card or personal data
Run one decision or test the same mandate against five boundary failures.
Run the sample or change a constraint to see the verdict.
EXACT SUPPORT BOUNDARY
Terminal outcome checking exists only for configured Stripe PaymentIntents and the supported x402 EIP-3009 profile. Three narrow input projections help normalize selected AP2, x402 and MPP fields. TAP, UCP, ACP and custom values are labels only; none of these labels establishes protocol conformance.
Inspect the exact support matrix →const reservation = requireAllowed(await verifier.verifyAuthority({
envelope: purchase,
evidence: signedAuthority
}))
const consumed = await processorGate.transitionExecutionAuthorization({
receipt_id: reservation.signed_receipt.receipt_id,
compact: reservation.signed_receipt.compact,
expected_envelope: purchase,
expected_audience: processorAudience,
action: "CONSUME",
idempotency_key: `${attemptId}:consume`,
provider_binding: exactProviderRequest
})
const redeemed = await providerGate.redeemExecutionPermit({
permit_id: consumed.execution_permit.permit_id,
compact: consumed.execution_permit.compact,
expected_audience: processorAudience,
expected_request: exactProviderRequest,
idempotency_key: `${attemptId}:redeem`
})
if (!redeemed.provider_submission_permitted || redeemed.idempotent_replay) {
throw new Error("No fresh provider claim")
}
const outcome = await submitOnceToProvider({
idempotencyKey: redeemed.provider_idempotency_key
})
const terminal = await providerGate.reportProviderSubmission({
provider_submission_id: redeemed.provider_submission_id,
permit_id: redeemed.permit_id,
claim_id: redeemed.claim_id,
payment_reference: outcome.reference,
outcome: outcome.status,
occurred_at: outcome.occurredAt,
provider_observation: outcome.boundedObservation
})
// independent_verification means independent of the caller's assertion.
// It is not an independent organization, certification or audit.
if (!terminal.independent_verification) {
await queueProviderReconciliation(redeemed.provider_submission_id)
throw new Error("Outcome remains fail-closed")
}
verifyExecutionReceipt(terminal.execution_receipt)ONE FRESH CLAIM, CHECKED OUTCOME
Production adds an immutable mandate registry, account-pinned issuer keys, one-time challenges, atomic cumulative-budget reservations and durable receipts. A first-party Gate adapter runs inside customer infrastructure, isolates the provider credential and is responsible for one idempotent bound provider operation. Hosted Reconcile then checks the exact configured Stripe PaymentIntent or x402 chain outcome without trusting the caller's report. The hosted API is designed not to collect card data, customers must not submit it, and MandateShield does not settle money.
Availability is part of the safety tradeoff: if hosted strict verification or reconciliation is unavailable, MandateShield does not grant a new authorization and an unresolved outcome stays reserved. That can pause checkout. Integrations should queue safely or route to manual review; they must not fail open or blindly retry a provider operation.
COMPARE PUBLISHED PLAN COST
Set your volume and average purchase. The calculator finds the lowest-cost published plan and shows effective software cost per 1,000 decisions and as a share of the average purchase. It makes no savings, loss-prevention or return-on-investment claim.
Lowest-cost planGrowth
Estimated monthly cost$499.00
Software cost / 1,000 decisions$0.998
Share of average purchase0.0008%
This is published plan pricing divided by your stated volume and average purchase value. It is not a loss estimate, ROI claim or promise of savings.
Choose Growth →START FREE, SCALE BY USAGE
No sales call, seat fee or annual contract. Create the account, choose a plan and create role-scoped live keys in the dashboard. Machine includes 50 million decisions for $4,999 per month.
LEARN WITHOUT A SALES CALL
Practical, evergreen references for merchants and developers implementing autonomous checkout.
Generate and verify a signed, deliberately non-executable decision.
AP2 · X402 V2 · MPP BRIDGESee every mapped binding and the non-executable assurance boundary before account-pinned authority is signed.
X402 V2 COMPATIBILITY PROFILESee exactly what MandateShield adds around EIP-3009—and what remains native x402 authorization, nonce, idempotency and settlement behavior.
PROVIDER-VERIFIED STRIPEVerify exact account, amount, currency, reference and status from Stripe itself; treat webhooks only as wake-up signals.
RELEASE INTEGRITYVersioned SHA-256 checksums, offline verification and SPDX SBOM.
BUYER AND AI DUE DILIGENCEOne graded index for the correct product identity, official external records, repeatable checks and facts not yet established.
FREE ASSESSMENTTen questions produce a prioritized, shareable action plan.
FREE BUILDERCreate fresh mandate JSON, copy curl and run the live engine.
MERCHANT GUIDESeven controls to verify before accepting an agent purchase.
AP2 CHECKLISTBinding, expiry, replay and audit evidence for production.
MCP IMPLEMENTATION GUIDEConnect callable tools to a consume-once authorization boundary.
VERSIONED EVIDENCEMap deterministic, cryptographic and execution claims to public contracts and machine-readable evidence.
ARCHITECTURE COMPARISONSee which gap remains after budgets, scoped credentials and provider-native controls have already done their job.
ARCHITECTUREExactly what MandateShield checks—and what it does not claim.
RESOURCE LIBRARYImplementation paths for every team and failure mode.
PLAIN-ENGLISH ANSWERS
No. MandateShield checks bounded authority for autonomous AI-agent purchases. It does not collect IBANs, signatures, debit instructions or payment credentials.
No. MandateShield at mandateshield.com is AI-agent payment-authority software operated from Bern, Switzerland. It is unrelated to Mandatory Shield Company at mandatoryshield.com, its Brussels team, ShieldAD/ADSecure and Microsoft Active Directory auditing.
MandateShield binds a supported signed final approval—including its narrow AP2 closed-payment projection—to the exact provider request a credential-isolated executor is about to send. It reserves approved spend, grants one fresh online claim and can check the configured Stripe or x402 outcome without trusting the caller's report before producing a signed execution receipt.
MandateShield is built first for teams turning externally approved AI-agent checkout facts into Stripe PaymentIntent requests while keeping credentials behind one exclusive executor. A supported x402 EIP-3009 profile remains available as a narrow compatibility profile, not as a claim that MandateShield replaces its native controls.
No. It adds a stateful execution-authority and reconciliation layer. A credential-isolated gateway must freshly redeem the exact permit before attempting an idempotent provider operation. That single-winner claim is not an exactly-once provider-delivery guarantee. MandateShield can then verify a configured Stripe PaymentIntent or x402 chain outcome; card processing, fraud scoring, sanctions screening and settlement remain with existing providers.
No. The API evaluates policy metadata such as amount, currency, merchant, consent and expiry. Payment credentials stay with the merchant's payment provider.
Yes, within one account when provider credentials and egress are isolated behind the required MandateShield Gate. The interlock atomically blocks new strict reservations, PROCESSOR consumption and permit redemption on MandateShield-mediated paths. Receipt verification, outcome reporting and reconciliation remain available. It cannot stop alternate customer infrastructure that bypasses the Gate or recall a step that committed before the pause.
The normalized policy envelope can label AP2, TAP, UCP, x402, MPP, ACP or custom inputs, but a label is not protocol conformance. Built-in field projection is limited to an AP2 terminal closed-payment projection, x402 v2 PAYMENT-REQUIRED input and one explicitly profiled MPP Payment charge challenge. Terminal outcome profiles exist only for configured Stripe PaymentIntents and the documented x402 EIP-3009 path. Full AP2 checkout chains, MPP method credentials, Visa TAP trust stores and the remaining protocol stacks stay external.