Work stages Project analysis Development tasks Technical documentation Work plan and time frames Coordination with lawyers and operator’s security service.
Discussion of the process and software
Architecture, for example, how the system will charge off money, identify the user, etc. Draw up documentation with a detail description of system operation Coordination with lawyers and security service of operators Engineering and development Payment acceptance system development SDK implementation for developers Integration with operators’ billing systems.
A precise mobile phone number database accurate mobile phone number list is essential for business success since it facilitates better communication, increases client outreach, and increases the efficacy of marketing campaigns. Businesses may interact with specific audiences, boost conversion rates, and cut down on resource waste by providing accurate contact information. In addition, it guarantees adherence to rules and regulations, building confidence and enduring connections with clients.
Testing and fixing bugs Functional testing Load testing System testing in conjunction with a mobile carrier Fixing bugs Commercial launch with operators Analysis and coordination with lawyers and security service Before starting the development, our team discuss the technical and legal aspects of the project with AppClick and operators.
We immiately agre on key issues
For example, how we would: Charge off money identify users confirm consent to purchase As a result of the discussion, a document was drawn up with a description of the set of functions, financial and legal scheme, and architecture of the system.
This document was once again finaliz with the customer, lawyers, and the operator’s security service, and the finish document was hand over to the customer and their partners. The screenshot of the document that we have prepar for mobile operators. It contains description of the functionality, financial-legal scheme and system architecture. Planning and development.
To prevent AppClick from wasting resources on administrative work, we discuss technical issues with the operator directly. To begin with, we chose the software and discuss with the operator options for the tariff scale: a one-time purchase or a subscription.
We then began development
As part of the development process, we strategies and tips to improve did the following: research the experience of other SDKs for payment and develop templates for integration on their basis wrote a set of libraries for developers, a control panel, and a module for working with operator’s billing made three parts for the management model: for an app developer, for a mobile operator, and for a call center (in case of conflict situations) compil a single version of the system for mobile developers made a brand subdomain for the operator.
Testing Before launching the system, we double check if it work correctly on the side of the customer and operators, and made sure that the user would not encounter bugs. For this, we conduct functional and load testing.
Then, together with the operator, we seo ebl test each link separately, and then the entire system. As a result, we found errors, but eliminat them before launch. Among the errors were the following: the payment went through, but the money was not debit in the billing the data was not includ in the statistics the user subscrib, but the subscription did not work the user did not receive a payment confirmation Production After successful tests, we launch the system and track the results.
There were no failures
To better understand how the system works, we show algorithms and service scenarios. Work algorithm Request from the user’s mobile phone to us A request from us to our own server from the operator’s system Interaction of the server with the operator’s billing to charge off money from a subscriber Work algorithm of the whole system A developer publishes an app with the integrat.
AppClick, together with the operator, identifies users and accepts their payments The mobile operator, together with AppClick, informs all participants about the actual charge-offs Service script A user launches an app Selects a paid option Presses «Pay» AppClick.
SDK creates a landing page with a
Payment form User pays If the payment goes through The landing page with the payment form closes The user automatically returns to the home screen If the payment fails AppClick SDK creates a landing page with a notification The user is automatically switch to this page On the landing page there is a confirmation that the payment did not go through, and a list of possible reasons Results: we agre on technical and legal details with operators and launch the system to monetize customer services It took 18 months to negotiate, create, and agree on technical documentation and to develop the system. The system launch in the second quarter of 2016.
Development was not difficult
We had already had a similar experience. The main difficulty was to fulfill the technical and legal conditions of the operators so as not to disrupt the terms of the entire project: Each stage had to be coordinat with several departments at once. To meet the deadlines, we involv a product manager: this way the developers were not distract and the tasks were not stall. In order to gain access to the servers, part of our team was hir as part-time operators.
There were many such conditions
And they took time. We understood that this was part of working with big business, so we simply put more hours into the project and found specialists with experience in working with corporations. Results of the work of the system for December 2019 — January 2020 156,700 100 rubles.
MTS and Beeline users paid for services and options through the AppClick system average payment Technical block of the project PHP 5.6 CodeIgniter PHP Framework Zend — PHP Framework / library Ris Memcache Cassandra WURFL — Mobile Device Database How can we help? Artificial intelligence technology.
