Errors
Keep in mind that you can receive errors described in SDK Errors and Web-Library Errors on top of the one listed here. The errors described here are thrown only from the from LimePay's API.
Error Name | Code | Message | Description | Occurence |
|
| Token is not provided | You are required to provide Lime Pay token for authorization where it is applicable | Accessing resources which require token authorization |
|
| Invalid token provided | You will get this error if the token provided is invalid | Accessing resources which require token authorization |
|
| Unauthorized request | You will get this error if your non-token authorization fails | Accessing resources which require non-token authorization |
Error Name | Code | Message | Description | Occurence |
|
| Insufficient token amount in escrow contract | You will get this error if your organization's escrow contract does not have enough tokens to fund a shopper | Processing payment |
|
| Insufficient wei amount in escrow contract | You will get this error if your organisation's escrow contract does not have enough wei to fund a shopper | Processing payment |
|
| Invalid gas limit | You will get this error if the gas limit of a signed transaction does not match the provided gas limit on payment creation | Processing payment |
|
| Invalid receiver | You will get this error if the | Processing payment |
|
| Invalid gas price | You will get this error if the | Processing payment |
|
| Method ID/function signature mismatch | You will get this error if a shopper signs different function from the one provided on payment creation | Processing payment |
|
| Function params does not match | You will get this error if a shopper signs a function with different parameter/s from the corresponding one that was provided on payment creation | Processing payment |
|
| Array of signed transactions must be provided | You are required to provide signed transactions in order to process fiat/relayed payment | Processing payment |
|
| Invalid number of signed transactions | The number of signed transactions must be the same as the number of generic transactions provided on payment creation | Processing payment |
|
| Invalid signer. The transactions were not signed by the Shopper's private key | The signer of the transactions (his public address) should be equal to the shopper's | Processing payment |
|
| Cannot decode generic transaction data! | You will get this error if a provided signed transaction is not valid or the parameter types provided on payment creation are not valid | Processing payment |
|
| Invalid signer. The Authorization signature is not signed by signer's wallet | You will get this error if the provided authorization signature for the funding of the shopper is not signed by a | Creating payment |
|
| {authorizationSignature} is not a valid authorization signature | You will get this error if the provided authorization signature for the funding of the shopper does not have the correct format | Creating payment |
Error Name | Code | Message | Description | Occurence |
|
| Payment was not found | The requested payment does not exist | Getting payment |
|
| Payment document was not found | You will get this error if you try to preview invoice/receipt or send invoice for a payment which is not successful | Preview invoice/receipt / send invoice |
|
| Vendor was not found | The requested vendor does not exist | Getting vendor |
|
| Shopper was not found | The requested shopper does not exist | Getting shopper |
|
| API User was not found! | The requested API user does not exist | Getting api user |
|
| User was not found | The requested user does not exist | Getting user |
|
| The record you have searched for does not exists | You will get this error if your searching criteria is invalid | Every time we cannot parse searching criteria |
Error Name | Code | Message | Description | Occurence |
|
| Invalid property {property}! {property} cannot be null, empty or whitespace | You will get this error when you do not provide a required property in the request | Everywhere where there is request body with required properties |
|
| Missing {request body object} data | You will get this error when you do not provide a required object in the request | Everywhere where there is request body with required objects |
|
| Property {property}should be an array of objects | You will get this error when a property is array of objects, but you provide something different | Everywhere where there is request body with array of objects type properties |
|
| Nonexistent country code | You will get this error if you pass non-existing country code to Vendor, CardHolderInformation | Processing Fiat payment / calculating VAT |
|
| (Input property) should be true/false | You will get this error if you pass non-boolean value to a property which is required to be boolean | Processing payment |
|
| WeiAmount must have non-zero value | You will get this error if your | Creating payment |
|
| Vat number {vat number here} is invalid | You will get this error if you pass invalid VAT number in CardHolderInformation | Creating vendor / Processing Fiat payment |
|
| Vat number is empty | You will get this error if you have vat number as property in CardHolderInformation, but it does not have a value | Creating vendor / Processing Fiat payment |
|
| {vat rate} is not a valid VAR rate for your country | You will get this error if you have provided an invalid REDUCED vat rate | Calculating the VAT for a fiat payment/processing payment with a reduced vat rate |
|
| [{some property}] should be Number | You will get this error if you have provided reduced vat rate that was not number | Calculating the VAT for a fiat payment/processing payment with a reduced vat rate |
|
| API user credentials limit has been exceeded, limit is 3 | You will get this error if you try to create more than 3 API Credentials | Creating API Credentials |
Error Name | Code | Message | Description | Occurence |
|
| Something went wrong. Contact your support for more information | General error | - |
|
| Bad request | You will get this error if you pass wrong input parameter | Every time bad input is passed |
|
| Too many requests, please try again later. | You will get this error if you exceed LimePay API rate limit | Every time rate limit is exceeded |
Error Name | Code | Message | Description | Occurence |
|
| Signature metadata for Payment cannot be retrieved | If your escrow contract is version 1 (by default all of them are version 2), you will get this error when you execute | Getting signature metadata for payment |
|
| Payment has already been processed | You are allowed to create a payment and process it, but not re-process it | Processing payment |
|
| Payment can't be processed, because shopper is malicious | You will get this error if a shopper is flagged as malicious one. You need to contact support once this error occurs | Processing payment |
|
| Payment can't be created, while another one is in processing state | You will get this error if you try to create new payment for a shopper, while another one is in processing state | Creating payment |
|
| Invalid payment amount | The Payment's amount must be bigger than 1 USD | Creating payment |
|
| Transactions with the given currency are not allowed | The provided currency is not supported | Creating payment |
|
| Cannot get payment token | You will get this error if for some reason you cannot get | Retrieving payment token |
May Vary |
| {payment transaction error} | You will get this error if LimePay's Payment Provider cannot process the payment for some reason. Possible Values for Error name are: | Processing Fiat payment |
Error Name | Code | Message | Description | Occurence |
|
| Shopper is invalid | You will get this error if you try to create a payment for invalid shopper | Creating payment |
|
| Cannot update the wallet of a Shopper that is using LimePay powered Wallet | You will get this error if you try to update a Shopper's | Updating Shopper |
|
| Cannot get Encrypted wallet for Shopper that is not using LimePay powered wallet | You will get this error if you try to get/save/change the Encrypted Wallet of a Shopper that do not use LimePay powered wallets | GET/CREATE/Change the encrypted Wallet of a shopper |
|
| No Wallet is saved for the requested shopper. Create the wallet first | You will get this error if you try to create a payment, get or change the encrypted wallet of a Shopper that does not have LimePay powered wallet yet | Create Payment, GET Encrypted Wallet, Change the password of a Encrypted wallet |
|
| Shopper already has LimePay powered wallet | When you try to create Encrypted Wallet for a Shopper that already has one | Create Encrypted Wallet for a Shopper |
|
| Invalid mnemonic was provided | When you want to change the password of a Encrypted Wallet for a Shopper and you provide wrong mnemonic | Change the password of a encrypted wallet |
