Slovenia Subscriptions

Slovenia Subscriptions

The information provided in this document is intended for developers to integrate the subscription and charging of your customers in Slovenia. If you have not already done so, please contact the business development team before attempting to follow this guide; business@messagecloud.com or +44 (0)330 1130 243, option 2.

Prerequisites

In order to start charging your customer in Slovenia, you should provide us with the following information:

  • Service keyword — a keyword for your customers to use to confirm their intent to opt into your service (Telemach only).
  • Service description — a short description of the service that will appear on the bill of the customer.
  • Subscription / One-time payment — if your service is a subscription service or only requires a one-time payment.
  • (Subscription only) Subscription interval — how often you will charge the customer.
  • (Optional) HTTP receiver — a URL to which we will send MOs and DLRs. If you are already using Gateway in other countries then you may have supplied us with this already.

Flow of Messages

There are three main networks in Slovenia, each having a different flow you will need to integrate in order to take advantage of subscription billing.

A1 Slovenija

  1. The customer chooses to subscribe to a service by entering their MSISDN into the merchant's website.
  2. The merchant sends a billed request to MessageCloud's Gateway API, with a short welcome message that will appear at the beginning of the double-opt-in SMS.
  3. MessageCloud sends the welcome message to the customer requesting confirmation of their opt-in by allowing them to reply with DA to the message.
  4. If the customer replies with DA, MessageCloud will forward a SUBSCRIBED delivery report onto your HTTP receiver (see Receiving a Delivery Report for more information).
  5. Upon receipt of this confirmation, the subscription can be considered active and subsequent billing requests can be sent using Gateway according to the advertised schedule. Subsequent requests will not require the double-opt-in.
  6. The customer could also reply to the double-opt-in with NE, meaning that they reject the subscription and should not be added to your subscriber list. This will be delivered to your HTTP receiver in the form of a FAILED delivery report.
  7. When the customer stops the subscription, a stop request will be sent to your HTTP receiver.

Telekom & Telemach Slovenije

  1. The customer chooses to subscribe to a service by entering their MSISDN into the merchant's website.
  2. At this point, you must obtain confirmation from the customer about their intention to subscribe. This can be achieved by sending a free message through Gateway requesting that the customer replies with DA.
  3. If the customer replies with DA, MessageCloud will forward this MO onto your HTTP receiver.
  4. Upon receipt of this confirmation, the subscription can be considered active and subsequent billing requests can be sent using Gateway according to the advertised schedule. Subsequent requests will not require the double-opt-in.
  5. The customer could also reply to the double-opt-in with NE, meaning that they reject the subscription and should not be added to your subscriber list. Like with the DA confirmation message, this will be delivered to your HTTP receiver. 
  6. When the customer stops the subscription, a stop request will be sent to your HTTP receiver. 

Technical Implementation of A1 Slovenija

There are a couple of important technical considerations to implement when working with A1. 

Similar to other markets we support, such as South Africa, it is a requirement to store the message_id of the confirmation message for subscription services. This message_id should then be prepended to the id parameter of any subsequent Gateway calls, separated from your own ID with a pipe symbol (|). For example, when you receive a confirmation delivery report from us, the HTTP notification will contain a message_id parameter with a value similar to 1234567890. When you want to charge the customer for their subscription, your POST to the Gateway API should contain the id parameter with the value 1234567890|a67d4ef652ccd78, where 1234567890 was the original message_id and a67d4ef652ccd78 is your own unique identification for the message.

Also, you cannot set your own ID for the initial opt-in message; doing so would overwrite the subscription ID you need to store in the SUBSCRIBED delivery report.

Below is a flow diagram showing how the opt-in process works.

A1 Slovenija Example

The following HTTP requests could be made to achieve the A1 flow.

1. Send a welcome message. The value of this message will determine how much you intend to charge at each subscription interval. No billing is done until you send your first billing request.

https://client.txtnation.com/gateway.php?reply=0&cc=XXXX&ekey=YYYY&message=Welcome%20to%20my%20test%20service&number=38600000000&value=2.49&currency=eur&network=A13SI

2. Receive a SUBSCRIBED delivery report:

https://your-http-receiver/?action=mp_report&report=SUBSCRIBED&id=1234567890&message_id=1234567890&number=38600000000

3. Send your billing request:

https://client.txtnation.com/gateway.php?reply=0&cc=XXXX&ekey=YYYY&message=Content%20message&number=38600000000&value=2.49&currency=eur&network=A13SI&id=1234567890|yourcallbackidhere

4. Receive your billing delivery report:

https://your-http-receiver/?action=mp_report&report=DELIVERED&id=1234567890|yourcallbackidhere&message_id=1234567890|yourcallbackidhere&number=38600000000

Technical Implementation of Telekom & Telemach

The implementation of Telekom and Telemach does not rely on any specific subscription IDs and can be treated slightly differently from A1 Slovenija.

The following HTTP requests could be made to achieve the Telekom and Telemach flow:

Example

1. Send a free message requesting that the customer replies with DA to confirm their intention to subscribe:

https://client.txtnation.com/gateway.php?reply=0&cc=XXXX&ekey=YYYY&message=Opt-in%20message.%20Please%20reply%20DA%20to%20continue.&number=38600000000&value=0.00&currency=eur&network=TELEKOM3SI

2. Receive a message from the customer with the desired action (DA/NE):

https://your-http-receiver/?action=mpush_ir_message&id=1234567891&message_id=1234567891&number=38600000000&message=da&network=TELEKOM3SI&shortcode=3400

3. Send your billing request:

https://client.txtnation.com/gateway.php?reply=0&cc=XXXX&ekey=YYYY&message=Content%20message&number=38600000000&value=2.49&currency=eur&network=TELEKOM3SI

4. Receive your billing delivery report:

https://your-http-receiver/?action=mp_report&report=DELIVERED&id=1234567891&message_id=1234567891&number=38600000000