# User identification payloads {% 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="" %} ### --- # Agent Instructions: 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: ``` GET https://docs.xaman.dev/environments/backend-sdk-api/user-identification-payloads.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.