> 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/readme.md). # Verifone API Catalog
Cover imageCover image (dark)

Checkout

Accept cards, wallets and local payments via hosted pages or embedded iFramesCheckoutICON BLACK CROSS AND UP SELLING.svgBroken linkICON WHITE CROSS AND UP SELLING.svg

3D Secure

SCA-compliant cardholder authentication with frictionless and challenge flows3D SecureICON BLACK SECURITY.svgBroken linkICON WHITE SECURITY.svg

Customer

Store and manage shopper details in one placeCustomerICON BLACK CUSTOMER ID.svgBroken linkICON WHITE CUSTOMER ID.svg

eCommerce

Global payments, recurring billing and digital wallets — tokenized and complianteCommerceICON BLACK ECOMMERCE.svgBroken linkICON WHITE ECOMMERCE.svg

PayPal eCom

Process PayPal and alternative payments through a single, globally unified checkout integrationPayPal eCommerceICON BLACK PAYMENT METHODS LOCALIZATION.svgBroken linkICON WHITE PAYMENT METHODS LOCALIZATION.svg

Reporting

Programmatically retrieve and download settlement, transaction and financial reports from Verifone's cloud platformReportingICON BLACK REPORTING TOOLS.svgBroken linkICON WHITE REPORTING TOOLS.svg

Order

Manage hardware orders, provisioning, and merchant boarding via APIOrder ServiceICON BLACK ORDER NUMBER.svgBroken linkICON WHITE ORDER NUMBER.svg
--- # 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/readme.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.