Errors

A failed request returns an error object, and its type determines how to handle it. The HTTP status is 4xx when the request can’t be completed, such as a missing parameter or a declined card, and 5xx when the error is on Bias’s side.

Invalid request errors that an integration can handle have a code. Payment errors have a decline_code, listed in decline codes.

An error’s message is written for developers. customer_message is safe to show to the customer, such as for a card decline or an expired discount code, and is null when Bias has no customer wording for the error.

The request-id response header identifies the request. Include it when you contact support.

The Error object

Handling errors

• Retry a rate_limit_error after the number of seconds in its Retry-After header.
• Retry a server_error with exponential backoff.
• For a payment_error, the decline code says whether to retry or ask the customer for another payment method.

An idempotency key makes it safe to retry a request after a network failure.

Errors in the SDKs

The Python SDK raises a typed exception for each error type, and the Rust SDK returns Err(biaspay::Error::Api(_)).

The TypeScript SDK returns API errors as values, typed as a union with the successful response. Only network and other fetch errors are thrown.

const customer = await bias.customers.create();
customer satisfies Customer | InvalidRequestError | IdempotencyError | RateLimitError | ServerError;

if (customer.object === "error") {
    throw new Error(customer.error.message);
}