AdeyVerify

Subscriptions & Billing

Plans, checkout, and payment confirmation

Every organization has its own subscription. Plans, prices, and request limits are configured by AdeyVerify administrators — nothing is hardcoded in the application.

Checking out

  1. GET /api/v1/subscriptions/plans — list available plans.
  2. POST /api/v1/subscriptions/checkout with a planId and paymentMethod (CBE or TELEBIRR) — this creates a pending subscription and returns the platform's own account to pay into.
  3. Pay that amount via the chosen method, then POST /api/v1/subscriptions/checkout/{billingTransactionId}/confirm with the transaction reference (or receipt/SMS) you paid with.

Step 3 reuses the exact same transaction verification engine used for the public API: AdeyVerify checks that the payment was actually credited to its own account, for at least the plan's price, before activating your subscription. A receipt can't be reused to activate two subscriptions — the same replay protection applies here as everywhere else.

curl -X POST https://your-api/api/v1/subscriptions/checkout/{billingTransactionId}/confirm \
  -H "Authorization: Bearer av_test_..." \
  -H "Content-Type: application/json" \
  -d '{"reference": "DIH1TJ194T"}'

A subscription is only ever marked active after the payment is independently verified — never on request alone.

Nothing else is blocked

An inactive or lapsed subscription never blocks access to your dashboard, account, or these docs — it only affects which verification services your plan includes.

Manage plans, view payment history, and re-run checkout from the dashboard's Subscription & Billing page.

On this page