PRE-SIGN CONTROL PLANE · NO CUSTODY · FAIL-CLOSED

Let agents act.
Keep authority.

Varyntiq checks the exact payment an AI agent wants to make before an existing wallet or processor signs it. Your team sets the policy; your signer keeps the keys.

Varyntiq is an independent decision layer. It returns a bounded ALLOW, BLOCK or REQUIRE_APPROVAL result before execution, with a receipt that can be checked by the signer.

POST /check
{
  "agent_id": "procurement-agent",
  "amount": 4800,
  "currency": "USD",
  "payee": "new-vendor.example",
  "rail": "x402"
}
REQUIRE_APPROVAL risk 68/100
NEW_PAYEE · AMOUNT_ANOMALY · OWNER_POLICY
receiptvnt_8f31…b90dbound & auditable
The missing step in agentic commerce
Agent intent→Policy decision→External signer→Payment rail
01Decision before signatureThe signer only sees an intent that has passed policy.
02Keys stay with youVaryntiq never takes custody or settles funds.
03Evidence for every callStable reason codes and an expiring receipt make the decision auditable.

CONTROL BEFORE EXECUTION

A neutral authorization layer for every payment rail.

The agent proposes. The control plane decides. Your existing wallet or processor remains the only component that can sign and move money.

01

Evaluate intent

Check amount, budget, payee, frequency, price history, duplication and the context that led to payment.

02

Return one decision

ALLOW, BLOCK or REQUIRE_APPROVAL, with stable reason codes that an agent can act on.

03

Prove what happened

Issue an expiring receipt bound to the request, endpoint, payee, amount, rail, network and asset.

LIVE-SAFE DECISION PROOF

See the dangerous path stop before signing.

Run five payment intents against the same policy. The demo is deterministic, transparent and safe: it never connects to a wallet, signs a transaction or moves money.

0 scenarios run0 blocked€0 moved
policy decisionrisk 08/100
ALLOW

Known recipient, exact amount and fresh nonce.

KNOWN_PAYEEWITHIN_BUDGETFRESH_NONCE
intent hashcalculating…
receiptdemo_—
signaturecreating…
browser verificationchecking…

This demo creates and verifies an ephemeral browser signature. No wallet, private key or real payment is involved.

Varyntiq stops here.
The external signer verifies this decision before paying. A fail-closed path blocks when the proof is missing or changed.

Ready for a full proof run.

POLICY + RISK

Controls owners can understand.

Budgets & limitsPer transaction, day and month
Duplicate protectionIntent replay and changed-data detection
Payee controlsAllowlist, blocklist and new-provider review
Trust provenanceOptional application-assigned trust class
Price anomaliesHistorical range and trusted-quote checks
Velocity controlsFrequency and burst detection
Prompt-to-payment defenseSignals for injected or redirected intent

SECURITY BOUNDARY

Built to reduce authority, not hide it.

Varyntiq sits before the component that can sign. That makes the boundary clear to engineering, security and finance teams.

VARYNTIQ DECIDES
  • Exact amount, asset, network and recipient
  • Budget, velocity and duplicate checks
  • Approval, denial and expiry rules
  • Signed decision receipt and reason codes
YOUR SYSTEM EXECUTES
  • Wallet or payment processor keeps the keys
  • Existing settlement and reconciliation remain yours
  • No private key, credential or balance is sent to Varyntiq
  • Missing or changed proof fails closed

VERIFIABLE TODAY

A working service, not a concept deck.

ProofControlled evaluationAvailable after qualification
BoundaryNo custody or signingExisting wallet stays in control
0funds or private keys heldAuthorization only

Published evidence separates local conformance from deployment and customer claims. No customer adoption, endorsement or guaranteed fraud prevention is claimed.

Technical adapters and evaluation material are shared privately after qualification. The public surface describes the boundary without exposing implementation details.

INTEGRATE WHERE AUTHORITY CHANGES HANDS

One pre-sign check.

decision = varyntiq.check(payment_intent)

if decision.status != "ALLOW":
    stop_or_request_approval(decision)

# wallet remains outside the control plane
wallet.sign(payment_intent, decision.receipt)
HTTPS /checkMCP toolx402 pre-signFail-closed client

CONTROLLED INTEGRATION PILOT

Protect one real agent payment flow.

We connect the authorization step to one existing payment path, define owner policy and prove the result with an auditable test pack.

Pilot scope
  • One agent workflow
  • One pre-sign integration
  • Policy configuration
  • Attack and failure-path validation
from€2,500
Request a controlled pilot ↗ Public qualification only. Do not submit credentials, wallet details, customer data or confidential architecture. Final scope and terms agreed before work begins. Automated billing is not active.