Skip to main content
When you use Natural as a card vault, your agent can pay with a user’s saved debit or credit card at most online checkouts. It types a stand-in card, and Natural’s proxy swaps in the real one as the payment goes out, so your agent never handles the card number.

Coverage at a glance

These are rough estimates from our checkout audits as of November 2026. Supported means our proxy handles that checkout today; merchants can change their checkouts at any time.

Checkouts that work out of the box

Most checkouts send the card number to their payment processor as typed. These work through Natural whichever processor the merchant uses, with nothing extra to set up. That includes checkouts on Stripe, Shopify, Braintree, Square, Checkout.com, Authorize.Net and Worldpay, and merchants that take the card on their own servers.

Checkouts that encrypt the card

Many of the largest retailers and airlines encrypt the card in the browser before it leaves the page, which a plain proxy can’t get past. Natural supports these checkouts one by one: the proxy encrypts the real card exactly the way the checkout would.

Payment processors

Merchants

We add merchants every week. For setup on an encrypted checkout, see Encrypted card fields.

If a checkout doesn’t work

Merchants change their checkouts, and some may need support we haven’t built yet. If your agent can’t pay somewhere, report it with POST /merchant-reports and we’ll look at it. Never include card numbers or codes in a report. You can also open card sessions with requestAgentToken: true to fall back to an agent token where the proxy can’t reach the card.