Verify an order

The authoritative answer to “did this order get paid?”. Call it from your backend with your secret key before you release goods, credit an account, or mark an order complete.

Endpoint

POST https://api-v4.reeple.ai/charge/order/verify

Authentication

Authenticate with your secret key in the api-key header — not your public key.

api-key: YOUR_SECRET_KEY

Your secret key must never reach the browser. This endpoint exists precisely so that confirmation happens somewhere the customer cannot influence.

Request body

Plain JSON — this endpoint is not encrypted.

Field	Type	Description
`reference`	String	Required. The order reference from Create an order.

{ "reference": "order-2026-0001" }

Request example

curl -X POST https://api-v4.reeple.ai/charge/order/verify \
  -H "Content-Type: application/json" \
  -H "api-key: YOUR_SECRET_KEY" \
  -d '{ "reference": "order-2026-0001" }'

Response

Returns the order’s settled state, in the same shape as Get order status.

{
  "status": "Successful",
  "statusCode": "00",
  "message": "Transaction was completed successfully",
  "data": {
    "isFinalStatus": true,
    "requeryNeeded": false,
    "orderSummary": {
      "orderReference": "order-2026-0001",
      "totalChargedAmount": 530,
      "fee": 30,
      "statusId": 5,
      "status": "Successful",
      "paymentType": "C",
      "paymentResponseCode": "00"
    }
  }
}

What to check before fulfilling

The status is final and successful

isFinalStatus is true and orderSummary.status is Successful.

The amount matches

totalChargedAmount is at least what you expected for this order. This protects you if a reference is ever replayed or tampered with.

You haven't already fulfilled it

Record fulfilment against the reference and make repeat verifications no-ops — you will see the same successful response more than once.

Verify against the reference you stored for the order, not one taken from a callback query string. A reference supplied by the browser is attacker-controlled until you’ve matched it to one of your own orders.

Common errors

Code	Message	Cause
`401`	`Invalid SECRET key. Please check and try again`	Wrong key type, or a key from the other environment
`13`	`Order not found at the moment`	The reference doesn’t match an order

Verify or status?

	Get order status	Verify an order
Key	Public	Secret
Body	Encrypted	Plain JSON
Safe from a browser	Yes	No
Use for	Updating your checkout UI while the customer waits	Deciding to fulfil

Callbacks and verification

The full server-side verification flow, with a worked example.

Get Started

Orders

Payment Methods

Banks

Payment Links

Tokenized Charge

Verification

Refunds

Utility

Endpoint

Authentication

Request body

Request example

Response

What to check before fulfilling

Common errors

Verify or status?

Callbacks and verification

​Endpoint

​Authentication

​Request body

​Request example

​Response

​What to check before fulfilling

​Common errors

​Verify or status?

Callbacks and verification

Endpoint

Authentication

Request body

Request example

Response

What to check before fulfilling

Common errors

Verify or status?