We were recently informed that the Disbursement API is no longer supported, so we’re currently reviewing alternative solutions that could potentially support our use case.
One option we’re exploring is Cash-In via Login, and we’re assessing whether it could be used as a workaround for batch disbursement.
Our main concern is around the authorization model.
Since Cash-In via Login relies on user session-based authorization, we’d like to clarify:
-
Is there any supported way to handle scheduled or batch disbursements without requiring an active user session each time?
-
Is it possible to bypass or programmatically manage the authorization step for system-initiated payouts?
-
Or is this solution strictly intended for user-initiated, real-time transactions only?
Our use case involves automated or scheduled payouts, so we’re trying to understand whether this solution aligns architecturally, or if we should instead be looking at a different product altogether.
We want to ensure we’re following the intended design and security model, rather than implementing a workaround that may not be supported long-term.
Appreciate any guidance or recommended direction. Thanks in advance