> For the complete documentation index, see [llms.txt](https://docs.hivesql.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hivesql.io/technical-informations/operations/txescrowtransfers.md). # TxEscrowTransfers #### Blockchain operations * escrow\_transfer #### Columns | Name | Description | | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | | from | account sending assets | | to | account receiving assets | | hbd\_amount | amount of HBD sent | | hive\_amount | amount of HIVE sent | | escrow\_id | a unique identifier assigned by the sender to this transaction | | agent | the name of the agent who will have authority to resolve disputes | | fee | the fee that goes to the agent regardless of any dispute | | fee\_symbol | the fee asset symbol | | json\_meta | extra meta-information that is not part of the consensus | | ratification\_deadline | the time before which the receiver and the escrow must agree to commit the transaction. If no action is taken, the funds are returned to the sender. | | escrow\_expiration | the time at which the funds will go to the receiver if no other action is taken | #### Description This table store transfers initiated just like any other transfer that requires the approval of a third party. Unlike a normal transfer, an escrow transfer specifies some additional fields. An escrow payment facilitates trade among two or more parties with the potential for dispute resolution. When a user makes a payment via escrow the escrow agent receives a fee regardless of whether or not a dispute was raised. --- # 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.hivesql.io/technical-informations/operations/txescrowtransfers.md?ask=&goal= ``` `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.