Building a production status page for payment infrastructure

What a useful status page answers

A customer does not need every internal metric. They need to know whether they can create wallets, send payments, receive webhooks, verify deposits, and withdraw funds.

The best status pages map to user-visible workflows. If a payment bot is down, the operator needs to know which step is failing and whether retrying is safe.

Components to expose

• REST API availability.
• Dashboard login and account management.
• Wallet creation.
• Internal transfers.
• External Solana sends and withdrawals.
• Webhook delivery.
• Solana RPC and settlement dependencies.

Internal health check model

type StatusComponent = {
  name: string;
  status: "operational" | "degraded" | "down";
  latencyMs?: number;
  lastCheckedAt: string;
  message?: string;
};

Synthetic checks

Do not rely only on server uptime. Run synthetic checks that resemble real product actions. A Worker can be online while webhooks are failing or an RPC dependency is degraded.

• Ping the API health endpoint.
• Check database read/write availability.
• Check webhook queue age.
• Check pending withdrawal backlog.
• Check Solana RPC latency and recent confirmation health.

Incident language

Write status updates like an operator, not a lawyer. Say what is affected, what users should do, and when the next update will arrive.

For example: External withdrawals are delayed. Internal transfers and deposits are unaffected. Do not resubmit withdrawals. We are draining the queue and will update in 20 minutes.

ROI

A status page reduces duplicate support tickets during incidents. It also gives serious users confidence that the team understands the operational surface of money movement.