Chain Transactions
These events are triggered by individual, underlying blockchain transfers directed to the order's receiving address. They are useful for merchants who need fine-grained visibility into specific transaction hashes (txHash), especially in scenarios where a user splits a single order payment into multiple smaller on-chain transfers.
🔔 Event Types
| Event Identifier | Trigger Condition & Business Meaning |
|---|---|
pay.chain.transaction | Transfer Detected (Created): A new transaction hash (txHash) directed to the order address is detected on the blockchain network. |
pay.chain.transaction.update | Transfer Updated: The status or block confirmations of the specific txHash have changed (e.g., reached safe confirmations). |
Crucial Warning
The confirmation of a single on-chain transaction does not necessarily mean the total order amount is fully paid (e.g., the user might have underpaid). Do not use these events as triggers for shipping goods. All fulfillment actions must strictly rely on the parent order'spay.transaction.updateevent (where status = completed).
📦 Payload Example
The data object provides the complete hash record details and links back to the main order via the payIdNo field.
{
"event_id": "997daf9b-4162-4864-914c-960ff6cc16ad",
"event_identifier": "pay.chain.transaction.update",
"data": {
"id": "e62f4f6e-6666-458f-99c1-b621b32e06c8",
"payIdNo": "1940644675780100098",
"cursorId": "375638181647749120",
"txHash": "0x32a6c8cba334eb52699d612e1ba7235a2cca6f21c81f871ec93c95fcd108f3a8",
"transferAmount": "0.011",
"type": "in_term",
"createdAt": "2025-07-03T06:14:11.218Z"
}
}Updated about 15 hours ago