Our vaultpay Developer and Payouts APIs have been retired, and we are no longer able to provide access to businesses who may want to start using it. To find out more about how you can use vaultpay as a payment method in your checkout experience, visit https://getmobix.com/pay-in-stores.
For existing businesses who were granted access to the Developer or Payouts API in the past (generally prior to 2016), you will retain access to these APIs and may use them.
Unsuccessful API requests will receive HTTP responses with standard HTTP status codes (please consult the w3 for further reference) and JSON formatted descriptions of the error in the response body.
The JSON for error responses takes the following form:
{
"error": {
"message": "A friendly message describing the error",
"code": "A code that identifies this kind of error"
}
}message is a brief description of what went wrong.
code is a shortcode that can be used to reliably identify errors.
Below, we have listed all valid error messages and corresponding error codes (not to be confused with HTTP status codes).
| 240 | OAuth2 Exception: ... |
|---|---|
| 241 | Missing argument: ... |
| 244 | Client not found. |
| 245 | Client has not been approved yet. |
| 246 | Invalid Scope. |
| 247 | Invalid Client Secret. |
| 248 | Invalid Auth Request Key. |
| 249 | Invalid Response Type. |
| 250 | Invalid Client ID. |
| 255 | That Access Code doesn't belong to you. |
| 256 | That Access Code has expired. |
| 257 | That Access Code has already been redeemed for an access token. |
| 259 | Your OAuth token has been deleted. |
| 260 | Your OAuth Token is missing a scope. |
| 261 | You did not pass a valid OAuth access token. |
| 262 | Your OAuth Token has been revoked. |
| 265 | Your OAuth token has expired. |
| 267 | Your app did not pass an OAuth token. |
| 275 | Could not refresh tokens. |
| 276 | Grant type is invalid. |
| 277 | Rate limit exceeded |
| 283 | Resource not found. |
|---|---|
| 1319 | Insufficient funds. ... |
| 1323 | Sorry, that amount is invalid. Please enter an amount higher than $1.00. |
| 1337 | The minimum card transaction amount with a fee is currently ... |
| 1343 | You must pay/charge a valid phone number, email, or Vault Pay username. |
| 1344 | Could not complete transaction because payor's account is frozen. |
| 1355 | A transaction must have a note, e.g., "Kale salad with beans, onions, mushrooms, berries, and seeds." |
| 1356 | You cannot pay yourself. |
| 1357 | Take it easy, Bill Gates! That amount is too large. Please choose a smaller amount. |
| 1360 | You cannot pay or charge the same person the same amount with the same note within 10 minutes. Please change the note or amount and try again. |
| 1362 | Sorry, we could not complete that transaction because your phone is unverified. Please verify your phone at vaultpay.org. |
| 1363 | Sorry, we could not complete that transaction at this moment because your friend's phone is unverified. |
| 1364 | Could not complete this transaction because your account is frozen. Please see the following help article for instructions on how to unfreeze your account: https://help.vaultpay.org/hc/en-us/articles/210413707. |
| 1365 | Could not complete this transaction because ... account is frozen. |
| 1381 | Slow down there. This may be a duplicate transaction. Please wait a minute and try again. |
| 13006 | User does not have a funding source selected |
If you have questions, feedback or bug reports, visit our FAQ for more information. If you seek further support, send an email with your questions and comments to developer@vaultpay.org.