How many man-hours did it take to build this app? Does releasing it as an Stripe app instead of hosting it on your own website(using Stripe Connect) reduced technical implementations such as authentication/authorization?
Ripe for failed founders to exploit
My business uses Payment links and a customer asked to cancel their subscription. Of course I canceled it but I stopped to think what would happen if I was hit by a bus. Is there no other option but a chargeback if a subscription does not have a cancel option?
I'm a bit ashamed to say, but I'm having trouble with checking if the customer has a valid subscription. I'm currently only storing the customer_id in the database and retrieving the information from Stripe to have it as a single source of truth and avoiding putting the Stripe info in our database and having to make sure it's synced.
On the other hand, I can't make a request to Stripe with every request, so I'm thinking of memoization or something.
I could find guides on how to accept payments and create subscriptions which are trivial, but no examples on what happens after that.
Suppose I have an API with a single endpoint and set up a subscription for a customer, how do I not hit the Stripe API with every request to check if the subscription is still alive without storing customer info in my database and having to sync it (i.e: keep everything in Stripe)?
At one point I asked the customer rep if there was any way to rid myself of this nuisance other than completely closing my account. She responded with the normal "that's your decision, blah, blah, blah...", but I was legitimately asking, not threatening.
I think I said something like: "No, let me be clear: I don't want to close the account. I just don't want to deal with this every six months either. I'm seriously asking if this is the only other recourse because it seems we've tried everything else."
It did get resolved eventually. It was also for a trivial amount so nothing like what you're looking at. It was still very annoying though.
App marketplaces are great all around. Great for users - more functionality. Great for partners - easy access to distribution/users. Great for the marketplace owner - improve your product, while adding network effects that deepen your moat against competitors.
Some of these may be very stable but this is always on the back of my mind: “Is this going to work in 5 years?”
If you ever want to witness horror, jump over to Shopify forums: Zapier integrations gone wrong, unresponsive APIs, App owners not responding, businesses adding free integration apps that were last updated during the Obama administration, etc.
While Stripe API and their core services are stable, none of this inspires confidence.
Easy way to create a recurring subscription based on a one-off price, currency and product description (just so this is still recognised as recurring revenue).
Recurring subscriptions that automatically pause and remind me 30/60 days before renewal so I can reach out to the customer and get a new purchase order.
Customer templates - Many customers purchase through resellers, so having templates for different resellers would accelerate the process to add new customers with the same bill-to but different ship-to.
Dashboard with upcoming renewals for annual subscriptions.
Saved export settings (columns) for payouts, so I can export these each month for my accountant.
Yes, you can do all of those through the API, and I'm sure Stripe will tackle these sooner rather than later, still, just to give you an idea.To continue, please accept Stripe Apps terms and conditions for your account. Press Enter to open the browser or visit https://dashboard.stripe.com/apps/accept-terms (^C to quit)
Waiting for confirmation...
After waiting for a few minutes, it terminates with this:
please accept Stripe Apps terms and conditions before proceeding
I've already accepted the terms.
You can follow that issue for updates (hopefully shortly!) and if you have additional details to add, adding them there will get them to the team directly.
Thanks again and sorry for the launch day bumps :)
What's interesting is strip invoicing is pretty uncompetitive here.
Fee for sending one invoice is $100/invoice. For every 100 invoices you are spending $10,000.
OUCH!!!
In other words, if someone was allowed to do an invoicing app in this marketplace it might do ok for a group out there. A target would be folks doing ACH payments (you need to cap per invoice including payment fees at $10 to be competitive here I think).
EDIT: Sorry, corrected to be $100/invoice from $500/invoice which is still much higher than we see elsewhere to send out an invoice.
There is an additional payments fee that applies.
"Transparent and consistent pricing You must clearly state your app pricing up front, without hidden costs or fees. App pricing must also be consistent with off-marketplace prices."
https://stripe.com/docs/stripe-apps/review-requirements#app-...
Though I suppose Stripe is watching for apps doing things Stripe should/could do itself as a real-time "what would people pay extra for?" list.
ex) Docusign is down by at least 80%
1. Stripe is a private company, it hasn't IPO'd.
2. YC was an early investor in Stripe, but as a late stage company, Stripe has many, many stakeholders that are investors: https://www.crunchbase.com/organization/stripe/company_finan... to think that they're beholden to YC and would make business decisions for the sake of YC companies -- oof.
But I'm sure you been paying attention to the markets....