CAIN-42 MCPGateAGENTIC AI 75 · #48
Browser payments without exposing card details
KERNEL announced payments using protected credentials in authorised browser sessions.
Last reviewed 2026-11-11
Agentic AI 75 / #48
2026 status: Product release · Category: Payments
The 2026 development
KERNEL announced payments using protected credentials in authorised browser sessions.
The governance gap
The safety property is that raw card data never enters model context. That requires a credential boundary the agent cannot read through, plus a mandate that limits what the credential may be used for.
Where CAIN-42 fits: Moat 2 — Security-Context Continuity
Core question: Does authority survive every boundary? Identity, scope and delegation are carried across tools, agents, memories and systems.
Keep the credential in a broker the agent cannot read, and authorise each use against a mandate. CAIN's broker and payment-mandate paths separate the agent's intent from the secret that fulfils it.
How the wiring works
- Store the credential outside the agent's context.
- Authorise the payment against a bounded mandate.
- Release the credential only to the authorised checkout flow.
- Record the authorisation without recording the secret.
What is real today
LIVE A public route in this deployment exercises this mechanism today, within its stated scope.
The mandate guard and broker concepts are real; the hosted demo uses fixed presets. No card network, wallet or KERNEL integration exists.
| Component in this repository | What the module says it is |
|---|---|
cain/commerce/mandate_guard.py | Agent Payment Mandate Guard. |
keystone/broker.py | BROKER KEYSTONE: CAIN Action Credentials. Agents get a credential for one action, never a standing key. |
cain/browser/agent_firewall.py | Browser Agent Action Firewall. |
Descriptions are the first line of each module's own docstring, read without importing it. A module path is a pointer into this repository, not a hosted endpoint. Its existence is checked by the test suite; its status for this use is the label above.
Check it yourself
- Run the live payment-mandate demo
/api/v1/payment-mandate-guard/presets - Fire a live decision through the CAIN-42 pipeline
/fabric/try— the same enforcement path every product sits behind.
Commercial package
| Offer | Agent Checkout Mandate Review |
|---|---|
| Buyer | Merchants, PSPs and browser vendors |
| Price (proposal) | $3,500–$7,500 per review |
| Bundle | Commerce & Payments — Delegated spending with a ceiling and a receipt. |
| Operator stream | Stream 2 of the 10-stream operator playbook |
Fintech, commerce platforms, marketplaces, treasury teams is the bundle buyer. The entry offer for this bundle is Payment-mandate review; browser-agent checkout review; the range is $2,500–$7,500 per review; integration from $10,000. A price on this page is a proposal, not a validated rate, and no customer is claimed.
Buy this as a product or service
CAIN-A75-048 — Agent Checkout Mandate Review DELIVERABLE
A bounded engine run on the buyer's sample: findings, a written report, and a SHA-256 artifact manifest. The manifest is unsigned: it is not a signature and not an attestation.
Kind: Assessment · Price (proposal): $3,500–$7,500 per review · Lead time: 5 business days.
Open the product page · all 75 products
What this page does not claim
What this page is not. CAIN-42 is not affiliated with, endorsed by, integrated into, or shipped with the organisation named in the 2026 item. The item is public context; the page describes how CAIN-42 would govern that class of capability. No page here claims a customer, a partnership, a certification, a patent, or a production integration. Prices are proposals. Built by a three-person team.