2,440 karma · joined December 3, 2009
We open-sourced Pi0 (referenced in this post): https://github.com/Physical-Intelligence/openpi
Happy to answer any questions on the model, hardware, etc
this product has always been about AI—what they launched is almost exactly what they pitched me. their expectation of where the world going ended up being prescient.
this is probably the most privacy-forward hardware device on the market—you have to physically be making contact with the device for it to begin listening (at which point an LED is prominently visible) and it will stop listening as soon as you break contact.
(That said, given many of these businesses may be on Stripe, we should have more ability to work with them to improve the experience for customers...)
The technology we've built is agnostic to debit or credit -- it really depends on your use case. That said, force posts (or transactions cleared without an underlying authorization) can happen on any card type.
For what it's worth, we have an API to initiate disputes (which you would be able to on a transaction initiated without a valid authorization) which you could use to recoup funds.
We've been primarily focused to date on companies where issuing cards is core to providing their business to customers, for example a startup that provides expensing customers, or a platform that needs to purchase goods in the real world. We're less focused on a business just using it for their own expensing (as we don't have receipt upload functionality, etc).
To your two other questions though:
(1) Could users approve things in real time? Sort of. We provide the ability (as you noticed) through API, but it needs to be responded to in < 2s, which means it's not possible for a human to be in the flow.
(2) Could this be linked to an external bank account? Again, sort of. To get in the weeds: as soon as we approve an authorization, we're on the hook for those funds. A debit to an external balance (or bank account) may fail and Stripe would be on the line. This is why we typically require funds to be in a Stripe account prior to purchases taking place.
Not really. We make it easy for institutions like Monzo to issue and manage cards, but I imagine that's just a fraction of what they've needed to build to run a regulated bank, service their customers, etc etc.
Cards draw from a Stripe balance (which is funded by payments that go through Stripe (or top-ups).)
The cards draw from a Stripe balance, which can be funded from a connected bank account (or ordinary Stripe charges).
Glad to hear on the developer friendliness! If there are ways we can continue to improve on that front, please shoot me a note: lachy@stripe.com
I'm curious though what you mean when you say Adyen is much more "bare metal" than Stripe. We don't typically talk too much publicly about our underlying infrastructure (our goal is to abstract away that [hopefully] unnecessary complexity), but we do strive to be as close to the bare metal as possible. (We're directly connected to all of the major card brands, and have "acquiring licenses" in numerous markets.)