Launch agents your customers can trust with their money
Your customers define their guardrails, agents can operate across existing merchants and rails, but funds only settle on delta if your customer's intent and policies were satisfied.
Agents can act flexibly, but delegated spending only settles if intent and policies were satisfied.
No merchant-side integration required
Works with cards, bank payments, and stablecoins
Private by default, with auditable receipts when needed
Complex policy constraints enforceable
Agents can already browse, decide, check out, and trigger transfers. The bottleneck is ensuring that what happened is what the user, enterprise, or platform actually approved.
Agents are capable
Approving a card authorization is easy. Enforcing that the agent bought the right thing, released funds for the right reason, or satisfied the right policy is the hard part.
But outcomes are unchecked
Without that, agentic payments cannot scale. And that is the gap delta closes at settlement.
delta closes the gap
Built for platforms that need to offer enterprise-grade control, security, and trust guarantees
User
Sends spending request along with policy
Platform
Finds item(s), verifies user's policy is satisfied
Makes purchase (with card/bank)
Merchant
Receives purchase via existing payment rails
Proves it made a purchase that satisfied the user intent's policy
User's intent settles, platform is paid
User
Sends spending request along with policy
Platform
Finds item(s), verifies user's policy is satisfied
Makes purchase (with card/bank)
Merchant
Receives purchase via existing payment rails
Proves it made a purchase that satisfied the user intent's policy
User's intent settles, platform is paid
Keep your stack. Add the missing control layer.
Integrate once at the platform layer. Keep your agent runtime, processor, issuer, card program, orchestration stack, and counterparties. delta adds the missing verification and settlement control layer.
How to integrate
Define the policy types your platform needs.
Connect your platform to delta via a simple API.
Launch on existing merchants and existing rails.
Platform Backend
Your existing infrastructure
via OpenAPI
Gateway
Settlement Layer
Agentic Commerce Stack
delta is compatible with the protocols that capture intent and the rails that move money.
Start integrating01 Does delta compete with AP2, ACP, Verifiable Intent etc.?
No, delta represents a different layer of the agentic payments stack.
From a payments perspective, agents introduce one major challenge: mismatches between the person's intent and the agent-provided outcome may differ.
Protocols developed by companies such as Google, Stripe, and Mastercard address this problem with merchant-side authorization standards.
delta focuses on spender-side settlement enforcement, ensuring that funds only move if the user's intent or policy was satisfied.
Authorization tells the ecosystem what the agent was allowed to do. Settlement enforcement decides whether money is actually allowed to leave.
02 How are settlement guarantees enforced?
Our SDK lets you write any policy or settlement constraints in the form of a zero-knowledge proof. This includes constraints about information on the internet, e.g. data from the merchant, thanks to zkTLS which is natively integrated into our SDK.
The delta settlement layer only settles transactions that were accompanied by a valid proof, meaning that policy was satisfied.
03 How does delta enforce settlement guarantees across external payment rails?
Agentic payments platforms on delta use a programmatic escrow model, consisting of the following steps:
1. Commit: the user or enterprise sends a signed intent with amount and policy to the platform. This amount is in stablecoins on delta.
2. Execute: the platform makes the purchase(s) on traditional payment rails.
3. Settle: the platform collects relevant data about the purchase(s) verifiably, and uses delta's proof engine to trigger the movement of the user's committed funds on the settlement layer.
The guarantee is that user funds cannot move unless the intent was satisfied.
The platform technically spends before the user's funds have moved. However, the platform can easily check whether a transaction will satisfy the user's intent before pulling the trigger, so their risk is minimal.
04 How can there be zero merchant integration?
delta is spender-side, and agentic payments platforms on delta use regular APIs to interact with merchants. zkTLS ensures that intent matching is cryptographically bound to the information provided by the merchant.
Therefore delta-based platforms do not require merchants to adopt any new standard or infrastructure, and for platforms using authorization standards such as AP2, no incremental integration is required.
Launch agents your customers can trust with their money.
To move from agent-assisted flows to unattended execution, you need more than approval and spend limits. You need settlement guarantees. delta gives platforms the control layer that makes money-moving agents deployable now.