Skip to main content
The card element renders a card number, expiration, security code, cardholder name, and postal code. Sensitive fields (card number, expiration, security code) are encrypted and never touch your page. Configure card inside Checkout for the recommended integration path, or mount standalone when you need a compact card-only form.

Standalone example

Fields

  • cardNumber: PAN input. Renders the brand icon as you type. Configurable via fields.cardNumber — label, placeholder, iconStyle, autoFocus, and the accepted-brands controls (acceptedBrands, acceptedBrandsPlacement). Full surface on the card reference.
  • cardExpiration: month/year expiration input. Configurable via fields.cardExpiration.
  • cardSecurityCode: 3- or 4-digit CVC/CID. Configurable via fields.cardSecurityCode.
  • holderName: native cardholder name input. Configurable via fields.holderName (label, placeholder, disabled, hidden).
  • postalCode: native billing postal code input. Configurable via fields.postalCode. Default visible; hide with fields.postalCode.hidden: true.
See the Card reference for every knob.

Submitted value

Calling card.submit() (or triggering it from Checkout) encrypts the card fields and fires onSubmit:
Forward the full envelope (encrypted fields plus riskData and browserInfo) to your server verbatim. Never send raw card data from the browser and never try to unpack the encrypted* values.

Inside Checkout

The nested card key accepts the same options the standalone element accepts (minus elementType). Values arrive on the Checkout envelope as value.card.

Next steps

Best practices

Configure fields, gate your Pay button, and match your brand.

Reference

Full options and value reference.
Last modified on July 29, 2026