Skip to main content

Two paths to checkout

Henry supports two checkout modes. Pick the one that fits your needs:

Hosted Checkout

The checkoutUrl returned by cart.create is a fully hosted checkout page. Redirect, iframe, or popup. Henry collects shipping, payment, and tax.

Headless Checkout

Call checkout.purchase from your server with card token and shipping info. Henry processes payment and places the order with the merchant. You own the UI completely.

Hosted Checkout

Overview

Henry’s Hosted Checkout is the fastest way to add commerce capabilities to your application. With our hosted checkout solution, you can accept payments without handling sensitive payment data or building complex UI components. Simply embed our checkout experience via iframe, webview, or redirect.

Why Choose Hosted Checkout?

Launch in Minutes

Pre-built UI components and hosted pages get you live fast

Zero PCI Burden

We handle all payment security and compliance requirements

Mobile Ready

Responsive design works seamlessly across all devices
Perfect for: Startups and businesses that want to move fast and launch quickly.

How It Works

Hosted Checkout uses a simple redirect or embedded iframe approach:

Embed options

The simplest integration - just redirect the user to the checkout URL.
Want to match your color scheme? Append ?theme=<light or dark> to the checkout URL.

Headless Checkout

Overview

Headless Checkout gives you full control over the buyer experience. You collect shipping and payment info in your own UI, then call Henry’s API server-side to process payment and place the order. To securely collect card details in your UI, use the Card Element. It tokenizes the card and returns a cardToken to pass to cart.checkout.purchase.
Keep card tokenization on the client to stay out of PCI scope. The Card Element collects and tokenizes card data inside an isolated iframe, so raw card numbers never touch your servers. A server-side POST /card/tokenize REST endpoint also exists (it is not exposed through the SDK), but sending the raw PAN, CVV, and expiry through your own backend brings your systems into PCI DSS scope (typically SAQ D). Only reach for it if you already operate a PCI-compliant environment.

Why Choose Headless Checkout?

Full UI Control

Own every pixel of the checkout experience - no iframes, no redirects

Your Brand

Seamlessly match your existing design system and user flows

Server-Side

All payment processing happens on your server - no client-side exposure
Headless checkout requires special enablement. Contact us to get set up.

How It Works

Call cart.checkout.purchase from your server with the buyer’s shipping and card info.

Next steps

Order Management

List and track orders after checkout - filter by status, cartId, and more

Universal Cart

Learn how to build and manage the cart before checkout