> For the complete documentation index, see [llms.txt](https://developer.paywall.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.paywall.one/payment-orchestration-integration-document/wallet-services/1.-wallet-owners/6.-query-by-identity.md).

# 6. Query by Identity

## **Identify Wallet Record by Identity**

<mark style="color:green;">`GET`</mark> `{{WalletUrl}}/api/v1/walletowner/by/identity?Identity=68567422314`&#x20;

{% hint style="info" %}
**Note:** Before calling this service, you must include the **apikeypublic** and **apiclientpublic** parameters in the Header section.

[<mark style="color:green;">**WalletAPI Address**</mark>](/payment-orchestration-integration-document/environment.md)
{% endhint %}

**The parameters that must be sent to the service are as follows:**

<table><thead><tr><th width="162">Parameter</th><th width="95.95703125">Type</th><th width="107">Required</th><th width="403">Description</th></tr></thead><tbody><tr><td>apikeypublic</td><td>string</td><td>Yes</td><td>It is the public key used for authentication in service calls.</td></tr><tr><td>apiclientpublic</td><td>string</td><td>Yes</td><td>It is the public key used to specify the identity of the API client.</td></tr></tbody></table>

**The (QueryString) parameters that must be sent to the service are as follows:**

<table><thead><tr><th width="162">Parameter</th><th width="403">Description</th></tr></thead><tbody><tr><td>Identity</td><td>The identity information of the wallet owner you want to query.</td></tr></tbody></table>

{% tabs %}
{% tab title="Service Request - JSON" %}
{% code lineNumbers="true" %}

```json
{
    "IsSuccess": true,
    "IsFailure": false,
    "Value": {
        "Id": "518432e0-5e95-40f6-bdcf-60278711ea66",
        "MaskedFullname": "E**s S****n",
        "Email": "Annalise.Zulauf67@hotmail.com",
        "PhoneNumber": "+905348744914",
        "MaskedTaxNumber": null,
        "MaskedIdentityNumber": "271******66",
        "OwnerType": "Individual",
        "CompanyName": "test",
        "Address": "address",
        "Country": "country",
        "City": "city",
        "DateOfBirth": "2030-10-15",
        "CreatedAt": "2025-08-20T10:02:07.41549Z",
        "UpdatedAt": null
    }
}
```

{% endcode %}
{% endtab %}
{% endtabs %}

## **Service Response**

<table><thead><tr><th width="192">Parameter</th><th width="147.89192708333331">Type</th><th>Description</th></tr></thead><tbody><tr><td>IsFailure</td><td>bool</td><td>Indicates whether the related service call has failed or not. (true/false)</td></tr><tr><td>IsSuccess</td><td>bool</td><td>Indicates whether the related service call was successful or not. (true/false)</td></tr><tr><td>Errors</td><td>Array</td><td>The area where error messages occurring during the service call are listed.</td></tr><tr><td>Value</td><td>Array&#x3C;Items></td><td>The area representing the main data object returned by the service.</td></tr></tbody></table>

## **Service Response** (Value)

<table><thead><tr><th>Parameter</th><th>Type</th><th width="348.94140625">Description</th></tr></thead><tbody><tr><td>Id</td><td>Guid</td><td>It is the unique identifier of the entity recorded in the system.</td></tr><tr><td>MaskedFullname</td><td>string</td><td>It is the field where the user's full name is displayed in a masked (hidden) format.</td></tr><tr><td>Email</td><td>string</td><td>It is the user's registered email address.</td></tr><tr><td>PhoneNumber</td><td>string</td><td>It is the user's registered phone number.</td></tr><tr><td>MaskedTaxNumber</td><td>string</td><td>It is the field where the user's tax number is displayed in a masked (hidden) format.</td></tr><tr><td>MaskedIdentityNumber</td><td>string</td><td>It is the field where the user's identity number is displayed in a masked (hidden) format.</td></tr><tr><td>OwnerType</td><td>string</td><td>It is the field that specifies whether the wallet owner is an individual or a corporate entity.</td></tr><tr><td>CompanyName</td><td>string</td><td>It is the registered company name of the wallet owner (if applicable).</td></tr><tr><td>Address</td><td>string</td><td>It is the field containing the registered address information of the wallet owner.</td></tr><tr><td>Country</td><td>string</td><td>It is the country information where the wallet owner is registered.</td></tr><tr><td>City</td><td>string</td><td>It is the city information where the wallet owner is registered.</td></tr><tr><td>DateOfBirth</td><td>Date</td><td>It is the date of birth of the wallet owner.</td></tr><tr><td>MerchantId</td><td>int</td><td>It is the date of birth of the wallet owner.</td></tr><tr><td>CreatedAt</td><td>DateTime</td><td>Indicates the creation time of the record.</td></tr><tr><td>UpdatedAt</td><td>DateTime</td><td>Indicates the last updated time of the record.</td></tr><tr><td>Wallets</td><td>List</td><td>It is the field representing the list of wallets associated with the user.</td></tr></tbody></table>


---

# 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://developer.paywall.one/payment-orchestration-integration-document/wallet-services/1.-wallet-owners/6.-query-by-identity.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.