Service status
This page provides operational guidance and public health checks. For a live incident affecting your integration, verify with API responses, webhook deliveries, and your own monitoring before taking fulfillment or payout actions.
Public checks
- Site/API health: /health and /api/health
- Tempest Pay auth check (requires secret key):
GET /api/v1/ping - Integration docs: /docs/integration, OpenAPI, Postman collection
curl -s https://tempesttouchwallet.com/api/health
curl -s https://tempesttouchwallet.com/api/v1/ping \
-H "Authorization: Bearer $TEMPEST_SECRET_KEY"
Component guidance
| Component | Normal behavior | If degraded |
|---|---|---|
| Wallet app | Sign in, balances, history, sends/deposits subject to account/network status. | Retry, check browser console/network, avoid repeated irreversible actions, contact support@tempesttouchwallet.com with request details. |
| Hosted checkout | Charge page loads, payment options/status update. | Do not assume payment failed/succeeded from UI alone; retrieve charge server-side and wait for verified webhooks. |
| Webhooks | Signed events delivered; duplicates possible; 2xx acknowledges. | Process idempotently, return 2xx only after durable receipt, reconcile using events/charge retrieval. |
| Price/rate data | Informational; charge conversion locked by charge flow. | Display prices may be stale/fallback; never use display-only prices for settlement. |
Incident reporting
Email support@tempesttouchwallet.com with the request ID, timestamp, endpoint, charge ID/reference, and non-sensitive error details. Do not send secret API keys, webhook secrets, passwords, or private keys.