Skip to content

Support

Before contacting support, check the basics:

  • Authentication failing? Read Authentication and confirm you’re using the right environment’s credentials at the right base URL. The most common issue: sandbox key against production base URL.
  • Body-binding mismatches? A 400 with error_code: "1101", "1102", or "1103" means the body’s (amount, currency, customer_reference) drifted from what the session was minted with. With Auth-v3 the SDK should omit those three fields entirely (the gateway reads them off the session) — legacy callers that still send them must keep them in lockstep with the session, or mint a fresh session.
  • Rate-limited? A 429 with error_code: "1301" honours Retry-After. See Rate limits.
  • Webhook missing? Check the notify_url allow-list in the dashboard — empty list rejects all. See Webhooks overview.

Every error envelope includes a request_id and (sometimes) a support_reference. Quote both when contacting support — the support team can pull the audit record with either.

{
"error": true,
"error_code": "1401",
"message": "Internal server error",
"request_id": "req_8f3a4c2e9b1d7a6f",
"support_reference": "sup_987654321",
...
}

Include:

  • The full request (URL, method, headers — redact Authorization, Idempotency-Key is fine to share).
  • The full response (status, headers, body).
  • The request_id from the envelope.
  • A timestamp in UTC.
  • Which environment (sandbox / staging / production).
  • Which SDK and version, if applicable.

Open an issue in the relevant repo:

When the corresponding GitHub repos are made public, they will be linked here.

Production status, planned maintenance windows, and incident postmortems live at status.pdirect.com (when available). Subscribe for incident notifications.