DStv subscription API for Nigerian applications

A DStv checkout should show the selected package and decoder together. A package name in an old receipt is useful context, but it should not become a permanent price list or a hardcoded purchasing rule.

Design the checkout

Use provider=DSTV when loading packages and service=DSTV in the purchase. Keep any billing period included in the catalogue label visible to the customer. Verify the smart number before confirming the subscription purchase.

Discover current products

Use a sandbox key with the view_products scope. Keep the key in a server environment variable. The request below reads the catalogue; it does not buy a service.

curl --fail-with-body --silent --show-error --max-time 20 \
  -H "Authorization: Bearer ${RIZPAY_API_KEY:?Set a sandbox API key}" \
  "https://my.rizpay.app/api/partners/sandbox/v1/products/cabletv?provider=DSTV"

Read products from data and their details from attributes. Follow pagination.total_pages when you need the complete list. Select an actual returned ID, not a guessed or documentation-example ID. Catalogue availability can change: refresh an unavailable selection and let the customer choose again.

Cable TV packages have fixed catalogue costs. Read price.amount, then calculate the retail price in your own system. Preserve the selected package label and the price the customer confirmed for the receipt. If either changes before purchase, ask for confirmation again instead of quietly charging a new total.

Confirm the payment target

Before purchasing, POST to /purchases/verify with product_id and smart_number. Continue only when data.verified is true and the customer confirms the returned details. Keep smart numbers as strings. Verification must correspond to the selected provider and package.

Prepare one purchase per order

The purchase request uses product_id, service, smart_number, external_reference. Enable the relevant purchase permission (purchase_cable_tv) and read_transactions for status checks. Confirm your key's permissions against the authentication reference when moving from sandbox to production.

This is the JSON body shape for a sandbox purchase. Replace every dollar-prefixed placeholder before sending it, using the product you selected and your stored order reference. Leave the optional phone number out of a sandbox cable body: the sandbox picks its outcome from the first recipient field present, so a phone number would replace the smart number as the fixture selector. The recipient values below are sandbox fixtures, not real recipients. For variable-amount products, choose an amount within the selected product's limits.

{
  "product_id": "$RIZPAY_PRODUCT_ID",
  "smart_number": "1212121212",
  "service": "DSTV",
  "external_reference": "$RIZPAY_ORDER_REFERENCE"
}

Send the body to POST /api/partners/sandbox/v1/purchases. Generate and persist the reference once for the order, following the documented format. Do not make a new reference simply because a request timed out. Keep product selection, pricing and authorization on your server; a browser or mobile app must never contain the partner secret.

Follow the result

Persist data.id from an accepted purchase and inspect data.attributes.status. An accepted request can still be pending. Read the existing purchase with GET /purchases/:id and reconcile signed webhook events with your stored order. If the response was lost, look up the existing external reference before considering another purchase.

A DUPLICATE_REFERENCE response establishes that a reference has already been used; it does not prove fulfillment. Retrieve the existing transaction and check its status. Only successful is a completed purchase. Handle failed and reversed outcomes according to the returned transaction and your own ledger; do not issue a second refund because the same event arrives again.

Does a successful API request prove the decoder is showing channels?

An accepted request is not the final subscription result. Track the transaction to its final status. If service is still not visible after a successful purchase, use the existing receipt and support process instead of buying again.

Before accepting real orders

Test a successful purchase, an unresolved pending result and a failure. Confirm that a repeated submit cannot make a second local order and that the receipt reflects the final state. Use the sandbox's configured test recipients rather than arbitrary phone or meter numbers. Sandbox delivery is simulated and is not a measurement of live biller reliability.

Read the product reference, sandbox guide and pricing explanation before enabling production access.