FAQs

Find answers to common questions about transaction and firewall policies, wallet setups, and signing processes.

What is the difference between setting up a Spending Limit versus a Transfers Policy? ▸

Spending Limit is a transaction policy that defines the maximum limit per transaction during transaction initiation. The Transfers policy is a Firewall policy where you define rules per transaction for Firewall approval.

Which API endpoints can we call for transaction signing for Firewall-enabled wallets? ▸

Applies to v2 wallets (hot withdrawal and deposit) only:

Automatic transaction signing using the Start or Stop Transaction Execution API.
Manual transaction signing using the Submit Transaction API.

How do we set up a custom transaction signing for hot wallets? ▸

You can use the Submit Transaction API to set up a custom cron job for manual transaction signing periodically. We recommend configuring the cron job at a 30-second interval. This applies to v2 wallets (hot withdrawal and deposit) only.

What is the difference between Transaction Policies and Firewall Policies? ▸

Aspect	Transaction Policies	Firewall Policies
Wallet Support	Supported for v1 and v2 wallets	Supported for v2 wallets only
Execution Stage	Executed during transaction initiation	Executed during the Firewall Approval stage
Purpose	Controls transaction rules and limits at initiation	Adds compliance, risk, and regulatory checks
Policy Types Included	Spending Limit Transaction Limit Address Whitelisting	Travel Rule Transfers Transaction Risk
Applicability	Ensures transactions comply with predefined limits and allowed addresses before initiation	Prevents risky or non-compliant transactions from being approved