logo

Errors

Bad Request

Either input was invalid or user was not in necessary state

Response Schema: application/json
code
required
string

A code that indicates the specific type of error.

Value: "BAD_REQUEST"
Example: "BAD_REQUEST"
description
required
string

A message that explains the meaning of the error code. Developers are advised not to make programmatic use of this value, as it may change.

Example: "The request failed because it was not in the correct format or did not contain valid data."
object
error_code
required
string

For 400 errors that can be handled programmatically, a short string indicating the error code reported.

Enum: "PATH_PARAM_MISSING" "USER_TOKEN_MISMATCH"
application/json
{
  • "code": "BAD_REQUEST",
  • "error_code": "PATH_PARAM_MISSING",
  • "description": "The request failed because it was not in the correct format or did not contain valid data.",
  • "details": {
    }
}

Bad Request Error Codes w/ Example Descriptions

NOTE: Values in quotes may change based on context and/or customization by the client

DEBIT_CARD_CREATION_BLOCKED
DailyPay has disabled account creation for debit cards using this BIN.
BANK_ACCOUNT_CREATION_BLOCKED
DailyPay has disabled account creation for accounts with this routing number and first four digits of account number.
INVALID_DEBIT_CARD
The user debit card information is invalid.
INVALID_CARD_TOKEN
The generic debit card token is invalid.
INVALID_USER_LOOKUP_QUERY
Email, phone number or custom field needs to be present.
LOOKUP_RESPONSE_LIMIT_EXCEEDED
More than "3" results returned from request.
ACTIVE_USER_REQUIRED
User must be registered with status ACTIVE, in order to "set primary bank account".
INELIGIBLE_CEWA_USER
User is ineligible for CEWA
INVALID_WISELY_USER_STATUS
User status must be one of active or review.
INACTIVE_WISELY_PA
Wisely provider account is not active.
INVALID_WISELY_REMAINDER_ACCOUNT
Invalid Remainder Account type for Wisely user. Must be a Wisely bank account.
INVALID_BANK_ACCOUNT_FORM
Provided bank account was invalid and bank account transfer account was not created.
INVALID_PROVIDER_BANK_ACCOUNT_FORM
Provided remainder account info was invalid and remainder account was not created.
INVALID_TRANSFER_ACCOUNT_FORM
Provided debit card was invalid and debit card transfer account was not created.
INVALID_TRANSFER_ACCOUNT_TYPE
Invalid Transfer Account Type.
INVALID_TRANSFER_ACCOUNT
Invalid or inactive transfer account.
INVALID_REPAYMENT_AMOUNT_PARAMS
direct_deposit_date, direct_deposit_amount and direct_deposit_currency need to be present.
INVALID_DATE
Date could not be parsed.
INVALID_GALILEO_TOKEN_DATA
Invalid Galileo card token data.
INVALID_TRANSFER_STATUS
Provided transfer payload was invalid and was not created.
INVALID_CURRENCY
Invalid currency. Valid currencies include "USD".
INVALID_TRANSFER_SCHEDULE
Allowed values for schedule are "INSTANT".
INVALID_TRANSFER_TYPE
Account is not eligible for "instant transfers".
INVALID_TRANSFER_DESTINATION
Transfer can only be made to "debit card".
MINIMUM_AMOUNT_SUBCEEDED
Invalid amount. Minimum transfer amount for this user is "$5".
INSUFFICIENT_AVAILABLE_BALANCE
Invalid amount. Requested amount greater than user available balance
MISSING_REMAINDER_ACCOUNT
A Remainder Account is required to make transfers but none was found for this user.
DUPLICATE_TRANSFER_ID
Transfer ID is not unique.
TRANSFER_LIMIT_EXCEEDED
You have reached the "10" transfer or attempted transfer limit within the past 24 hours. Check back tomorrow.
TRANSFER_AMOUNT_LIMIT_EXCEEDED
You have reached the "$200" transfer amount limit within the past 24 hours. Check back tomorrow.
USER_TOKEN_MISMATCH
When including user_id in path, ID must match user access token.
PATH_PARAM_MISSING
Must include "user_id" in path.
USER_NOT_ACTIVATABLE
User must be activated before "creating remainder account".
INVALID_FILTER_QUERY
Invalid filter query.
INVALID_FILTER_FIELD
"person_id" is an invalid field for this resource.
INVALID_FILTER_VALUE
The value "123" is an invalid type for "person_id".
INVALID_FIELD_OPERATION
"partial_match" is not permitted on "person_id".

Unauthorized

Client authorization is invalid.

Response Schema: application/json
code
required
string

A code that indicates the specific type of error.

Value: "UNAUTHORIZED"
Example: "UNAUTHORIZED"
description
required
string

A message that explains the meaning of the error code. Developers are advised not to make programmatic use of this value, as it may change.

Example: "Client or user may not be authorized to use the resource."
object
application/json
{
  • "code": "UNAUTHORIZED",
  • "description": "Client or user may not be authorized to use the resource.",
  • "details": {
    }
}

Forbidden

Client requires additional permissions or scopes.

Response Schema: application/json
code
required
string

A code that indicates the specific type of error.

Value: "UNAUTHORIZED"
Example: "UNAUTHORIZED"
description
required
string

A message that explains the meaning of the error code. Developers are advised not to make programmatic use of this value, as it may change.

Example: "Client or user may not be authorized to use the resource."
object
application/json
{
  • "code": "UNAUTHORIZED",
  • "description": "Client or user may not be authorized to use the resource.",
  • "details": {
    }
}

Not Found

Requested resource could not be found.

Response Schema: application/json
code
required
string

A code that indicates the specific type of error.

Value: "NOT_FOUND"
Example: "NOT_FOUND"
description
required
string

A message that explains the meaning of the error code. Developers are advised not to make programmatic use of this value, as it may change.

Example: "The request failed because the requested resource could not be found."
object
application/json
{
  • "code": "NOT_FOUND",
  • "description": "The request failed because the requested resource could not be found.",
  • "details": {
    }
}

Unknown

Server experienced an unknown or unexpected error.

Response Schema: application/json
code
required
string

A code that indicates the specific type of error.

Value: "UNKNOWN"
Example: "UNKNOWN"
description
required
string

A message that explains the meaning of the error code. Developers are advised not to make programmatic use of this value, as it may change.

Example: "Server experienced an unknown or unexpected error."
object
application/json
{
  • "code": "UNKNOWN",
  • "description": "Server experienced an unknown or unexpected error.",
  • "details": {
    }
}
➔ Next to Client Portal Guide