Pricing and fees
Tempest Touch is a custodial wallet and Tempest Pay is a merchant payment service. Exact fees, enabled assets, and settlement behavior depend on current platform configuration, your account status, and the selected network/asset. The in-app quote, admin/merchant configuration, and API responses are the source of truth for live transactions.
Account access
Creating a wallet account does not require purchasing software. Network transfers, withdrawals, and other actions may incur platform fees and/or blockchain/network costs depending on the flow.
Hosted checkout + API
Merchants can create charges, redirect customers to hosted checkout, and receive signed webhooks. Merchant fees, gateway/platform fee splits, and settlement rules are configured by the platform and may vary by account, mode, asset, and network.
Test mode
Use test keys and sandbox/test flows where supported to validate integration behavior before live use. Test simulations do not represent final commercial pricing or live blockchain settlement guarantees.
What can affect the final amount
| Factor | How it matters |
|---|---|
| Asset and network | Supported assets/networks have different decimals, confirmation behavior, liquidity, and operational costs. Availability can change. |
| Transfer type | Internal/platform-booked transfers, external sends, withdrawals, and merchant checkouts can follow different fee and settlement paths. |
| Price conversion | USD-priced merchant charges are converted to supported settlement assets using live prices and locked according to the charge flow. Display-only prices may be informational/stale and must not be used for settlement. |
| Account status | KYC/verification, risk controls, frozen/restricted states, and merchant approval can affect access to live features. |
| Confirmations/finality | Blockchain confirmation timing affects when a payment is detected, marked processing, or considered paid. Do not fulfill orders until a verified paid webhook/server-side status check. |
Settlement and responsibility
- Crypto transactions can be irreversible after broadcast/confirmation.
- Users and merchants must verify addresses, networks, assets, amounts, and order references.
- Merchants must fulfill only after verifying a signed webhook or retrieving charge status server-side; browser redirects are not proof of payment.
- Refund processing may be limited, delayed, or unavailable depending on the product flow and operational state; check current API/docs/status before relying on refunds.
Next steps
Developer overview · Integration guide · Sandbox guide · Contact sales/support