Skip to navigation
Core resources

Customers

Store a customer and reuse them across payments.

Status: contracted_test. Customers are in the generated API Reference; only sk_test_* mode is promised.

A Customer represents a buyer you bill more than once. Create, retrieve, update, delete (not available for US Stripe Connect stores), and list are all served. Attach metadata (a flat string map) to carry your own identifiers, and reference the customer from a Checkout Session or a Payment Intent.

Payment methods on a customer

A customer’s saved payment methods are read through the one contracted customer-scoped route:

  • GET /v1/customers/{id}/payment_methods — nested list

The top-level /v1/payment_methods namespace, including its filtered-list alias, is unavailable for merchant-public keys. See Payment methods.

The full request/response shape is in the API Reference.

Hidden from the public API

Each item below is hidden because it does not follow the Stripe parity ADR (ADR 0004 as amended). The hidden public /v1 registry lists every hidden item. Public /v1 answers a hidden operation as an unknown URL, refuses a hidden request parameter or value with Stripe’s invalid_request_error, and omits a hidden response key.

  • the query parameter search of GET /v1/customers (HIDE0-046)