Skip to the content
IPification - Mobile authentication solutions
Menu
Menu
Have a Question?
Search
04. IPification for Merchant
01. How fast merchants can integrate IPification solutions?
02. What type of Native apps are supported by IPification?
03. What is the pricing for using IPification?
04. *Merchant dashboard status & roadmap as the merchants will definitely enquire about the same once we start onboarding them
05. *Once we finalize with a merchant and we are ready to launch, what all information we need to provide to the product team , so that they can be charged for every successful authentication. i.e. price point agreed, use case agreed etc. is there any form we have designed which we need to fill up & share with the product team prior to launching the merchant?
06. *Once a merchant is launched can we track the revenues & daily/weekly/monthly authentications? Also if a merchant is pre-buying a certain number of authentications, when do we notify them that their authentications are about to expire & they need to top up?
07. *Aggregator account: I am engaged with a number of aggregators, who would onboard client's for us, so any client being launched via a particular aggregator, would have some kind of identifier attached to it so that we know that the particular client has been launched by a particular aggregator & we need to bill that particular aggregator? I have a few other aggregator related queries which I will discuss during the call. one is more to do with Zoho & other about an arrangement where an aggregator initially works as an agent till the time their platform is able to support our API integration & then move to the aggregator model. how would the billing happen in this case?
08. What does the “Service Provider” require to join the IPification service?
09. What parameters do you require from us to be able to get the hash of the three static values (MSISDN, IMEI, and IMISI)? We need this information with respect to our user journey
10. What parameter they will require to validate the hash? In case a fraudster swapped a SIM, what is in place to get the actual hash from the authentication after the actual user regains the SIM.
11. From your experience, how do we get to the real customer in case of an identified swapped SIM.
12. *What are the cost benefits for validation agents (banks, card administrators, retail)?
In this regard, if the operation of these retailers that operate together with all their platforms in different countries and are carried out simultaneously, the transactions that are validated distributed in each country and centralized in Chile, the total of IPification transactions will be registered in Chile or in each country?
You are here:
Main
04. IPification for Merchant
Category - 04. IPification for Merchant
Articles
01. How fast merchants can integrate IPification solutions?
02. What type of Native apps are supported by IPification?
03. What is the pricing for using IPification?
04. *Merchant dashboard status & roadmap as the merchants will definitely enquire about the same once we start onboarding them
05. *Once we finalize with a merchant and we are ready to launch, what all information we need to provide to the product team , so that they can be charged for every successful authentication. i.e. price point agreed, use case agreed etc. is there any form we have designed which we need to fill up & share with the product team prior to launching the merchant?
06. *Once a merchant is launched can we track the revenues & daily/weekly/monthly authentications? Also if a merchant is pre-buying a certain number of authentications, when do we notify them that their authentications are about to expire & they need to top up?
07. *Aggregator account: I am engaged with a number of aggregators, who would onboard client's for us, so any client being launched via a particular aggregator, would have some kind of identifier attached to it so that we know that the particular client has been launched by a particular aggregator & we need to bill that particular aggregator? I have a few other aggregator related queries which I will discuss during the call. one is more to do with Zoho & other about an arrangement where an aggregator initially works as an agent till the time their platform is able to support our API integration & then move to the aggregator model. how would the billing happen in this case?
08. What does the “Service Provider” require to join the IPification service?
09. What parameters do you require from us to be able to get the hash of the three static values (MSISDN, IMEI, and IMISI)? We need this information with respect to our user journey
10. What parameter they will require to validate the hash? In case a fraudster swapped a SIM, what is in place to get the actual hash from the authentication after the actual user regains the SIM.
11. From your experience, how do we get to the real customer in case of an identified swapped SIM.
12. *What are the cost benefits for validation agents (banks, card administrators, retail)?
In this regard, if the operation of these retailers that operate together with all their platforms in different countries and are carried out simultaneously, the transactions that are validated distributed in each country and centralized in Chile, the total of IPification transactions will be registered in Chile or in each country?
+ 5 Articles
Show all articles
IPification - Mobile authentication solutionsIPification - Mobile authentication solutions