Knox In development

Payment infrastructure for agent-driven software

Payments your coding agent can integrate.

Knox is building one prescribed, Stripe-compatible payment integration that an agent can install and verify in your existing app.

See how it works

The intended Knox workflow

From an existing checkout to a verified change.

The agent prepares a focused integration change. Your team stays in control of what ships.

Connectors show the sequence from Inspect to Integrate to Verify.
  1. 01Understand the app

    Inspect

    The agent finds the current checkout, key order data, and the path that fulfills the order.

  2. 02Make a focused change

    Integrate

    It makes a Knox-specific code change on a branch and prepares a pull request.

  3. 03Check the result

    Verify

    It runs a test payment and checks integration status for a person to review.

Knox is in development. Supported frameworks and payment flows will be defined as the product takes shape.

What Knox is building

A consistent integration. More options behind it.

These are product directions, not claims that every capability is available today.

01 Planned

Processor flexibility

Add or change supported processors behind one merchant integration, with traffic moved in stages.

One integration pattern
02 Exploring

Payment-path resilience

Evaluate ways to reduce unnecessary synchronous dependence on Knox while keeping the merchant integration simple.

Architecture under evaluation
03 Architecture commitment

VGS-backed card-data boundary

Knox is being built on VGS Collect and a VGS outbound proxy. Raw card data goes to VGS while Knox routes aliases.

Implementation in progress

VGS is a PCI DSS Level 1 service provider. Merchant validation and scope depend on the final implementation.