EWA request status
Lifecycle of earned wage access (kasbon) requests through disbursement.
EWA request status
Earned wage access (EWA) requests are created by employees in the Momen app. Your integration lists them with GET /ewa-requests — you cannot create a request through the API.
Each request moves through these statuses:
| Status | Terminal | Meaning |
|---|---|---|
SCHEDULED | no | Disbursement scheduled |
PROCESSING | no | Disbursement in progress |
SETTLING | no | Disbursed; settlement in progress |
PARTIAL | no | Partly settled |
COMPLETED | yes | Disbursed to the employee |
FAILED | yes | Disbursement failed |
REJECTED_BY_SYSTEM | yes | Rejected automatically, e.g. at cut-off |
Terminal statuses do not change again. Poll less once you see a terminal value.
Legacy values
Older requests may use REJECTED, CANCELLED, or EXPIRED. Treat any value not listed in the table above as terminal if it is not one of the non-terminal statuses.
Lifecycle
Loading diagram…
Cut-off on list responses
GET /ewa-requests includes a cutoff object on each request with the employee's current pay cycle, withdrawal window, and available_to_withdraw. Use it to reconcile limits without a separate call.
Employees and deletion
You cannot delete an employee while they have a non-terminal EWA request (employee_has_active_ewa_request). After completion, failure, or rejection, deletion succeeds and history remains visible in list results.