Solidgate logo in black and white.

Payment form

What is a payment form?

Payment form is the user-interface element that collects and submits a customer's payment details during an online transaction. It captures card data, billing information, and any extra fields the transaction needs, then hands that data to a for processing.
Payment forms appear at checkout on sites and inside mobile apps. The form is the data-entry component itself, distinct from a (the full checkout screen it sits on) and the gateway (the service that transmits what it collects). Because it's the last thing a customer touches before money moves, its design has a direct effect on how many started checkouts turn into completed sales.

Key facts: fields a payment form collects

A payment form gathers the data a processor needs to authorize a charge:
  • Card details: card number, expiry date, and
  • Billing information: cardholder name and
  • Order context: amount, currency, and sometimes shipping details
  • Authentication inputs: data that feeds verification when a transaction requires it

Types of payment forms

Payment forms differ mainly by how they're integrated into a checkout:
  • Hosted form: loaded on the payment provider's domain, which keeps raw card data off merchant servers and narrows scope.
  • Embedded (inline) form: rendered inside the merchant's own page through an iframe or SDK, so checkout stays on-brand while card data still flows to the provider.
  • Redirect form: sends the customer to the provider's page to enter details, then returns them to the merchant once payment finishes.

Why it matters

A payment form is the last step before a sale completes, so small design choices change revenue:
  • A long or unclear form raises cart abandonment, because customers drop off when asked for data they didn't expect.
  • Inline validation and specific error messages let a customer fix a mistyped card number instead of re-entering the whole form.
  • paired with a hosted or embedded form keeps raw card data off merchant servers and lowers PCI compliance burden.
  • Fewer input errors feed a higher , since clean, correctly formatted data produces fewer avoidable declines.

Related terms