SMILEKARO PAY DEVELOPERS

Own API. Clear payment states.

Integrate directly with akqr.in. This API is independent of IMB and every other payment gateway. The current version is a safe test environment with payments disabled.

!
Test mode — requests only create PENDING orders. Until a verified payment provider is connected, do not request funds or fulfil orders based on these responses.

1. Create a test API key

Open Dashboard → API credentials, create a key, then copy it immediately. It is shown once. Store it only on your trusted server. Header: x-smilepay-key.

2. Create order

POST https://akqr.in/api/v1/orders

curl -X POST 'https://akqr.in/api/v1/orders' \
  -H 'Content-Type: application/json' \
  -H 'x-smilepay-key: YOUR_TEST_API_KEY' \
  -d '{"order_id":"SHOP-ORDER-1001","amount":"149.00","payer_phone":""}'

Response includes order with status: PENDING and an HTTPS checkout_url on our payment host. The same order ID is idempotent for the same amount.

3. Check order status

curl -H 'x-smilepay-key: YOUR_TEST_API_KEY' \
  'https://akqr.in/api/v1/orders/SHOP-ORDER-1001'

Do not treat a browser redirect or payer message as proof of payment. SUCCESS will only be available after signed server-side verification with an approved payment provider is implemented.

4. Dashboard & hosted checkout APIs

EndpointPurposeAuthentication
GET /api/console/bootstrapDashboard analytics and recent ordersMerchant cookie
GET/POST /api/console/itemsPayment links & pagesMerchant cookie
GET/POST /api/console/receiversReceiving account configurationsMerchant cookie
GET/POST /api/console/keysCreate/view test integration keysMerchant cookie
GET/PUT /api/console/settingsCheckout branding, URLs, webhook settingMerchant cookie
GET https://pay.akqr.in/api/public/p/<id>Hosted payment-page detailsPublic token

5. Webhooks & status verification

Saving a webhook URL in the dashboard does not activate callbacks. Future live integration must verify provider signatures, compare amount/order/merchant, enforce idempotency, then dispatch authenticated webhooks with logged delivery attempts and retries. No API credential or wallet secret should ever appear in a browser.

Go to API credentials →