> 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/3d-secure.md). # 3D Secure The **3D Secure API** enables merchants to authenticate cardholders using the 3DS protocol, supporting both frictionless and challenge flows compliant with the Strong Customer Authentication (SCA) directive. Use these endpoints to initiate authentication lookups, manage JWT handshakes with the 3DS Client SDK, and query historical authentication records. {% hint style="info" %} All endpoints support both **Bearer (JWT)** and **Basic** authentication. See the [Authentication](#authentication) section below for details. {% endhint %} ## Environments {% tabs %} {% tab title="Production" %}
RegionBase URL
EMEAhttps://emea.gsc.verifone.cloud/oidc/3ds-service
Americashttps://us.gsc.verifone.cloud/oidc/3ds-service
New Zealandhttps://nz.gsc.verifone.cloud/oidc/3ds-service
{% endtab %} {% tab title="Sandbox" %}
RegionBase URL
Global Sandboxhttps://cst.test-gsc.vfims.com/oidc/3ds-service
Americas Sandboxhttps://uscst-gb.gsc.vficloud.net/oidc/3ds-service
{% endtab %} {% endtabs %} ## API Reference
NameDescriptionPageCover imageCover image (dark)
3DS AuthenticationList, count, and retrieve historical 3DS authentication records with rich filtering support.3DS AuthenticationICON BLACK RISK ASSESMENT.svgICON WHITE RISK ASSESMENT.svg
LookupInitiate cardholder authentication — triggers frictionless or challenge flow and returns the authentication outcome.LookupICON BLACK CONTACT INFORMATION.svgICON WHITE CONTACT INFORMATION.svg
JWTCreate and validate JWTs for the 3DS Client SDK authentication handshake.JWTICON BLACK TOKEN.svgICON WHITE TOKEN.svg
## Authentication All endpoints accept either authentication method on each request. {% columns %} {% column %} #### Bearer (JWT) Pass a signed JWT in the `Authorization` header: ```http Authorization: Bearer ``` The JWT must be signed with your Verifone-provisioned private key and must include `entity_id`, `sub` (user\_id), and `roles` claims. {% endcolumn %} {% column %} #### Basic Auth Pass base64-encoded `username:password` in the `Authorization` header: ```http Authorization: Basic ``` {% endcolumn %} {% endcolumns %} --- # 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/3d-secure.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.