Search…
Overview
"AWS for public blockchain transactions"
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.

Supported Methods

The Managed Transactions API supports the following methods of operation:
Method
Use-Case
Broadcast
the API signs arbitrary calldata and broadcasts a transaction to a named recipient
Subsidize
the API sends exact funds needed to execute the contemplated transaction to a named beneficiary, which broadcasts the transaction upon receipt of the subsidy

Supported Networks

The Managed Transactions API could theoretically support any public blockchain. The following networks are currently supported:
Network
Currencies
Supported Methods
Base Cost
Pricing
Ethereum
ETH
gas¹
Contact Us
Polygon
MATIC
Broadcast
gas¹
Contact Us
¹ 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).

Sender Addresses

Provide Payments uses the following "hot wallet" addresses, which vary based on the target network, in connection with the Managed Transactions API:

Ethereum

Network
Sender Address
Ethereum Mainnet
0x0A18277d6CF3253A89089A428f18bb3B66AF734e
Ethereum Ropsten Testnet
0x308354456d4a3d594a0dB0b154E1a52ed3312067
Ethereum Kovan Testnet
0x308354456d4a3d594a0dB0b154E1a52ed3312067
Ethereum Görli Testnet
0x308354456d4a3d594a0dB0b154E1a52ed3312067

Polygon

Network
Sender Address
Polygon Mainnet
0x0A18277d6CF3253A89089A428f18bb3B66AF734e
Polygon Mumbai Testnet
0x308354456d4a3d594a0dB0b154E1a52ed3312067

Liquidity

Liquidity is provided programmatically by Provide Payments on supported networks; transaction fees are paid using the network-native currency. Funds are stored in one or more hot wallets, secured by Vault, and used to fund transactions which are broadcast on behalf of API users.