This article covers the following topics:
PayPack Error Logs
PayPack keeps a log record of all processes for payment charges and refunds.
You can find logs under each NetSuite transaction’s subtab or by using the custom page searches listed below.
- PayPack Charge Logs
- PayPack Refund Logs
- PayPack Developer Logs (requires enabling debug mode in PayPack configuration)
Stripe Error Codes
Find the latest Stripe API error codes, HTTP status codes, and error types by visiting the links below.
HTTP STATUS CODE SUMMARY
| 200 - OK | Everything worked as expected. |
| 400 - Bad Request | The request was unacceptable, often due to missing a required parameter. |
| 401 - Unauthorized | No valid API key provided. |
| 402 - Request Failed | The parameters were valid but the request failed. |
| 403 - Forbidden | The API key doesn't have permissions to perform the request. |
| 404 - Not Found | The requested resource doesn't exist. |
| 409 - Conflict | The request conflicts with another request (perhaps due to using the same idempotent key). |
| 429 - Too Many Requests | Too many requests hit the API too quickly. We recommend an exponential backoff of your requests. |
| 500, 502, 503, 504 - Server Errors | Something went wrong on Stripe's end. (These are rare.) |
ERROR TYPES
| api_error | API errors cover any other type of problem (e.g., a temporary problem with Stripe's servers), and are extremely uncommon. |
| card_error | Card errors are the most common type of error you should expect to handle. They result when the user enters a card that can't be charged for some reason. |
| idempotency_error | Idempotency errors occur when anIdempotency-Keyis re-used on a request that does not match the first request's API endpoint and parameters. |
| invalid_request_error | Invalid request errors arise when your request has invalid parameters. |
Questions
If you have any questions, please contact us through the support widget.