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)
- Navigate to a Sales Order or Invoice → novamodule subtab → PayPack Charge Logs.
- Click customize view.
- Add column to view Payment Method Details.
- Click save.
The below are examples of common error messages and troubleshooting solutions.
|Invalid Payload when syncing customer to Stripe manually.||No email address on the customer record. Check the configuration saved search that is used for customer syncing.|
|No such customer: 'cus_N1C3tRaelKyvFk'; a similar object exists in test mode, but a live mode key was used to make this request.||This occurs when a NetSuite customer has already been synced to a Stripe Test Mode environment with test mode key. To fix, remove the value in the customer's field Stripe Customer Id (PayPack) and re-sync.|
|Multiple customers with same email exists in Stripe||In the event Stripe has multiple customers with the same email address, it is best to manually import the corresponding Stripe Customer ID to the NetSuite Customer record. This can be manually done or using NetSuite CSV Imports.|
|Unable to load the payment form. Please contact us.||
A payment link will be generated on a NetSuite Sales Order, Invoice, or Invoice Group record. The script is a user event type that runs after submit.
In certain situations when other NetSuite scripts are running, the payment link script may be delayed in executing. Please troubleshoot what other scripts may be causing the delay.
For other scenarios, bad HTML in the payment link header design can also cause the page to break.
Lastly, always check to see if another customer deposit or customer payment has already been applied to the transaction.
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.)|
|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.|