In this manual we want to help you to make sure your PSMS API service is compliant in all markets you have chosen. To make it as easy as possible we have prepared a step by step guide with general requirements every service should respect in all of the countries we support. In some countries there are additional requirements which you will find in the tables under the steps below. By following these 6 simple steps you will make sure your service is compliant and simplify the launch approval process with the operators. All of the information can also be found in the Country Regulations document.
Unfortunately you cannot use Fortumo if your service is related to:
Next make sure your service also respects country specific content restrictions.
Please keep in mind that in the Middle Eastern and North African region the carriers do not allow social casino games (even virtual poker games are categorized as gambling), bingo, tarot, horoscope, VPN services and religion related services. There are also very strict regulations towards dating and chatting services – make sure to avoid any nudity in your service (already slight revealing is considered as inappropriate).
Here are some of the examples that we have prepared for you:
Payment flow for Web services
Payment flow for In-App services
Manually managing payment windows to be compliant and include everything required in every country we support will be very time-consuming for you. To assist you with this, we’ve developed a service data export XML API which allows you to automate service configuration and payment window management across countries. This API will list supported operators, keywords, shortcodes, prices and local disclaimers for every country you’ve configured. We strongly encourage you to implement this API in your project. You can read more about our XML API in the technical specification.
It is mandatory for every reply message to include:
Below are 2 examples of a compliant reply message:
There is maximum 120-symbol message length limit which you should not exceed (50 symbols for replies in Unicode).
We have made it easy for you by gathering localised reply message formats, payment page disclaimers and currency formats into one Country Regulations document. Feel free to use these examples and modify them according to your service to make more revenue by improving the payment experience.
Brazil example for web services
Brazil example for In-App services
Once you have followed all steps above, prepared a compliant payment window and are ready to launch the service, please hit the Go Live button on Dashboard under Services tab. You will see a list of countries that need carrier additional approval before they can be activated.
To help our Approvals team to get your service live as quickly as possible, please carefully fill the form and kindly send us following information:
In United Kingdom and Ireland local regulators require every service provider to register before operating any mobile payment services. We’ve prepared additional step-by-step guidelines to assist you with the process:
Once done, kindly send us the registration numbers (PPP registration number for UK and Comreg PRS licence for Ireland) to email@example.com.
How long will it take to get you service approved?
Once you have submitted the service materials to approval, our team will get back to you within two business days. However there are stricter markets, where carriers are performing thorough checks resulting in approvals that might take up to several weeks. For example in MENA, Ireland, United Kingdom, South-Korea and Canada.
We hope that this guide was helpful in preparing a compliant service. In case there is something that remained unclear please contact us at firstname.lastname@example.org.