Service status and maintenance

Every service has moments when a feature pauses — maintenance, an upgrade rolling out, a provider on the other side of a rail doing its own work. What distinguishes a payment app is how it behaves in those moments. Kit Pay's rule: money actions refuse cleanly rather than proceeding into uncertainty.

How a pause behaves

• Features can pause and resume individually. The app shows what your account can use right now, so a paused feature is announced by the surface you would use it from — not discovered by a payment failing strangely.
• A refused action is a complete non-event: nothing half-happened, nothing needs untangling. When the feature resumes, you act again, fresh.
• Money that was already yours stays recorded to you throughout. A pause interrupts new actions, not the ledger.

Why refusing beats limping

The dangerous failure in payments is not the error message — it is the payment that half-happens during a wobble and leaves two sides with two different beliefs. Kit Pay's designs are fail-closed for exactly this reason: an action either completes and is recorded on both sides, or it refuses. Frustrating for a minute; trustworthy for years. The same principle runs through the deposit design: held rather than guessed, resolved rather than lost.

What to actually do

1. Read what the app says — announcements about your account's features appear there, from the source.
2. Make sure the app is up to date; running an old version is the most common self-inflicted "outage".
3. Wait and retry rather than hammering — a refused action does not queue, so nothing stacks up behind your attempts.
4. If money seems affected — an entry you expected is missing after things resume — check your history first, then ask through Help in the app.