> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rapidtopup.com.ng/llms.txt
> Use this file to discover all available pages before exploring further.

# Integration Checklist

> Complete these items before going live with your RapidTopup integration.

Use this checklist to ensure your integration is production-ready.

## Before Going Live

**1. Secure your API key**

Store your API key in an environment variable, not hardcoded in source code. Confirm it is **not** in any public repository.

**2. Test a real purchase**

Make at least one live purchase call and confirm the response contains a valid `reference`.

**3. Implement idempotency**

Every `POST /purchase` call includes a unique `idempotency_key`.

**4. Add two-step verification**

For all Cable TV and Electricity purchases, `GET /services/verify` is called first and the customer name is displayed to the user for confirmation.

**5. Set up webhooks**

A webhook URL is configured in the Developer Dashboard. Your endpoint verifies the `X-RapidTopup-Signature` header and returns `200 OK`.

**6. Implement /requery fallback**

If a webhook is missed or a purchase returns `pending`, your system calls `POST /requery` to sync the status.

**7. Handle retry logic**

Your app implements exponential backoff for `429 Too Many Requests` and `503` responses.

**8. Handle the pending status**

Your UI gracefully shows a "processing" state when a transaction returns `pending` instead of failing silently.

***

## Quick Reference

| Item | Endpoint |
| - | - |
| Check wallet before bulk purchases | `GET /balance` |
| Get valid `variation_code` values | `GET /services/data`, `/services/cable`, `/services/electricity` |
| Verify meter/smartcard before purchase | `GET /services/verify` |
| Submit purchase | `POST /purchase` |
| Check status of a pending transaction | `POST /requery` |

> [card] [Need help?](https://rapidtopup.com.ng/contact)
>
> Open a support ticket with your transaction `reference` or `error_id` and our team will respond within 24 hours.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.