Retrieve a single customer by ID from your Checkout Page account.

Returns one customer record directly by ID, without pagination.

Use list_customers first if you need to discover a customer ID by email or name. Use this tool when you already have the ID.

If the customer ID does not exist, returns a 404 error: "Customer not found".

For modification requests, show what's currently stored. The merchant can edit the customer record directly in the Checkout Page dashboard. The customer can also update their own details through the customer portal. For data deletion (GDPR/privacy), this requires human intervention in the dashboard.

The top-level address field is the billing address. The shipping.address field is the shipping address. These are separate and often don't match. When asked about "my address" without specifying which, present both addresses clearly labelled (e.g. "Billing address: … / Shipping address: …"). Don't return only one when both exist, and don't return the billing address in response to a shipping address question.

Customer records are identity/profile only — no purchase history, no transaction amounts.

Cross-tool routing:

To see what this customer has bought, use their id as the customerId filter on the transaction tools:

• list_payments(customerId: "...") — one-time purchases, digital products, invoices.

• list_bookings(customerId: "...") — event tickets and registrations.

• list_subscriptions(customerId: "...") — recurring billing.

Records do not overlap between transaction tools — a transaction only appears in one tool. No risk of double-counting when combining results.

For a complete customer picture, call get_customer for profile data, then query the transaction tools with the same ID.

Example uses (not exhaustive):

• "Fetch customer 6812fe6e9f39b6760576f01c" → direct lookup by ID

• "Show me the full customer profile for this customer ID" → returns all available fields

• "Show me the profile and orders for customer X" → get_customer for profile, then fan out to transaction tools with customerId

Example customer support uses:

• Customer asking what information is stored about them — look up by ID, return all stored profile fields. Note that customer records only contain profile data — for a complete picture of what's stored, also query the transaction tools with customerId to show their purchase history.

• Customer wants to update their address, phone number, or email — look up current profile, present what's on file. The merchant can edit the customer record directly in the Checkout Page dashboard. The customer can also update their own details through the customer portal.

• Customer says the name on their account is wrong — look up profile, check name field. If a shipping.name also exists and differs, present both. The merchant can update the name in the Checkout Page dashboard; the customer can update it via the portal.

• Customer requesting deletion of their personal data — GDPR/privacy request. Look up the full profile, show what's stored, and explain that data deletion requires human intervention in the Checkout Page dashboard.