Skip to main content

Authentication

Use your API key as a Bearer token in the Authorization header for every request.
  • All requests must use HTTPS (TLS 1.2+). Requests made over HTTP are rejected.
  • Keep your secret keys secure and do not embed them in client-side code or mobile apps.
  • We return a per-request X-Request-Id you can reference when contacting support.
Never expose your secret API key in client-side code or mobile apps.

Idempotency (required for live POST requests)

To safely retry POST requests without duplicating operations, send an idempotency key:
  • Tie the idempotency key to your merchantTransactionId.
  • Reuse the exact same idempotency key when retrying the same logical request.
  • Repeating a POST with the same key returns the original response as long as method, path, and body are identical.
  • Conflicting retries (same key but different body) return 409 conflict.