Available Subscription Channels

To run a successful premium messaging campaign, you need a large database of subscribers. Our premium billing gateway allows you to subscribe users through the following channels :

SMS Subscription Options

You are required to to build a list of only consenting subscribers. There are a number of reasons for this requirement:

  1. It is a legal requirement set forth by regulatory bodies and mobile networks.
  2. To prevent unscrupulous Content Providers from spamming mobile user.
  3. To be able to verify the consent of subscribers.

SMS Subscriptions
 A major channel for premium service subscriptions is SMS. To subscribe users onto a premium content service via SMS, you need to be assigned a keyword and a short code.

A user then subscribes to your service by sending your service assigned keyword (e.g. join) to your assigned short code (e.g. 1944).

You can implement SMS subscriptions through the Receive SMS API.

Flow for SMS subscription

Web Subscriptions

To acquire subscribers through the web, a content provider needs to provide a publicly accessible website (eg JumpFon) for users to provide mobile number and network provider details.

After receiving subscription details (mobile number and network), the Content Provider sends a PIN code to the user’s mobile phone to be re-entered into the website for subscription confirmation.

Flow for Web Subscription

  1. The user provides a phone number and a network provider on the Content Provider’s website.
  2. The Content Provider then sends the PIN to the user through an SMS.
  3. The user enters the PIN into website to confirm his or her subscription.
  4. A welcome message is sent to the user to confirm subscription – this is sent from the default auto-response allowed on the short code from your Unity account.

WAP Subscriptions
 WAP subscriptions enable mobile phone users to subscribe to premium services via a WAP site. It is similar to web subscriptions.

Flow for WAP subscriptions

  1. Mobile phone user navigates to the WAP site and selects a premium service.
  2. Service details and related charges are presented to the user on the WAP site.
  3. User is requested to enter his phone number to proceed with subscription.
  4. A free SMS containing a confirmation URL is sent to the user.
  5. User confirms subscription by tapping on the URL provided
  6. A welcome message is sent to the user to confirm subscription – this is sent from the default auto-response allowed on the short code

USSD Subscriptions.

USSD is another channel through which premium Content Providers can manage service subscriptions.

Users dial a USSD service code and are directed through a series of menus to result in a subscription.

The flow for a USSD subscription flow is described below:

Flow for USSD subscription 

  1. The user initiates a USSD dial, eg*714#.
  2. The user then receives a menu of possible services to subscribe to.
  3. After selecting the preferred service, the user is presented with service charge, billing frequency and an unsubscription option.
  4. User is only subscribed after they provide their consent to the charges and service details by selecting the right menu option

In-app purchases 

In-app purchases are purchases/payments made from within a mobile application.

Users typically make an in-app purchase in order to access special content or features in an application such as power-ups, restricted levels, virtual money, special characters, boosts, etc.

Application developers are able to provide in-app purchases by sending an SMS to a premium shortcode on behalf of an application user.

To prevent user complaints of being debited without their consent all in-app purchases must conform to below:

  1. Actual games/phones must be submitted for in-house testing.
  2. Developers must provide a means to stop purchases from all or specific MSISDNs.
  3. Purchases must be on-demand and not subscription based.
  4. Associated shortcode and charge must be boldly displayed to the user. E.g. Your purchase of 2000 coins will attract a fee of GHC 0.50 from shortcode 1234
  5. Acceptance and rejection buttons must be visibly displayed together always.
Did this answer your question?