The approval and completion layer for agent-initiated purchases

VotexPay gives AI agents a controlled way to browse, prepare purchases and ask for payment, while the user keeps approval, card control and the final completion signal.

Mission

Agents are getting better at research, comparison and checkout preparation. Payments are still the trust boundary. VotexPay makes that boundary explicit: an agent can request a purchase, the user can approve it, and the agent can verify that the user completed it.

Agent-native interface

MCP tools, REST endpoints and SDKs for goals, browser actions and purchase status.

Human approval

One-time handoffs and step-up authentication keep the spending decision with the account holder.

Completion signal

The agent polls a recorded status instead of inferring that a merchant checkout succeeded.

Architecture

The user and the external agent meet at the VotexPay API and MCP layer. VotexPay applies authentication, scopes, approvals and audit, then uses Supabase, Stripe, an isolated browser and the available payment rails.

User

Controls approvals, step-up authentication, trusted devices and payment limits.

External agent

Connects over MCP or REST with a scoped API key. Can browse, research and request actions.

VotexPay API and MCP

Approval and completion layer. Validates keys, binds approvals, runs agent jobs and exposes one-time payment handoffs.

Supabase

Auth, Postgres, row-level security

Stripe

Saved-card payments, 3DS, webhooks

Isolated browser

Sessions, actions, screenshots

Policy and audit

Scopes, approvals, request IDs

Payment rails

User-paid handoffLiveVault card fillComing soonSupplier APIComing soonLink US/CanadaLiveVirtual cardsComing soon
VotexPay never places raw card data in agent context. User-paid purchases complete on the merchant site; vault card filling is available only in test/preview today.

Current status

Live features are available in production. Test features require the test or preview deployment. Coming-soon items are listed so expectations match the product.

Supabase authentication

Live

Email and password, TOTP, passkeys and trusted devices.

Scoped API keys

Live

Hashed at rest, revocable, and limited to the scopes an agent needs.

MCP and SDKs

Live

Streamable HTTP MCP server plus Python and TypeScript SDKs.

Isolated browser sessions

Live

Explicit actions in isolated sessions with SSRF and prompt-injection guards.

Agent Runs

Live

Pro+ only. Dual-LLM planner and quarantined extractor for browsing and research. They do not execute merchant payments.

Saved-card payments

Live

Stripe payments with human approval, 3DS and webhooks. This charges VotexPay, not a merchant checkout.

User-paid purchase handoff

Live

Create purchase, one-time /pay/{token} approval, merchant checkout, user confirmation, agent status polling.

Platform security

Live

Security headers, CORS, request IDs, SSRF DNS guard, screenshot blocking after card fill, RLS and test/prod Supabase separation.

PCI vault and autofill

Coming soon

Coming soon. Basis Theory test vault, PCI autofill, unified card entry, vault purchase fill and submit. Production PCI is disabled.

Stripe Elements filling

Coming soon

Iframe card field filling and select action. Merchant CAPTCHAs and 3DS may require user handoff.

Link rail for US/Canada

Live

Live for eligible US/Canada Link wallets. The user connects Link in Settings and approves every spend in Link; VotexPay fills the one-time card server-side.

Supplier API rail

Coming soon

Reseller and supplier integration is planned but not built.

Stripe SPT and Forwarding

Coming soon

Pending. Not available today.

Virtual cards

Coming soon

Coming soon. Stripe Issuing was refused. Nium and Marqeta are not integrated.

Production card autofill

Coming soon

Coming soon. Production PCI is disabled. Arbitrary-merchant autonomous card purchases are not offered.

ChatGPT and Claude plugins

Coming soon

Planned for later. Use MCP or REST today.

Status reflects the production and test environments as of 6 November 2026. Agent Runs perform browsing and research. They do not execute real merchant payments.

What VotexPay is

  • An approval and completion layer for agent-initiated purchases.
  • A scoped API and MCP server for agents, with human-controlled payment decisions.
  • An isolated browser execution service for browsing, research and explicit actions.
  • A user-paid purchase handoff that works without PCI or an issuer.
  • A saved-card payment flow through Stripe, with human approval and 3DS.

What VotexPay is not

  • Not a bank, payment institution or card issuer.
  • Not an autonomous merchant checkout. Agents do not execute real merchant payments.
  • Not a production card vault today. PCI autofill is coming soon; Production PCI is disabled and Basis Theory is test only.
  • Not a virtual card provider. Stripe Issuing was refused and other issuers are not integrated.
  • Not a guarantee that a merchant will accept a payment, complete an order or avoid CAPTCHA and 3DS handoff.

Principles

User control

Approval stays with the user. Agents can request, prepare and hand off, but they cannot approve a payment or bypass step-up.

Least privilege

API keys are scoped, hashed and revocable. One key per agent, and only the scopes the task actually needs.

No raw card exposure

Card data is not placed in agent context. Production PCI is disabled, and no PAN is stored in the VotexPay database.

Auditable by design

Requests carry IDs. Purchases bind amount, merchant origin, card and session where applicable. Status is checked, not assumed.

Start building

Read the developer quickstart to create a key, connect MCP and make a user-paid purchase. The AI docs describe the tool map, approval flow and current limits for autonomous agents.