# Payment Inquiry

To confirm orders have been processed on the third party's customers' end, we implemented a payment inquiry feature that allows xendbridge to inquire about the status of the crypto payments from the third party. 

For this, we require the third party to provide a webhook endpoint and response data that meets the following specifications and share this url with us to proceed with transactions on the live environment.

## Payment Inquiry

<mark style="color:blue;">`GET`</mark> `https://{YOUR BASE URL}/api/order/inquiry?reference=XS_460ed3181a9b48a0`

#### Query Parameters

| Name                                        | Type   | Description                |
| ------------------------------------------- | ------ | -------------------------- |
| reference<mark style="color:red;">\*</mark> | string | XS\_435tfe4rf3rf4d33rf4rde |

{% tabs %}
{% tab title="200: OK Success" %}

```json
{
    "data": {
      "hashVerificationUrl": "https://bscscan.com/tx/0x7af63d512a3a6fcbfd23b41b1f77b9125a5d86524432fc01b7560edf2eb3ba03",
      "isProcessed": true,
      "transactionHash": "0x5169bb5e7ff0f3502ba818120f2eebaad512bc2816c7f9399e60cc42033a672c"
    },
    "status": "OK",
    "message": ""
}
```

{% endtab %}
{% endtabs %}


---

# 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://doc.xendbridge.com/api-method-calls/payment-inquiry.md?ask=<question>
```

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.