The most common use case of KMS and hardware wallets involves using Tatum KMS as your custodial service and automated transaction signature service.
After this, the selected few within your organization with access to the on-premise Tatum KMS environment would make transfers to a cold/hardware wallet as your internal processes demand.
On the other hand, some customers may want to skip Tatum KMS altogether and implement their own custodial service or interface directly with the Tatum API endpoints with a Hardware wallet. In these cases, the KMS API endpoints available at the following link would work the same.
However, the implementation of a custom solution, be an alternative KMS or a Hardware wallet directly interfacing with Tatum API endpoints is out of the scope of Tatum.
It is possible to implement an alternative KMS or a hardware wallet and keep using Tatum API endpoints.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article