Prearranged fields for card number, expiration, and security code. Create with payments.create("card"), enable your payment button from onChange, and confirm with payments.createConfirmationToken(). Card numbers remain in PCI-isolated hosted fields. layout supports stacked (default) and compact.
Mounts inside Payments. Pass props and callbacks through the create options or React props.
Exclusive.CardElement is an alternative to PaymentElement or CardFields in this Payments handle. Mount one at a time. Destroy it before mounting another.
Mounts inside a WhopPayments scope. The three card inputs as one unit, PCI-isolated by the tokenizer, so the number, expiry and security code never enter your process.
Mount inside <Payments>, which owns the charge and the confirmation token. <Payments> itself mounts inside <WhopElements>. Reach for it when the form takes a card and nothing else: it registers itself as the collection surface, so createConfirmationToken tokenizes it with nothing else wired.
Fires when card fields change. complete becomes true after the buyer fills all three. Use it to enable confirmation. brand is the detected card network. funding is the detected funding type (credit, debit, or prepaid), null until the number identifies one. issuingCountry is the lowercase two-letter code of the country the card was issued in, null until the number identifies one.Signature:((payload: { complete: boolean; brand: string; funding: string | null; issuingCountry: string | null; }) => void)
Runs when the element fails to load or crashes. The fallback remains visible. Use code for programmatic handling. sourceKey identifies a failed host-state source.Signature:((e: { message: string; code?: string | undefined; sourceKey?: string | undefined; }) => void)
Removes the element and releases its frame and subscriptions. You can call it more than once. React removes the element automatically.Signature:() => void
Style these parts through appearance.classes. Use camel case or kebab case for property names and include units. Page stylesheets can’t reach the element’s frame. The framework validates each declaration before injecting it.
Class
Targets
.whop-Card
Card element root
.whop-CardError
Card configuration error pane
.whop-CardField
Card number, expiration, or security code field
.whop-CardFieldError
Card validation message
.whop-CardFieldGroup
Stacked card number, expiration, and security code fields
.whop-CardFieldInput
Bordered PCI input container
.whop-CardFieldInputFocused
Focused PCI input container
.whop-CardFieldInputInvalid
Invalid or incomplete PCI input container
.whop-CardFieldRow
Compact card number, expiration, and security code row
Renders immediately and validates as the buyer types. The brand appears once the number identifies one. state.isComplete turns true when all three fields are valid.
Use it instead of WhopPaymentElement when card is the only method you take. Mounting both is a conflict: the controller mints from one collecting surface.
createConfirmationToken(billingDetails:) needs a cardholder name for the card lane, so pass one or mount an address element that collects it.
publicKey is an advanced escape hatch. Omit it and the SDK fetches the account’s tokenizer key.
Mount it inside a WhopPayments(accountID:charge:) scope, which creates the controller and hands it to its content. payments.buyer is the signed-in buyer once an email sign-in has proven one. WhopBrandingElement has to be on screen too, because Whop is merchant of record on these sales and createConfirmationToken refuses without it. Style with .whopElementsAppearance(_:). The module is Elements, not the wallet SDK’s WhopElements. See Getting started and Appearance.
Applied to the element’s outer View. For theming, prefer appearance.parts on the provider, which covers every element on this surface. Note the React Native part names are their own set today, not the web’s whop-* class names, so a web appearance object does not port across unchanged.
The three fields render together once the publishable key resolves. onChange reports complete when all three are valid, and the element shows its own per-field errors.
Card numbers never pass through your code. The fields are PCI-isolated native inputs, and the SDK hands Whop a token, so your app stays out of PCI scope.
Mounting this makes the provider’s collection surface the card, so createConfirmationToken tokenizes it with no extra wiring. Do not mount it beside a PaymentElement: exactly one collection surface is live at a time.
For a form where the three fields sit in your own layout, use CardFields instead.
Wrap your app in <WhopElements getToken={…}> once, then mount <Payments> around the elements. See Getting started and Appearance.
Assistant
Responses are generated using AI and may contain mistakes.