> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/api-reference/open-api-references/customer.md). # Customer The **Customer API** stores and manages shopper personal, billing, and shipping details in a single place. Each customer record is identified by a UUID that can be passed to other Verifone services — including Checkout, eCom, and 3D Secure — wherever customer data is required. {% hint style="info" %} A customer record is not always required to process a payment. However, providing one unlocks fraud scoring, APM support (PayPal, Klarna, and others), 3DS authentication, and richer reporting in [Verifone Central](https://docs.verifone.com/verifone-central-getting-started/verifone-central/commerce/reporting/orders-transactions-reports). {% endhint %} ## Environments
EnvironmentBase URL
EMEA Productionhttps://emea.gsc.verifone.cloud/oidc/customer-service
Americas Productionhttps://us.gsc.verifone.cloud/oidc/customer-service
New Zealand Productionhttps://nz.gsc.verifone.cloud/oidc/customer-service
Global Sandboxhttps://cst.test-gsc.vfims.com/oidc/customer-service
US Sandboxhttps://uscst-gb.gsc.vficloud.net/oidc/customer-service
## Authentication All endpoints support both Bearer (JWT) and Basic Auth. See your Verifone onboarding documentation for credential details. ## API Reference
NameDescriptionPageCover imageCover image (dark)Cover image (dark)Cover image (dark)
List & Create CustomersSearch for existing customers using RSQL filters, or create a new customer record.List\Create CustomersICON BLACK CUSTOMER ID.svgICON WHITE CUSTOMER ID.svgICON WHITE CUSTOMER ID.svgICON WHITE CUSTOMER ID.svg
Get, Update & Delete CustomersRetrieve a customer by UUID, update their details, or permanently delete a record.Get\Update\Delete CustomerICON BLACK PRICING UPDATE.svgICON WHITE PRICING UPDATE.svgICON WHITE PRICING UPDATE.svgICON WHITE PRICING UPDATE.svg
FAQsCommon questions about when and why to use customer records.faqsICON BLACK FRIENDLYNESS.svgICON WHITE FRIENDLYNESS.svg
## Quick Start {% stepper %} {% step %} ### Create a customer record Send a `POST /v2/customer` request with the shopper's billing details and your `entity_id`. {% endstep %} {% step %} ### Store the customer UUID The response returns an `id` field containing the customer UUID. Persist this value — you will pass it to Checkout, eCom, or 3DS when processing payments for this shopper. {% endstep %} {% step %} ### Use the UUID in downstream services Pass the customer UUID to the Checkout or eCom API request body wherever customer data is accepted. For 3DS flows, ensure billing address fields are populated on the record. {% endstep %} {% endstepper %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.verifone.com/api-reference/open-api-references/customer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.