re Inventory: we want to provide live product availability information to the developer through our API. We encourage app developers to GET latest product info from our API before even rendering a potential Buy Now button. To make that possible we keep product information extra-fresh from big retailers, and even update it on the fly when we see orders failing because the product is out of stock.
re Payments/Processor: So that's where it gets interesting. We have constructed for Pinterest a full payment distribution infrastructure to send payment information securely to large retailers or their processors. This infrastructure will also be used by Relay. Doing so, we believe we bring a ton of value to the ecosystem. But I'm sure you agree with that given your focus!
Re:Stripe: Relay
by jusben1369 on Monday September 14, 2015 @08:25PM
(#10218303)
Congrats on the big day btw!
In other words, since the app system doesn't have links like browsers, a whole new system is needed to emulate them.
Re:Stripe: Relay
by jusben1369 on Monday September 14, 2015 @08:25PM
(#10218302)
Well they could push out and invoke a browser session which is how it was done initially and is still sometimes done. But yes conversion is poor.
In the mobile world with mobile optimized apps those redirects don't work. So app developers want to make the payment experience feel like it's happening "within the app" Twitter, Facebook, Pinterest and others all then had to solve for the inventory + payments challenge. Defaulting to Stripe can be problematic if the retailer already has a different payment processor relationship in place. By solving for the inventory piece I suspect Stripe is hoping to help drive momentum around overcoming the processor objections.
Full disclosure I work at Spreedly where we help solve for the payment dilemma (not inventory) by allowing developers to work with a wide range of payment processors and/or affiliate API's.