> For the complete documentation index, see [llms.txt](https://docs.velafi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.velafi.com/api-reference/webhooks/stablecoin-payment-order-message-push.md).

# Stablecoin Payment Order Message Push

## Stablecoin Payment Webhook

When the status of a stablecoin payment order changes, the system sends an event notification to the merchant’s pre-configured endpoint via **Webhook**.

The webhook mechanism enables merchants to receive **real-time payment updates** without actively polling the order query APIs.

* The webhook payload includes core order information and blockchain-related transaction data
* Merchants should properly handle the webhook request
* A successful **HTTP 200 response** is recommended to acknowledge receipt

***

### Webhook Event

Event Type: `STABLE_COIN_PAYMENT_WEBHOOK`

***

### Webhook Payload

The webhook request body contains the following parameters:

* webhookId: Unique identifier for the webhook event.
* eventType: Event type identifier.
* orderId: Payment order ID.
* userId: User identifier.
* merchantId: Merchant identifier.
* linkId: Payment link ID.
* walletId: Wallet identifier.
* walletName: Wallet name.
* referenceId: Merchant reference number.
* currency: Currency type.
* network: Blockchain network identifier.
* networkName: Blockchain network name.
* depositAmount: Deposit amount.
* feeAmount: Transaction fee.
* receivedAmount: Actual received amount.
* status: Order status (e.g., `CONFIRMED`).
* fromAddress: Sender wallet address.
* toAddress: Receiver wallet address.
* txHash: Blockchain transaction hash.
* paymentLink: Payment link URL.
* createTime: Order creation timestamp.
* cancelTime: Order cancellation timestamp.
* processTime: Processing timestamp.
* confirmTime: Confirmation timestamp.

***

### Webhook Example

```json
{
  "webhookId": "ebab8a9663704e7cbbebe672c7c67912",
  "eventType": "STABLE_COIN_PAYMENT_WEBHOOK",
  "orderId": 1234567890,
  "userId": 9876543210,
  "merchantId": 42,
  "linkId": 56789,
  "walletId": 10001,
  "walletName": "Main USDT Wallet",
  "referenceId": "REF-2024-05-03-001",
  "currency": "USDT",
  "network": "ethereum",
  "networkName": "Ethereum Mainnet",
  "depositAmount": 1000.00,
  "feeAmount": 2.50,
  "receivedAmount": 997.50,
  "status": "CONFIRMED",
  "fromAddress": "0x1234567890abcdef1234567890abcdef123456789",
  "toAddress": "0x9876543210fedcba9876543210fedcba98765432",
  "txHash": "0xabcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcd",
  "paymentLink": "https://payment.example.com/pay/123456",
  "createTime": 1714671600000,
  "cancelTime": null,
  "processTime": 1714672200000,
  "confirmTime": 1714672800000
}
```

***

### Notes

* Merchants must configure a **publicly accessible webhook endpoint** to receive event notifications.
* The webhook will be triggered when the **payment order status changes**.
* Merchants should return **HTTP 200** to confirm successful receipt of the webhook event.
* All timestamps are returned in **Unix milliseconds**.  - Stablecoin Payment Webhoo


---

# 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://docs.velafi.com/api-reference/webhooks/stablecoin-payment-order-message-push.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.