1) There's no branding on the shirt at all. The shirt is shipped from Scalable Press, so I'm not sure what the packaging will say, but I imagine they have something in place for white-labelling.
2) "Passive income" side project, though with all the HN hate it's turning into a bit more scrambling than I'd imagined :).
3) I do ask them questions since I'm a pretty early user of the API, but it's pretty well-documented at this point so I don't imagine you'd run into much trouble developing on it.
While our webhooks are perfect for building things like receipts, we want to make the seller experience for the most common use case as nice as possible.
We do encourage folks to use our webhooks to build receipts for more complex use cases (e.g. if you want to include maps, images, or just in general need a more complex receipt structure for your particular business), but the simplest case is one we can and should provide well for :).
Hi! I work on product at Stripe. We're currently working on better API for managing recipients.
However, I can't seem to reproduce the issue you're seeing--could you provide a bit more context? If you change a recipient's bank account, their past transfers will still appear on their page in your Stripe dashboard and when listing transfers via the API and filtering by recipient ID.
Oh no — I'm very sorry to hear that. We try to avoid giving ETAs for functionality in order to avoid having people get stuck like this. (At the same time, we sometimes do indicate when we plan to do something — which does have this failure mode.) But we should probably have been clearer that it wasn't going to happen imminently — want to drop me a line at [email protected] and I'll see if there's any way we can help?