I created this thread to address a misconception about Paystack being peddled on a different thread. I addressed this but it appears more light is still needed, based on the questions still being asked by our dear friend, @kananga
Basically, it started with this.
To which I responded and said the following.
I speak as CTO of Paystack and I can assure you there is no evidence of this in our codebase. There is no evidence of same in either Uber’s or KongaPay’s codebase either.
Uber processes transactions directly through the MasterCard Internet Gateway Service with Access Bank as the acquiring bank.
KongaPay is a whole different ball game altogether, working with multiple banks and NIBSS to enable them directly debit bank accounts. You can confirm this with any developer on the KongaPay team. It is worthy of note that as at when the product launched, Flutterwave was not a thing.
That said, Paystack started off as Uber is - processing transactions via MiGS with Access Bank as our acquiring bank. It was why we could authorize and charge cards without requiring PINs or One Time Passwords. It was also the reason we could not process Verve cards at launch because those are local to Nigeria. Today, we work with multiple banks as acquirers, primarily GTB and Zenith, and directly with Interswitch to support PIN/Token authentication for MasterCard and Verve cards. For cards that have already been authorized once, we simply pass them off to MiGS for subsequent charges (recurring billing, or when a charge is sent to an existing customer’s card).
We also have relationships in place with eTranzact and NIBSS to make things like direct bank debits and automated transfers possible. As a player in the financial services space, we are also directly regulated by CBN as a Payment Service Provider and I can assure you that hasn’t been a small feat in terms of requirements - 100 million naira in share capital paid for, rate regulation, amongst other things. So no, you cannot just “become a retailer too if you are interested in fintech”.
My colleague, @FatherMerry also jumped in to add that we used Flutterwave for a brief period of time as part of the numerous processors we processed transactions through largely as part of a banking relationship. That is correct. Above, I mentioned that at launch, we worked with Access Bank as our acquiring bank while processing directly through Mastercard. Over time, we built relationships with multiple banks to achieve this and largely with more flexibility.
I cannot say for certain when Flutterwave became a thing, but due to their deep relationship with Access Bank (more on this later), transactions we passed through our Access Bank integration went through Flutterwave, starting late May, 2016. I would love to go into the intricacies of this, but I reckon that isn’t why we are here. Over time, and for multiple reasons, this stopped being the case.
Paystack’s core offering has not changed since we launched, and our mission is to simplify the process of accepting payments online while equipping our customers with the best tools to make that possible. What is not true however, and does disservice to our business (and everyone who has worked to make it into what it is today) is to conclude that we are “powered by” Flutterwave or rely on their tech somehow. I have heard this in so many different variations including that Paystack is a Flutterwave white label - something I immediately took to Twitter to address after hearing it from two people in one night.
https://twitter.com/0x/status/803136031562182657
I understand that there may still be questions asked and I am very happy to answer them here instead.
@kananga Based on the distribution of our transactions, your adamant stance would be better channeled into saying we run on Interswitch technology. At least, that will be closer to the truth.