The requires_attention status

Transfers move through their lifecycle automatically. Occasionally, a transfer needs manual intervention from the Increase team and is popped out of the normal flow into the requires_attention status.

This is a very rare status. If we intervene with one of your transfers, we’ll let you know via Slack and email. We’ll also be working to get your transfer back into the processing pipeline.

What it means

requires_attention is an escape hatch used by Increase operators. Because it sits outside the normal happy and unhappy paths, no transfer transitions into it automatically as part of routine processing. You don’t need to poll for this status or build special handling to detect it. At the same time, you should be able to deserialize transfers that end up in this status. If you use one of our SDKs, you’ll get correct parsing out of the box.

We’ve found this to be a powerful pattern for handling state machines at scale. It’s hard to predict in advance the ways that large systems will degrade, and having a pre-built release valve has proven itself consistently worthwhile. We also prefer correctness and transparency instead of masking a regression by pretending to be in a happy-path pending status.

If you have any questions about a transfer in this status, reach out to support@increase.com.