Transaction History & Status

Because transactions are an integral part of the wallet, we also provide you with the capability to check on transactions related to wallets.

Transaction History

When displaying transaction history to your wallet holders, we only provide the ability to fetch transactions per address. If you would like to display transactions broken down differently, we recommend that you store data within your system in order to more easily show the most relevant transaction data to your users.

Due to the nature of blockchain and because interoperability is core to our wallet design, you will still need to fetch the latest transactions on-chain. However, storing this data on your end will enable a more robust transaction history experience.

{wireframes of different transaction history options}

SDK

The SDK does not yet support this capability. However, even if you used the SDK to build the wallet, you can still use authentication from the SDK and then utilize the APIs for this capability.

API

Our APIs only support fetching transaction history by address. Depending on your use case, data aggregation, filtering, and consolidation may be required on your end. For more information about this API, head over to Transaction History APIs.

Wallet Level Transaction History

In this case, you will need to first fetch the wallet to get all the addresses associated with that wallet holder. Once that is complete, you will need to call our transaction history API once for each address associated with the wallet. The resulting response data will need to be aggregated and organized according to your sort criteria.

Address Level Transaction History

In this case, your use case matches our API structure so you will simply need to call our transaction history API and transaction data will be returned to you sorted by most recent.

Asset Level Transaction History

In this case, you will need to call our transaction history API and then filter the data down to the asset.

Transaction History By Time Period

In this case, you will need to get wallet level transaction history as described above, aggregate on your end, and then filter by time period.

Transaction Status

After a transaction occurs, you will need to keep wallet holders informed of the status of their transaction. Depending on network conditions, transaction completion time may vary. We recommend you store the transaction hash until the transaction is fully complete.

SDK

The SDK does not yet support this capability. However, even if you used the SDK to build the wallet, you can still use authentication from the SDK and then utilize the APIs for this capability.

API

Our APIs require the transaction hash to fetch the status for a particular on chain transaction. Transaction status can include

• PENDING -> Successfully broadcast and waiting to be processed

• FAILED -> Transaction did not go through

• SUCCESSFUL -> Transaction is successful

Saving Transaction Hash

For every transaction API, you will receive the transaction hash in the response. If you choose not to utilize our transaction history APIs, you can save the transaction hash directly after the transaction occurs. This is the recommended approach to mitigate any data discrepancies that result from cached data on the history.

Fetching Transaction Hash

If you choose not to save the transaction hash after the transaction occurs, you will need to fetch it using transaction history APIs. Once it is fetched, you can call the transaction status API as described in Transaction Status APIs.