Skip to main content
Upcoming — generated from the latest merged element source; documents unreleased development. Use the channel picker at the top of the sidebar for the docs of a published release.
In development — not yet part of a stable release. Belongs to the Payments group. Render <CardElement /> inside it (React), or call payments.create('card', { … }) on the handle (vanilla) — consumer props and on<Event> callbacks both go in the create options / JSX props.
Exclusive — when using CardElement, you can’t mount PaymentElement or CardFields in the same Payments handle: these are alternatives — mount one at a time; destroy it to mount another.

Preview

A live, interactive demo of this element with sample data:

Usage

Props

"compact" | "stacked"
Field arrangement: ‘stacked’ (default) puts the number on top with expiration and security code below; ‘compact’ is the classic single row — the number flexes, expiration and security code sit fixed-width to the right, all inside one visual container. Defaults to "stacked".

Events

Pass a callback in the create options (or React prop) to receive these.

onChange

The card fields changed — complete: true means all three are filled so the confirm can run; drive your pay button off it. brand is the detected card network. Signature: ((payload: { complete: boolean; brand: string; }) => void)

onLoaderStart

Fired the moment the element’s own loading skeleton has painted inside its frame — the earliest point a consumer-managed loading state can hand off without ever exposing a blank. Always precedes onReady; most consumers only need onReady. Signature: (() => void)

onReady

Fired once the element has booted and painted its first complete frame. Signature: (() => void)

onError

Fired when the element fails to load or crashes; the element shows its own error fallback. message is human-readable; framework refusals also carry code (e.g. HOST_SOURCE_FAILED, with sourceKey naming the failed hostState key) so hosts can switch on codes, never message text. Signature: ((e: { message: string; code?: string | undefined; sourceKey?: string | undefined; }) => void)

Methods

Call these on the element handle — the return of create (vanilla) or the component ref (React).

mount

Place the element on the page: appends its container to target (a CSS selector or an element) and starts loading. Nothing renders until this is called. React consumers never call it — the component mounts itself. Signature: (target: string | HTMLElement) => void

destroy

Remove the element from the page and release its frame and subscriptions. Safe to call more than once. React consumers never call it — unmounting the component does it. Signature: () => void

update

Change this element’s consumer props after mount — it re-renders with the merged props. React consumers never call it — updating the JSX props does the same. Signature: (options: Partial<CardElementProps>) => void

Styling

Each part below is a stable class name — safe to depend on. Restyle a part by mapping its class to a style declaration object under appearance.classes (properties camelCase or kebab-case, values as strings with units — the same shape as React’s style prop). The element renders in its own frame, so page stylesheets can’t reach it: these declarations are sanitized against a safe-property allowlist and injected inside the frame for you.
In React, pass the same object as the appearance prop on <Payments>; appearance also applies globally at WhopElements({ appearance }).