> For the complete documentation index, see [llms.txt](https://docs.xaman.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xaman.dev/environments/backend-sdk-api/user-identification-payloads.md).

# User identification payloads

When building your own backend integration, you can request a user to sign a Sign Request with a "SignIn" transaction type. This is a pseudo transaction type allowing a user to confirm their r-address

{% hint style="info" %}
A SignIn transaction will **never** be submitted to the XRP ledger, as it is an invalid transaction type (XUMM specific pseudo transaction type).
{% endhint %}

A sign `SignIn` sign request can be as simple as this:

```json
{
  "txjson": {
    "TransactionType": "SignIn"
  }
}
```

All Xumm payload options are valid for a `SignIn` transaction.

\
After the user signs your SignIn request, the server to server call (to your configured Webhook location) will receive the signed transaction containing the signed transaction HEX blob.

## Response

When the user signs the Sign Request, you will get a signed transaction (that has never been submitted to the XRP Ledger).

You can now get the account address and some basic public account information from the payload details, and assign this information to your own local dataset, like a session.

### Verify the signature

If you want to you can run your own signature verification on the signed `SignIn` pseudo transaction our platform returns to you. Of course the Xumm platform also verified the signature for you. Would you like to check yourself as well, we have created this package

{% embed url="<https://www.npmjs.com/package/verify-xrpl-signature>" %}

###


---

# 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.xaman.dev/environments/backend-sdk-api/user-identification-payloads.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.