@Uduak wrote:
My team is about to launch a new payment service and one of the things we have done is bring our blacklist Dbase from our mobile recharge, bulk sms and school applications. Turns out its a lot of data.
So I have created an API to share the data so that other websites taking payments in Nigeria can easily lookup the email or phone number and get a warning. Something like the TMF for websites around here.I don't think its cool for someone to perpetrate fraud on say www.quickairtime.com and then go ahead and do same on www.printivo.com regardless of the difference in business.
Another thing is the issue of Pay on delivery. The e-commerce guys can simply ping and realise that the user device_id/phone_number/email/Card_PAN is associated with five(5) Pay on delivery rejections and decide If its worth the risk.
Also, we are beginning to have a lot more Nigerians calling their banks to dispute payments after receiving services from websites.While I have created open APIs for anyone to reference from our DB, I think we should have a more sustainable approach like a repository.
Three weeks ago, I sent this to my legal guy and the feedback is that it will have to be an API only access repository so you can only crosscheck entries electronically and post to it electronically, PLUS would have to be operated as "CLOSED" as the TMF List.
Technically the following data would be shared across the network;
email - nothing on it.
device id - Now the diamond
phone number - Thanks to sim reg, now traceable
card pan - So if there's a stolen card on the loose, we can all dodge it. Be warned.Please does anybody have a project like this? or am I the only one paranoid about ecommerce fraud detection.
Posts: 4
Participants: 4