> For the complete documentation index, see [llms.txt](https://doc.xendbridge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.xendbridge.com/api-method-calls/third-party-order-operations/pay-for-order.md).

# Pay For Order

This `POST` endpoint confirms a buy or sell order for a third-party customer indicating a successful transfer of funds. Only the `secretkey` is passed in the header while the request to be made would contain only an `emailAddress` and `orderReference`.

If successful returns a "Payment made successfully" `200`message.

## Pay for order

<mark style="color:green;">`POST`</mark> `https://canary.xendbridge.com/api/PeerToPeerOrder/ThirdParty/Order/Confirm`

#### Headers

| Name                                        | Type   | Description |
| ------------------------------------------- | ------ | ----------- |
| secretKey<mark style="color:red;">\*</mark> | String | {secretKey} |

#### Request Body

| Name                                              | Type   | Description                                                        |
| ------------------------------------------------- | ------ | ------------------------------------------------------------------ |
| emailAddress<mark style="color:red;">\*</mark>    | String | <johndoe@gmail.com>                                                |
| orderReference<mark style="color:red;">\*</mark>  | String | XB\_0877e5692ee946f491bafab275d3d522                               |
| transactionHash<mark style="color:red;">\*</mark> | String | 0xcfa4a293e6fd903329e9c035f4f17dafbd0dbd9b76b613be5cd2ba7b7a4baaa7 |

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

```javascript
{
    "data": true,
    "status": "OK",
    "message": "Payment Updated Successfully"
}
```

{% endtab %}
{% endtabs %}

{% tabs %}
{% tab title="Request Fields" %}

<table><thead><tr><th width="165.66666666666666">Parameters</th><th width="150">Type</th><th>Definitions</th></tr></thead><tbody><tr><td>emailAddress</td><td>string</td><td><code>Required</code> The email address of the third party client.</td></tr><tr><td>orderReference</td><td>string</td><td><code>Required</code> The order reference of an order made.</td></tr><tr><td>transactionHash</td><td>string</td><td><code>Required</code> The unique hash of a transaction on the blockchain network</td></tr></tbody></table>
{% endtab %}

{% tab title="Response Fields" %}

<table><thead><tr><th width="176.66666666666666">Parameters</th><th width="150">Type</th><th>Definitions</th></tr></thead><tbody><tr><td>data</td><td>bool</td><td>This can either be true or false.</td></tr><tr><td>status</td><td>string</td><td>This returns a status message of the request.</td></tr><tr><td>message</td><td>string</td><td>This returns either <code>Payment updated successfully</code> if success, or <code>Failed to update payment status. Please try again later</code> if failed.</td></tr></tbody></table>
{% endtab %}
{% endtabs %}


---

# 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://doc.xendbridge.com/api-method-calls/third-party-order-operations/pay-for-order.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.