> 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/implement-payment-passkeys/delete-payment-passkeys-from-issuer-backend.md).

# Delete payment passkeys from issuer backend

## Overview

Use this flow when a device is lost or stolen.

The issuer backend can get the payment passkeys and delete the selected payment passkey.

This flow is available for Visa only.

### Flow

<figure><img src="/files/bcjk6dhwqGlvwOYYxlui" alt="" width="563"><figcaption><p>Issuer backend flow for deleting payment passkeys.</p></figcaption></figure>

This flow runs entirely in the issuer backend.

It does not involve the device or the D1 SDK.

The APIs to get payment passkeys and delete them are synchronous.


---

# 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/implement-payment-passkeys/delete-payment-passkeys-from-issuer-backend.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.