Overview
⚠️The Managed Transactions API is not currently in production; all functionality and related documentation is provided as a courtesy for early adopters. Many APIs related to this service are under active development, should be considered unsupported "alpha" versions and may change or be removed without notice.
The Managed Transactions API enables traditional enterprise procurement of public blockchain services without the need to ever buy or hold cryptocurrency.
Users are billed in arrears based on transaction volume. Fees incurred when using the Managed Transactions API are billed in arrears and always expressed in terms of the customer's choice of fiat currency.
The Managed Transactions API supports the following methods of operation:
The Managed Transactions API could theoretically support any public blockchain. The following networks are currently supported:
¹ Value transfers (i.e., payment of cryptocurrency or tokens to a third party) are not currently supported by the Managed Transactions API. Such transfers may be supported in a future release. As of today, this service only pays the fee to broadcast transactions to the network (i.e., gas).
Provide Payments uses the following "hot wallet" addresses, which vary based on the target network, in connection with the Managed Transactions API:
Network | Sender Address |
Ethereum Mainnet |
|
Ethereum Ropsten Testnet |
|
Ethereum Kovan Testnet |
|
Ethereum Görli Testnet |
|
Liquidity is provided by the UBT utility token in an opaque manner (i.e., programmatically, behind the scenes). UBT is stored in a hot wallet, secured by Vault, and used to fund transactions which are broadcast on behalf of customers using the API. When additional liquidity is required, additional UBT is pulled from a professional custodian service into the hot wallet.
