Payment Errors

An overview of all related Payment errors on the client and server-side

Introduction

We use standard HTTP response codes for success and failure notifications. In general, 200 HTTP codes correspond to success, 40X codes are for a developer or user-related failures, and 50X codes are for Okra-related issues. We’re always working to minimize payment errors related to Okra integrations when initiating payments and to address connectivity issues across bank infrastructure.

Breakdown of an Okra Error

Name

Description

status

The HTTP status code associated with the error. This will only be returned in the response body when the error information is provided via a webhook.

message

A user-friendly representation of the error code. null if the error is not related to user action.
This may change over time and is not safe for programmatic use.

data

Response data from the API, including the details of the successful or failed response.

Method

The method that performs the error function

code

The particular error code

type

A broad categorization of the error. Safe for programmatic use.
Possible values: SUSPENDED, EMPTY_QUEUE, FLAGGED_USER, NO_RECORD_ID, RATE_LIMIT


Did this page help you?