Troubleshooting
Common errors
Troubleshooting API Requests
Review this information in case of any of these errors. If you are still
experiencing issues, please contact our support team and include in the support
request the header X-Trace-Id header value provided in all of our API responses.
| Error | Description | How to resolve |
|---|---|---|
| Using the incorrect API endpoint | Merchants send their request to an incorrect API endpoint. | Ensure the correct API endpoint is used, including the account number as part of the endpoint. Avoid trailing slashes or spaces in the URL. |
| Using HTTP | All API requests must be made over HTTPS. Calls made over plain HTTP will fail. | Always use HTTPS. |
| Payment method/currency not supported | Accounts support only a single payment method/currency combination. | Contact support for additional Test accounts or to request alternate payment methods. |
| Invalid parameters | The request includes invalid parameters. | Refer to the respective API Reference for valid parameters. |
| Invalid JSON | The structure of the API request body does not conform to the JSON schema standard. | Validate with a JSON validator tool and ensure valid characters are used. |
| Incorrect or missing authentication | Merchant provides incorrect JWS detached token token. | Refer to the Authentication section for instructions on how to pass credentials. Ensure the public/private key used is correct. |
| Incorrect content type | Content-Type header not properly set. | Review message format section |