Checkouts

Create reusable payment experiences from managed templates.

Updated July 29, 2026

On this page

Before you start

A Recurrify merchant login
A Funnel source and ready router before live payment testing

A Checkout is a reusable, source-independent payment experience. It owns its template-driven layout, policies, and presentation overrides. The Funnel that uses it supplies the Source Page, hostname, delivery setup, offers, and router.

Create a Checkout

Choose a template

Open Checkouts, choose a managed template, and enter a name. The template provides the required payment structure and protected runtime controls; editable content and styling can be customized after creation.

Configure payment presentation

Open the designer to arrange editable sections and style the Checkout. Configure appearance overrides and policy links from Checkout settings. Runtime-owned payment components remain protected by the selected template.

Save and publish

Choose Save to store the draft, then Publish to make that exact saved revision available to new sessions. Unsaved changes are never published. Publishing queues and caches a screenshot used by Funnel graph thumbnails.

Use it in a Funnel

Add the Checkout to any eligible Funnel and select the router in the Funnel's General tab. Source branding and delivery are resolved from that Funnel. A Funnel can contain at most one Checkout, and every path after payment must finish at a terminal Thank-you Page.

Publishing a Checkout refreshes every saved Funnel that references it. New sessions use the new published revision; in-flight sessions stay on the runtime revision with which they started.

Accept wallets and PayPal

When the active Funnel can route to an Express-enabled Stripe MID, Checkout offers Wallet or PayPal beside card entry. The secure Stripe sheet renders Apple Pay, Google Pay, or PayPal only when that method is eligible for the current browser and transaction. Recurrify never infers availability or renders a simulated wallet button.

Wallet authorization is completed inside Stripe, then the payment is finalized through the same Recurrify operation ledger as card payments. A returned redirect resumes automatically in the original tab. Reusable card-backed wallet methods remain pinned to the original Stripe MID for renewals; Recurrify does not cascade a provider-owned wallet reference to another gateway.