When you're working with Zamp's API, encountering a 500 error code can be confusing, especially when your transactions are successfully processed. Don't worry—this is a common issue, and we're here to help you understand and resolve it.

500 Error Code: This usually indicates an "Internal Service Error," but sometimes transactions are processed successfully despite this error.

Occasional occurrence: a 500 response sometimes appears even though the transaction processed. If it keeps happening for you, our engineering team can investigate the specific cases.

Successful Transactions with 500 Error: Even if you receive a 500 error code, your transaction might still be processed correctly.

If it continues: if you repeatedly see 500 errors, send us the details below and our engineering team will investigate those specific transactions.

Providing Details Helps: Sharing specific transaction details and timestamps can help us investigate more efficiently.

Sometimes, our API may return a 500 error code, which typically signals an "Internal Service Error." However, there are instances where the transaction is processed successfully despite this error. This can occur due to temporary server issues or other technical glitches.
​

If you see this repeatedly, our engineering team can investigate the specific transactions you report. Sharing the details below helps us trace them in the API logs.

If you encounter a 500 error code, providing specific details can significantly aid our investigation. Please share:

- The transaction IDs involved

- The exact time (in UTC) when the error occurred

For example, in a recent case, a customer provided transaction IDs and the timestamp, which helped us narrow down our search in the API logs.