Skip to main content
If the Network Tokenization API fails, you’ll receive an error in the format of the following example:
Some errors include a details array containing field-level information, including a location (the camelCase property name that caused the error) and a message describing the issue. This information doesn’t contain PAN or cardholder data and is safe to surface to end users. For example, a ValidationFailed error always includes details:

HTTP Response Codes

What endpoint you call determines the types of HTTP response codes you can potentially receive. This table outlines the types of errors you can receive:

API Error Details

A 500 response indicates an unexpected internal error rather than a business-logic failure. It isn’t associated with any of the named error reasons above. If you receive one, contact your Pagos Account Manager and provide them with the requestId value from the error response body.