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

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

PrefixNamespace IRI
n8http://ods-qa.openlinksw.com:8896/about/id/entity/http/www.openlinksw.com/osdb/services/
pwdrhttp://www.w3.org/2007/05/powder-s#
n7http://linkeddata.uriburner.com/about/id/https/radar.techcabal.com/t/is-paystack-essentially-a-reseller-of-flutterwaves-excellent-payment-tech/9589/
n52016-12-08T11:44:
schemahttp://schema.org/
rdfshttp://www.w3.org/2000/01/rdf-schema#
n2http://linkeddata.uriburner.com/proxy-iri/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
xsdhhttp://www.w3.org/2001/XMLSchema#
Subject Item
n2:03ce1ab5d49d82856ee576f6430dfe3f7b6e6a85
rdf:type
rdf:Statement
rdfs:label
Embedded HTML5 Microdata Statement 40
pwdr:describedby
n7:11 n8:tech_cabal_search
rdf:object
kananga
rdf:predicate
schema:author
rdf:subject
n2:232cc1361cf6be6c81e91661d0508697ef258ce8
Subject Item
n2:0674856f5982802191b6d7b665c6f5d5dbc12c39
rdf:type
rdf:Statement
rdfs:label
Embedded HTML5 Microdata Statement 41
pwdr:describedby
n8:tech_cabal_search n7:11
rdf:object
n5:11Z
rdf:predicate
schema:datePublished
rdf:subject
n2:232cc1361cf6be6c81e91661d0508697ef258ce8
Subject Item
n2:232cc1361cf6be6c81e91661d0508697ef258ce8
rdf:type
schema:DiscussionForumPosting
schema:datePublished
n5:11Z
pwdr:describedby
n7:11 n8:tech_cabal_search
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
UserLikes:0 UserComments:2
schema:headline
Is Paystack essentially a reseller of Flutterwave's excellent payment tech?
Subject Item
n2:3783695fae7d1a3de07bfe7b40c1705afdcad081
rdf:type
rdf:Statement
rdfs:label
Embedded HTML5 Microdata Statement 39
pwdr:describedby
n8:tech_cabal_search n7: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:232cc1361cf6be6c81e91661d0508697ef258ce8
Subject Item
n2:444e78f8516362a84fa74ce9ca182bde5b4d4b58
rdf:type
rdf:Statement
rdfs:label
Embedded HTML5 Microdata Statement 42
pwdr:describedby
n7:11 n8:tech_cabal_search
rdf:object
Is Paystack essentially a reseller of Flutterwave's excellent payment tech?
rdf:predicate
schema:headline
rdf:subject
n2:232cc1361cf6be6c81e91661d0508697ef258ce8
Subject Item
n2:4a0828f86d10f037a8bce1516d6f89d09924edce
rdf:type
rdf:Statement
rdfs:label
Embedded HTML5 Microdata Statement 45
pwdr:describedby
n7:11 n8:tech_cabal_search
rdf:object
#24
rdf:predicate
schema:position
rdf:subject
n2:232cc1361cf6be6c81e91661d0508697ef258ce8
Subject Item
n2:974c77428aedb846b92ce9c3ca5495c846ab77e5
rdf:type
rdf:Statement
rdfs:label
Embedded HTML5 Microdata Statement 46
pwdr:describedby
n8:tech_cabal_search n7:11
rdf:object
schema:DiscussionForumPosting
rdf:predicate
rdf:type
rdf:subject
n2:232cc1361cf6be6c81e91661d0508697ef258ce8
Subject Item
n2:983ec1657c3ad757a7ac80ef327210ce6b790bb2
rdf:type
rdf:Statement
rdfs:label
Embedded HTML5 Microdata Statement 43
pwdr:describedby
n8:tech_cabal_search n7:11
rdf:object
UserComments:2
rdf:predicate
schema:interactionCount
rdf:subject
n2:232cc1361cf6be6c81e91661d0508697ef258ce8
Subject Item
n2:a07cda8e62e83bfd4951be57a87178c70a48cdf7
rdf:type
rdf:Statement
rdfs:label
Embedded HTML5 Microdata Statement 44
pwdr:describedby
n8:tech_cabal_search n7:11
rdf:object
UserLikes:0
rdf:predicate
schema:interactionCount
rdf:subject
n2:232cc1361cf6be6c81e91661d0508697ef258ce8