This HTML5 document contains 57 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

PrefixNamespace IRI
n4http://ods-qa.openlinksw.com:8896/about/id/https/radar.techcabal.com/t/is-paystack-essentially-a-reseller-of-flutterwaves-excellent-payment-tech/9589/
pwdrhttp://www.w3.org/2007/05/powder-s#
n72016-12-08T11:44:
schemahttp://schema.org/
rdfshttp://www.w3.org/2000/01/rdf-schema#
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n2http://ods-qa.openlinksw.com:8896/proxy-iri/
xsdhhttp://www.w3.org/2001/XMLSchema#
Subject Item
n2:892213f6bc11df4f22192720f2ee18735ef77d72
rdf:type
schema:DiscussionForumPosting
schema:datePublished
n7:11Z
pwdr:describedby
n4:11
schema:author
kananga
schema:position
#24
schema:articleBody
Thanks @iaboyeji for being diplomatic about the matter. Your explanation is very gracious. I didn’t realise radar was a paystack circle jerk. The amount of hostility directed towards me for stating plain facts is staggering, but that’s alright, I probably deserve some of it for the choice of words I used in my initial statement (By which I still stand). This is an article from Techcabal that basically corroborates my statement - http://techcabal.com/2016/08/15/flutterwave-iyin-compete-paystack/ For one, all these companies (especially Paystack and Pay With Capture) have been operating for a while. Has Flutterwave been servicing these clients since? If so, who was running the firm before Iyin’s announcement? Delaware public records do not show the owners of the company, and Flutterwave hasn’t answered our question concerning this directly. But more importantly, how long before Flutterwave starts to offer startups the same services as Paystack? While both teams are coy about this, it seems illogical to assume that Flutterwave would continue to allow a middle man sit between them and the companies that ultimately use their services. Once the infrastructure is built, what stops them from allowing anyone stick a payment interface in their web or mobile app? Finally, how do comapnies like Paystack distinguish themselves from other payment providers when anyone can connect to Flutterwave’s API and launch their own payment service? Is there room for more than one payment processor in this market? I noticed that there is a lot of “tip toeing” around the issue, I wonder why that is. People don’t want to hurt other people’s feelings? Whenever there is a lot obfuscation, the simplest explanation is usually the correct one. Anyone with a discerning brain, or inside knowledge of the matter knows I am correct.
schema:interactionCount
UserComments:2 UserLikes:0
schema:headline
Is Paystack essentially a reseller of Flutterwave's excellent payment tech?
Subject Item
n2:dcb2cf5abb5a554b6de66eda2571491d21838e69
rdf:type
rdf:Statement
rdfs:label
Embedded HTML5 Microdata Statement 111
pwdr:describedby
n4:11
rdf:object
Thanks @iaboyeji for being diplomatic about the matter. Your explanation is very gracious. I didn’t realise radar was a paystack circle jerk. The amount of hostility directed towards me for stating plain facts is staggering, but that’s alright, I probably deserve some of it for the choice of words I used in my initial statement (By which I still stand). This is an article from Techcabal that basically corroborates my statement - http://techcabal.com/2016/08/15/flutterwave-iyin-compete-paystack/ For one, all these companies (especially Paystack and Pay With Capture) have been operating for a while. Has Flutterwave been servicing these clients since? If so, who was running the firm before Iyin’s announcement? Delaware public records do not show the owners of the company, and Flutterwave hasn’t answered our question concerning this directly. But more importantly, how long before Flutterwave starts to offer startups the same services as Paystack? While both teams are coy about this, it seems illogical to assume that Flutterwave would continue to allow a middle man sit between them and the companies that ultimately use their services. Once the infrastructure is built, what stops them from allowing anyone stick a payment interface in their web or mobile app? Finally, how do comapnies like Paystack distinguish themselves from other payment providers when anyone can connect to Flutterwave’s API and launch their own payment service? Is there room for more than one payment processor in this market? I noticed that there is a lot of “tip toeing” around the issue, I wonder why that is. People don’t want to hurt other people’s feelings? Whenever there is a lot obfuscation, the simplest explanation is usually the correct one. Anyone with a discerning brain, or inside knowledge of the matter knows I am correct.
rdf:predicate
schema:articleBody
rdf:subject
n2:892213f6bc11df4f22192720f2ee18735ef77d72
Subject Item
n2:be2f621273464936018292690bd52f0d3d75e545
rdf:type
rdf:Statement
rdfs:label
Embedded HTML5 Microdata Statement 112
pwdr:describedby
n4:11
rdf:object
kananga
rdf:predicate
schema:author
rdf:subject
n2:892213f6bc11df4f22192720f2ee18735ef77d72
Subject Item
n2:17e11a87bd62c6feaa0842f871f7f69bb1fbfba0
rdf:type
rdf:Statement
rdfs:label
Embedded HTML5 Microdata Statement 113
pwdr:describedby
n4:11
rdf:object
n7:11Z
rdf:predicate
schema:datePublished
rdf:subject
n2:892213f6bc11df4f22192720f2ee18735ef77d72
Subject Item
n2:72f7a55cf1312545a3a961a66884db1195dee342
rdf:type
rdf:Statement
rdfs:label
Embedded HTML5 Microdata Statement 114
pwdr:describedby
n4:11
rdf:object
Is Paystack essentially a reseller of Flutterwave's excellent payment tech?
rdf:predicate
schema:headline
rdf:subject
n2:892213f6bc11df4f22192720f2ee18735ef77d72
Subject Item
n2:9f1fdb70420f8499ec6c678559dc678212bb3e2a
rdf:type
rdf:Statement
rdfs:label
Embedded HTML5 Microdata Statement 115
pwdr:describedby
n4:11
rdf:object
UserComments:2
rdf:predicate
schema:interactionCount
rdf:subject
n2:892213f6bc11df4f22192720f2ee18735ef77d72
Subject Item
n2:85caaea841e7eb6d4d35f317bd6bdbbd9482ec0e
rdf:type
rdf:Statement
rdfs:label
Embedded HTML5 Microdata Statement 116
pwdr:describedby
n4:11
rdf:object
UserLikes:0
rdf:predicate
schema:interactionCount
rdf:subject
n2:892213f6bc11df4f22192720f2ee18735ef77d72
Subject Item
n2:204a37034035d79b59cb1a7a7e4278e24a0fe7c3
rdf:type
rdf:Statement
rdfs:label
Embedded HTML5 Microdata Statement 117
pwdr:describedby
n4:11
rdf:object
#24
rdf:predicate
schema:position
rdf:subject
n2:892213f6bc11df4f22192720f2ee18735ef77d72
Subject Item
n2:f07f9a83cc77ae9c71700949ebea79f08944f4bf
rdf:type
rdf:Statement
rdfs:label
Embedded HTML5 Microdata Statement 118
pwdr:describedby
n4:11
rdf:object
schema:DiscussionForumPosting
rdf:predicate
rdf:type
rdf:subject
n2:892213f6bc11df4f22192720f2ee18735ef77d72