API documentation

Sterling exposes a simple, body-authenticated payout API plus dynamic UPI collections. Every request is reviewed by a human before it settles. Your account_id and secret_key live on your dashboard under Developers.

1 · Initiate a payout

POST /api_payout_bank

Queues a bank/UPI payout for review. Idempotent on request_id. Provide account_number + ifsc for a bank transfer, or upi_id for UPI.

curl -X POST https://www.sterling.ezeematrix.com/api_payout_bank \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "YOUR_ACCOUNT_ID",
    "secret_key": "YOUR_SECRET_KEY",
    "request_id": "ORDER-1001",
    "amount": "500.00",
    "account_name": "Ravi Kumar",
    "account_number": "50100234567890",
    "ifsc": "HDFC0001234"
  }'

Response returns the request status (Pending until an admin approves), and — once approved — the bank utr.

2 · Fetch payout status

POST /api_payout_status

curl -X POST https://www.sterling.ezeematrix.com/api_payout_status \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "YOUR_ACCOUNT_ID",
    "secret_key": "YOUR_SECRET_KEY",
    "request_id": "ORDER-1001"
  }'

Status maps to Success (approved, with UTR), Pending, or Failed.

3 · Collections (pay-ins)

Create a pay-in and we mint a unique UPI QR encoding the exact amount and reference. Your customer scans, pays in any UPI app, and enters the UTR on a hosted page. You verify (or an admin does) before the wallet is credited.

4 · Webhooks

On payin.approved / payin.rejected / payout.approved / payout.rejected we POST a JSON envelope to your webhook URL, signed with HMAC-SHA256 (header X-Signature) using your webhook secret, within a replay window (X-Timestamp). Verify both before trusting the payload.