Errors
To help you identify and fix any errors that you may encounter, our errors follow RFC-7807 standards.
Our errors include the following fields:
type
- Link to our developer portal for more information about the error.title
- Short description about the error.status
- HTTP status code.detail
- Longer description about the error.
Depending on the type of error we may return additional fields.
Errors
API error
We can’t process your request. We also return an errors
array that contains a message
field for each error. The message
field provides more detail about the error.
Example code
Bad request
Your request is missing a parameter, or a value is in the wrong format. To help you identify the parameter, we also return an errors
array that contains the following fields for each incorrect parameter:
parameter
- Name of the parameter that contains the error.detail
- Short description of the error.message
- Longer description of the error.
Example code
Cannot be modified
You attempted to change a resource that can’t be changed.
Example code
Capabilities missing
The terminal can’t run the action. We return an errors
array that contains a message
field for each error. The message
field provides more information about the error.
Example code
Card type is not supported
You can’t run transactions with the card type that you provided in the request.
Example code
Contract already signed
We couldn’t resend the email because the merchant already signed the contract.
Example code
Currency is not supported
You can’t process transactions with the currency that you provided in the request.
Example code
Forbidden
You don’t have permission to perform the action that you requested.
Example code
Funding accounts limit reached
Funding accounts restricted. You can not have any more than two funding accounts attached to this entity.
Example code
Funding accounts restricted
You created funding instructions for a funding account that can’t receive funds.
If the status of the funding account is pending
or rejected
, the funding account can’t receive funds. To check the status of a funding account, send a GET request to the Funding Accounts endpoint.
Example code
Idempotency key in use
You supplied an idempotency key that you used in a previous request. Idempotency keys must be unique.
Example code
Idempotency key missing
Your request didn’t contain an idempotency key. You must supply a unique idempotency key for POST requests and PATCH requests.
Example code
Insufficient funds
You don’t have enough funds to send to your merchant. View the balance of your funding account to check what funds are available to send to your merchant.
Example code
KYC check failed
We didn’t create your entity because it failed our Know Your Customer (KYC) check.
Example code
National ID in use
One or more supplied national IDs are not unique. All national IDs must be unique.
Example code
No control prong or authorized signatory
Your request didn’t indicate which owner is the control prong or the authorized signatory. Set one owner as the control prong or the authorized signatory.
Example code
No pricing agreement exists for the processing account
We couldn’t resend the email because there is no pricing agreement for the processing account.
Example code
Not acceptable
We can’t send a response in the MIME-type format that you requested. We return responses only in application/json.
Example code
Not authorized
We can’t verify your identity. This can occur if your Bearer token has expired.
Example code
Not found
We can’t find the resource that you requested. We also return a resource
field that contains the name of the resource. Make sure that you have included the correct URI.
Example code
Not requested by email
We couldn’t resend the email to the merchant because you didn’t originally choose to send the information by email.
Example code
Payload too large
Your payload is too large. If you’re uploading a document, make sure that each attachment is less than 6MB.
Example code
Processing terminal was not accepted
The terminal can’t run your request. We return an errors
array that contains a message
field for each error. The message
field provides more information about the error.
Example code
Resource already exists
You attempted to create a resource that already exists.
Example code
Search too broad
Your request has produced a list of results that is too large. Narrow your search criteria.
Example code
Tax ID in use
The tax ID that you supplied is already in use. Supply a unique tax ID.
Example code
Too many control prongs
Your request included more than one owner as the control prong. You can set only one owner as the control prong.
Example code
Unsupported media type
Your payload is the wrong format. If you’re uploading a document, make sure that your attachments are in one of the following formats:
- application/pdf
- image/png
- image/bmp
- image/gif
- image/jpeg
- image/heic
- image/heif
Example code
Volume limit has been reached
This request exceeds the processing limit that we permit on your account. We return an errors
array that contains a detail
field and a message
field for each error. The message
field provides more information about the error.