> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/payment-passkeys-issuers/payment-passkeys.md).

# Payment Passkeys

Payment Passkeys removes passwords, and redirects with biometric authentication, enabling seamless and secure checkout across card-on-file (COF), Click to Pay (C2P), and emerging agentic commerce flows. It is aimed to reducing fraud, increase approval rates and lowering operational friction and its related costs.

<a href="/pages/8aiA0Jh84rLqUtZkxEO1" class="button primary">Explore Docs</a>

{% columns %}
{% column %}

{% endcolumn %}

{% column %}

{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

{% endcolumn %}

{% column %}

{% endcolumn %}
{% endcolumns %}

<div align="left"><figure><img src="/files/j0hXDtU9E4tPU3yjGZnz" alt="" width="101"><figcaption></figcaption></figure></div>

### Why Thales to implement Visa & Mastercard Payment Passkeys?

The service leverages Thales’ expertise to abstract the complexity of Visa and Mastercard Payment Passkeys into a single, consistent solution built on the Thales D1 platform and designed around its unified credentials principles. It enables issuers to deploy faster, scale new capabilities with ease, and reduce cost of ownership to build and maintain fragmented integrations.

{% columns %}
{% column %}

{% endcolumn %}

{% column %}

{% endcolumn %}
{% endcolumns %}

{% columns fullWidth="false" %}
{% column width="25%" valign="middle" %}

<div align="center"><figure><img src="/files/xwZfFGM2uFwoyCMmpUyO" alt=""><figcaption></figcaption></figure></div>
{% endcolumn %}

{% column width="75%" valign="middle" %}

#### Abstract the fragmented integrations

Offload continuous specification and mandates updates and minimize integration complexities into a unified orchestrator to maximize Token Assurance Levels.

{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

{% endcolumn %}

{% column %}

{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column width="75%" %}

#### Accelerate agentic commerce readiness

We are shifting Issuers from a complex, multi-endpoint integration be it Tokenization with CTF and MDES ID\&V or Click to Pay to a plug-and-play digital orchestrator. Issuers integrate once and launch new services in just weeks.
{% endcolumn %}

{% column width="25%" valign="middle" %}

<figure><img src="/files/FhYybm0whzzazvAYFncB" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

{% endcolumn %}

{% column %}

{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column width="25%" valign="middle" %}

<div align="center"><figure><img src="/files/IMb5UxwayooKwBjzbrLW" alt=""><figcaption></figcaption></figure></div>
{% endcolumn %}

{% column width="75%" valign="middle" %}

#### Unified credential foundation

Beyond silos: we converge vision, expertise and execution in Thales D1 platform, that lets us deploy, scale, and pivot to any new service faster and more cost-effectively.
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

{% endcolumn %}

{% column %}

{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

{% endcolumn %}

{% column %}

{% endcolumn %}
{% endcolumns %}

<div align="left"><figure><img src="/files/j0hXDtU9E4tPU3yjGZnz" alt="" width="101"><figcaption></figcaption></figure></div>

### **Features**

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><img src="/files/twGCGeAQsJiYYzOp1nuJ" alt=""></td><td><strong>Payment Passkey creation</strong></td><td>The unified D1 SDK enables an issuer agnostic Payment Passkey experience, allowing cardholders to securely create Visa and Mastercard Payment Passkeys in their banking app. Built to leverage Issuer own SCA at app login, it drives trust in the bank to accelerate adoption and ensure creation is being made only by the genuine cardholders.</td></tr><tr><td><img src="/files/tYl52hi8raBbnGzcIjJ7" alt=""></td><td><strong>Payment Passkeys lifecycle management</strong></td><td>Be it through the unified D1 SDK or backend APIs, issuers and their cardholders can list, create, rename, and delete Visa and Mastercard Payment Passkeys for their cards, ensuring full lifecycle control and visibility.</td></tr></tbody></table>

{% columns %}
{% column %}

{% endcolumn %}

{% column %}

{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

{% endcolumn %}

{% column %}

{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

{% endcolumn %}

{% column %}

{% endcolumn %}
{% endcolumns %}

<div align="left"><figure><img src="/files/j0hXDtU9E4tPU3yjGZnz" alt="" width="101"><figcaption></figcaption></figure></div>

### Use cases

{% columns %}
{% column width="66.66666666666666%" %}
**Token verification CTF and MDES ID\&V**

The unified SDK can be enabled to support in-app ID\&V for CTF and MDES ID\&V for device binding and payment passkey creation from merchant upon checkout.
{% endcolumn %}

{% column width="33.33333333333334%" %}

<figure><img src="/files/JGZbRxSYvFTXhDLXPm9Z" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column width="33.33333333333334%" %}

<figure><img src="/files/FSpCGdbMue9CMUetFC1E" alt=""><figcaption></figcaption></figure>
{% endcolumn %}

{% column width="66.66666666666666%" %}
**Orchestrate Click to Pay and Payment Passkeys**

Aggregators and issuers use BrandMyCard to rapidly design and launch small‑series cards for employers, retailers, or partners. Leveraging a single pre-approved base plastic stock significantly reduces validation cycles and cuts waste.

{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

{% endcolumn %}

{% column %}

{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

{% endcolumn %}

{% column %}

{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

{% endcolumn %}

{% column %}

{% endcolumn %}
{% endcolumns %}

<div align="left"><figure><img src="/files/j0hXDtU9E4tPU3yjGZnz" alt="" width="101"><figcaption></figcaption></figure></div>

{% columns %}
{% column width="91.66666666666666%" valign="middle" %}

### <mark style="color:$primary;">Start Building</mark> with Thales

Accelerate your payment solutions and deliver secure, scalable experiences today.

<a href="https://lp.thalesgroup.com/dev-portal" class="button primary">Contact Us</a>&#x20;

&#x20;
{% endcolumn %}

{% column width="8.333333333333343%" %}

{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.payments.thalescloud.io/payment-passkeys-issuers/payment-passkeys.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.