|
|
|
|
|
by PragmaticPulp
1511 days ago
|
|
EDIT: The accused person has denied these allegations, claiming that Plaid reached out to Stripe (not the other way around) and that the RFPs were because Stripe invited Plaid to be part of the product: https://pbs.twimg.com/media/FR8FjJ9VsAAMY_k?format=jpg&name=... > Wow! Jay, you took interviews with Plaid & asked probing questions multiple times over the past few years, and your team sent repeated RFP's (under NDA!) to us asking for tons of detailed data. I wish y'all the best with these products, but surprising to see the methods. I don't know. Talking with a company shouldn't disqualify you from ever working on a competing product. Sending an RFP doesn't mean you can never build your own product. The Plaid CEO is trying to anchor the conversation around malicious intent, but it's not hard to imagine a scenario where this product-minded person legitimately explored working with Plaid, legitimately explored partnership opportunities at Stripe, and walked away believing it would be better for Strip and for himself to build a competing solution at Stripe. Plaid's product isn't entirely novel. In my experience as a consumer it has failed at least 3/4 times I've tried to use it with my financial institutions. I'm frankly more surprised that it took this long for anyone to enter their space to compete against Plaid. |
|
1. Obviously this is a product we'd want to build because our customers want it
2. We contacted Plaid to see if they wanted to be part of it
3. Plaids pricing didn't work for us so we built it ourselves / went with other providers
Not sure what you'd even get from talking to the team at Plaid that couldn't be learned in an afternoon or two using product that use Plaid and hacking on banking API's.