There are different errors you can receive while making the request

Oauth Error

While invoking request to Flexcharge endpoint, Braintree must receive the Flexcharge access token successfully by invoking /oauth2/token endpoint with the app_key and app_secret passed by the merchant. If we fail to obtain the access token we will return Oauth error in the response body.

{
  "error": "OAuth error",
  "message": {
    "oauth_error?": true,
    "oauth_status": 400,
    "error-category": "external"
  },
  "request-uuid": "a-unique-identifier-for-the-request"
}

Destination Errors

When something goes wrong with your request, the error code and description included in the response body will provide insight into the problem. Here is an example of what the response body would look like:

{
  "status": 401,
  "body": {
    "description": "The Authorization header token is invalid. Invalid access token",
    "code": 101216
  }
}

Vault Errors

When we are unable to load details associated with a payment method nonce.

{
  "error": "Vault error",
  "message": {
    "vault_error?": true,
    "vault_status": 404,
    "message": "payment_method_token not found"
  },
  "request-uuid": "a-unique-identifier-for-the-request"
}

Using Payment Method Nonce associated with a non-credit-card payment method

Only payment method nonces which are associated with a credit card will work for this config.

{
  "error": "No config specified for payment type",
  "message": {
    "vault_type": "some-non-credit-card-type",
    "supported_by_config": ["CreditCard"],
    "validation_error?": true,
    "error-category": "merchant"
  },
  "request-uuid": "a-unique-identifier-for-the-request"
}