Reference5 min read

Go-live checklist

What reviewers check before your app is approved for production.

Look-up tables. Come here when something breaks.

Work through this before you submit for approval. Most rejections are not technical, they are a missing description, an unreachable notification URL, or an obligation nobody read.

Your application

  • The app description explains, in plain words, exactly what a customer is paying for.
  • The CaaS API is enabled on the application and the charging details are complete.
  • The notification URL is public, HTTPS, and already live, not a placeholder.
  • The redirect URL points at a real page that handles both success and failure.

Your integration

  • The API Secret exists only on your server. It is not in client-side code, a mobile binary, or version control.
  • Every request generates a fresh unique 15-digit request ID.
  • Fulfilment is driven by the async notification, never by the browser redirect.
  • The callback handler is idempotent, a replayed notification cannot grant access twice.
  • Raw notification payloads are logged and retained for reconciliation.
  • Server clocks are synchronised with NTP so request times do not drift.

What your customer sees

  • The price is shown before the customer commits, in taka.
  • Insufficient balance (E3009) has its own friendly screen with a retry option, this will be your most common failure.
  • No raw error code is ever displayed to a customer.
  • For subscriptions, cancelling is obvious and works.
  • A support contact is visible inside the app.

Your obligations

  • You can respond to any customer query or claim within 24 hours. This is a binding term, not an aspiration.
  • You hold documented authorisation for any third-party service you resell, and can produce it on request.
  • Your content does not breach the prohibited-content rules in the developer terms.
  • Marketing material has been sent to support@digimart.store for approval before publication.
  • You are not using the hSenid logo, and you use the hSenid name only in standard, non-bold font.

Then submit

A Digimart administrator reviews the application. Once approved, you can publish your service publicly. Chase a pending review at support@digimart.store.