Errors

For more information, please see the documentation at here.

There are two base error formats that can be returned in card issuing: Bad Request and Internal. Below are the common elements of both types of errors. Depending on the endpoint more fields may be available.

Bad Request Errors

Bad request error are any errors that can be resolved by the requester. This includes but is not limited to:

• Malformed request body or URL
  
• Resource not found
  
• Request violates configuration or status of entity
  

In most cases a bad request can only be resolved by changing the request or making a change to the entity. There are some conditions that will resolve on their own, mostly status and limit conditions.

HTTP Status Codes

Body Response Format:

{
    "error": {
        "code": "Error code that can be programmatically checked against",
        "message": "Human readable error message, subject to change"
    }
}

Internal Errors

Internal errors are errors that are encountered in fulfilling a request that cannot be resolved by a caller. In general, errors with HTTPS status codes 503 and 504 will resolve themselves after a period of time.

Internal errors are returned with a tracking code. This code is used to help investigate or reconcile issues that have occurred.

HTTP Status Codes

Body Response Format:

{
    "error": {
        "code": "Error code that can be programmatically checked against",
        "message": "Human readable error message, subject to change",
        "tracking_code": "41519fff-439c-4d3d-ab33-4b74c763d2de"
    }
}

Cardholders, Accounts and Cards

The actions that can be performed with a card or account are limited by their status. For actions taken through the API or through Berkeley’s portals only the account status is relevant.

Of special note is the status awaiting_processor. While accounts do not need to be active to load accounts in this temporary state will fail to load. It is possible to retry the load after this state has cleared.

Statuses

Value Loads

Limit Based Errors

Value loads are subject to limits on the amount of funds and the number of load operations that can be completed. These limits are set up on a per program basis.

Below is a table of error codes associated with load limits:

Value Load Transaction Codes

Please contact support to see if the following codes are relevant/available on a per program basis.

The following transaction codes can be passed in the transaction_code field for both value load and unload.

transaction_code

ACH

ACH is a batch process. This means that when an ACH transaction is created it is not yet completed. It’s status can be checked using the ACH Transaction History endpoint.

ACH Status Codes

These status codes shows the processors current progress in completing the ACH transfer.

📘

Related pages:

Card Issuing Certification and Onboarding
Secondary Authorizations
Simulate Authorization and Settlement