Errors

What PayTomorrow error responses look like and how to fix the common ones.

HTTP status codes

StatusMeaning
200Success.
401 UnauthorizedThe access token is missing, expired, or from the other environment. Get a new token and retry once.
417 Expectation FailedThe request was understood but rejected. Validation errors and business-rule errors both use this status. Read errorDetails.
5xxSomething went wrong on PayTomorrow's side. Read-only requests can be retried with backoff. For a mutation, first reconcile whether it succeeded; do not blindly repeat order creation, settlement, or refunds. Contact support with the request time and path when the outcome is unknown.

Error body

Errors return JSON with the reason in errorDetails:

{
  "timestamp": "2026-09-23T18:04:11.532Z",
  "status": "EXPECTATION_FAILED",
  "path": "/application/ecommerce/orders",
  "error": "Expectation Failed",
  "errorDetails": "Seems like the json you sent is missing info or has the wrong format:  - property email must be a valid email address, you sent: 'jordan@'"
}

The same message is also sent in an error response header.

Common errors

Getting help

When you contact support, include:

  • the environment (staging or production)
  • the application token or pt_id
  • the request path and the time it failed
  • the full errorDetails

Never include your API password or API Signature.

On this page