Create a customer
POST/customers
Create a customer
Request
Responses
- 200
- 400
- 401
- 409
- 429
- 500
Customer created successfully.
Invalid parameter value.
Cause: email was provided but isn't a valid email address
(error: invalid_param).
Fix: Check message for which field failed, correct the
request body, and resend.
Retry: Safe once the request body is corrected. Retrying the same unmodified request will fail again.
Missing or invalid API key.
Cause: One of three things; see error in the response body:
no_api_key: theAuthorizationheader was omitted entirely.invalid_api_key: a header was sent but the token isn't a recognized PayFlow key (wrong scheme, malformed, or a test-mode key used against production, or vice versa).api_key_expired: the key was valid but has since been rotated or revoked.
Fix: Send Authorization: Bearer <your API key>. For
api_key_expired, generate a new key in the Dashboard and update
the integration.
Retry: Safe, but will keep failing until a valid, current key for the right environment is supplied.
Duplicate request (idempotency conflict).
Cause: The Idempotency-Key header was reused, but the request
body doesn't match the first request that used that key.
Fix: Use a new, unique Idempotency-Key for a genuinely
different request. Re-send the original body if you meant to
retry the same operation.
Retry: Not safe to retry unchanged; the same conflict will recur. Retrying with the original body succeeds (idempotent replay) instead of erroring.
Rate limit exceeded.
Cause: Too many requests were sent from this API key within the current window.
Fix: Slow down request rate and honor the Retry-After header
if present. Consider batching or caching reads where possible.
Retry: Safe after waiting out the window; retrying immediately will fail again.
Response Headers
The maximum number of requests allowed per window.
Requests remaining in the current window.
Unix timestamp (seconds) when the current window resets.
Seconds to wait before retrying.
PayFlow server error.
Cause: An unexpected failure on PayFlow's side, not caused by the request.
Fix: Nothing to change in the request. If it persists, contact PayFlow Developer Support with the request ID.
Retry: Safe. Use an idempotency key on write requests so a retry can't create a duplicate if the original actually succeeded.