Skip to main content

Check Status

Use the Order Status API to fetch the real-time status of a payment order created using the Elite Neo Bank Payment Gateway. This API helps merchants:
  • Verify payment completion
  • Track transaction status
  • Validate redirected payments
  • Reconcile transactions securely
The Order Status API should always be used for final payment verification instead of relying only on frontend redirects.

Endpoint

To view all available base URLs and environments, refer to:

➡️ API Resources

Authentication required.

Refer to:
➡️ Headers
➡️ Signature Generation
➡️ Timestamp Validation

Request Parameters


Example Request Body


Example cURL Request


Example Success Response


Response Parameters


Payment Status Values


  1. Create Order API
  2. Redirect customer to hosted checkout
  3. Customer completes payment
  4. Receive redirect/webhook
  5. Call Order Status API
  6. Verify final payment status server-side

Why Order Status Verification is Important

Frontend redirects may not always guarantee successful payments due to:
  • Browser interruptions
  • Network failures
  • Customer closing the payment page
  • Delayed bank confirmations
Always verify transactions using the Order Status API before marking orders as successful.

Best Practices

  • Always validate payment status server-side
  • Verify webhook notifications
  • Store kwikX_order_id for reconciliation
  • Retry status checks for processing transactions
  • Avoid duplicate order IDs

Common Errors

400 Bad Request

Possible reasons:
  • Missing order_id
  • Invalid payload structure
  • Incorrect request format

401 Unauthorized

Possible reasons:
  • Invalid API key
  • Incorrect signature
  • Expired timestamp

Order Not Found

Possible reasons:
  • Invalid order ID
  • Order does not exist
  • Incorrect merchant credentials

If the payment status is:
Retry the status check after a few seconds before marking the transaction as failed.

Security Recommendations

  • Generate signatures server-side only
  • Never expose secret keys publicly
  • Use HTTPS only
  • Validate webhook signatures
  • Verify timestamps before processing responses