> For the complete documentation index, see [llms.txt](https://docs.saferpay.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saferpay.com/home/interfaces/backoffice/secure-card-data/secure-card-data-details.md).

# Secure Card Data Details

![(click to enlarge)](https://3537448238-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fzpi9teY7Tm2pCZ1Bw8zO%2Fuploads%2FKO2E1EpV4TQoVJ9sgmmR%2FBO_SCD_Search_List_Details.png?alt=media\&token=4a1f1711-b75c-4480-bb46-b2f44a500f17)

By clicking on Details for a Secure Card Data entry, the details page will be displayed.

![(click to enlarge)](https://3537448238-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fzpi9teY7Tm2pCZ1Bw8zO%2Fuploads%2F7dYQI6XXRArQEMOMZbMo%2FBO_SCD_Details.png?alt=media\&token=bfc94124-2e25-4d33-99fa-4872d1abffd8)

This view is giving you some more information about the alias itself, a possibility to [demask the PAN](/home/interfaces/backoffice/transactions/journal-details.md#demasking-the-pan), the card type, the expiration date and lifetime, which you can both edit by clicking on the Edit symbol, and more.

#### 3-D Secure Authentication

Under the new [PSD2 law](https://saferpay.github.io/sndbx/psd2.html), it became necessary to also add a layer of so-called **Strong Consumer Authentication** to card aliases, in the form of 3D Secure.

## New Payment

You can also execute new payments through this alias if you so wish by clicking on [Authorization](/home/interfaces/backoffice/transactions/journal-details.md#authorization) (click for further details) or [Credit for a Refund](/home/interfaces/backoffice/transactions/journal-details.md#refund) (click for further details).


---

# 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.saferpay.com/home/interfaces/backoffice/secure-card-data/secure-card-data-details.md?ask=<question>&goal=<user_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.