{"templateId":"openapi_docs","versions":[{"version":"v1.40","label":"v1.40 STS","link":"/products/custody/devbox/transactions","default":true,"active":false,"folderId":"c15a2701"},{"version":"v1.39","label":"v1.39 STS","link":"/products/custody/v1.39/devbox/transactions","default":false,"active":false,"folderId":"c15a2701"},{"version":"v1.38","label":"v1.38 STS","link":"/products/custody/v1.38/devbox/transactions","default":false,"active":true,"folderId":"c15a2701"},{"version":"v1.34","label":"v1.34 LTS","link":"/products/custody/v1.34/devbox/transactions","default":false,"active":false,"folderId":"c15a2701"},{"version":"v1.26","label":"v1.26 LTS","link":"/products/custody/v1.26/devbox/transactions","default":false,"active":false,"folderId":"c15a2701"},{"version":"v1.19","label":"v1.19 LTS","link":"/products/custody/v1.19/devbox/transactions","default":false,"active":false,"folderId":"c15a2701"},{"version":"v1.15","label":"v1.15 LTS","link":"/products/custody/v1.15/devbox/transactions","default":false,"active":false,"folderId":"c15a2701"}],"sharedDataIds":{"openAPIDocsStore":"oas-products/custody/@v1.38/devbox.json","sidebar":"sidebar-sidebar.yaml__products_custody_v1.38_devbox"},"props":{"definitionId":"products/custody/@v1.38/devbox.json","dynamicMarkdocComponents":[],"baseSlug":"/products/custody/v1.38/devbox","seo":{"title":"Transactions","description":"A **transaction order** is an order to transfer assets or request an operation on the ledger. In the simplest case, it relates to the transfer of a native cryptocurrency; in more advanced cases, it can apply to the execution of smart contract methods and other on-ledger features.\r\n\r\n**Transaction orders** may differ from one ledger protocol to another, but they at least define the account origin, and normally have an amount and a destination address; for some protocols, a single transaction may include multiple destinations and amounts, possibly denominated in various currencies.\r\n\r\n**Transaction orders** rely on property `parameters` to define ledger-specific transaction order parameters.\r\n\r\nWe present below the transaction order parameters for Bitcoin:\r\n - `outputs`: sequence of pairs of destination and amount;\r\n - `feeStrategy`: fee calculation strategy, which may be `Low`, `Medium` or `High`; the actual fee amount corresponding to the selected strategy is automatically set by the system at execution time based on a network metrics;\r\n - `maximumFee`: maximum fee the user is willing to pay to execute the transaction; in rare occasions, *Harmonize* may decide to rebroadcast a transaction with higher fees to ensure inclusion within the ledger, as long as `maximumFee` has not been reached.\r\n\r\nFor an exhaustive list corresponding to each respective ledger protocol, we refer to the reference manual.\r\n\r\n*Harmonize* supports multiple types of destinations for **transaction orders**:\r\n - ledger address: a ledger address is a protocol-level address, whose format may differ from one ledger protocol to another;\r\n - account: an account destination is an **account** `id`, which is guaranteed to implicitly resolve to an address of the account; for protocols supporting multiple addresses per account, no guarantee is provided over which account address the resolution leads to;\r\n - endpoint: an endpoint destination is an **endpoint** `id`, which is guaranteed to implicitly resolve to the address of the endpoint.\r\n\r\nOnce a **transaction order** is fully approved the order becomes executable. The corresponding **vault** may capture the pending **transaction order** and build and sign a corresponding ledger transaction.\r\n\r\n**Transactions** are incoming or outgoing ledger transactions that have been detected on the ledger or shall be broadcast. **Transfers** are the financial representation of their corresponding **transactions**. ","siteUrl":"https://docs.ripple.com","lang":"en-US","llmstxt":{"hide":false,"sections":[{"title":"Table of contents","includeFiles":["**/*"],"excludeFiles":[]}],"excludeFiles":[]}},"itemId":"transactions","disableAutoScroll":true,"metadata":{"subType":"openapi-operation"},"compilationErrors":[],"markdown":{"partials":{},"variables":{"rbac":{"teams":["anonymous"]},"user":{},"remoteAddr":{"hostname":"docs.ripple.com","port":4000,"ipAddress":"216.73.216.201"},"lang":"default_locale","env":{"PUBLIC_REDOCLY_BRANCH_NAME":"main-enterprise-product-docs","PUBLIC_VAR_LQH":"Liquidity Hub","PUBLIC_VAR_LQHUI":"Liquidity Hub UI","PUBLIC_VAR_ODL":"On-Demand Liquidity","PUBLIC_VAR_RN":"RippleNet","PUBLIC_VAR_RNC":"RippleNet Cloud","PUBLIC_VAR_RNSERVER":"RippleNet Server","PUBLIC_VAR_ROSAPINAME":"RippleNet Orchestration","PUBLIC_VAR_RPD":"Payments Direct","PUBLIC_VAR_SL":"Smart Liquidation","PUBLIC_VAR_SLAPI":"Smart Liquidation API","PUBLIC_VAR_CUS":"Ripple Custody","PUBLIC_VAR_RPO":"RippleNet Payment Object","PUBLIC_VAR_RNH":"Payments Direct UI","PUBLIC_VAR_RPODL":"Ripple Payments ODL","PUBLIC_VAR_RP":"Ripple Payments","PUBLIC_VAR_RNAPI":"RippleNet Server API","PUBLIC_VAR_RIPPLE_USD":"Ripple USD","PUBLIC_VAR_RLUSD":"RLUSD","PUBLIC_VAR_RS":"Ripple Stablecoin","PUBLIC_VAR_RS_PLATFORM":"Ripple Mint","PUBLIC_VAR_RS_UI":"Ripple Mint UI","PUBLIC_VAR_RS_API":"Ripple Mint API"}}},"pagePropGetterError":{"message":"","name":""}},"slug":"/products/custody/v1.38/devbox/transactions","userData":{"isAuthenticated":false,"teams":["anonymous"]},"isPublic":true}