yashmaistry

I completely agree.

Our demand for meat has increased so much it is inevitable that the market is going to resort to breeding animals faster with less care to supply the demand.

By cutting down we can have a positive impact

I see where you are coming from As it stands, it only solves a niche problem.

We want to help new startups, who are both looking to get their MVP build faster and are looking for no code/ low code options.

It will take time to build out a product for the larger community but for now we are looking to small a problem.

Thanks for your feedback

Your product looks good!

Using Stripe Connect is something we are going to add.

Stripe Connect & OAuth was something we thought about. It's definitely recognised as a more secure method and it's also low friction to integrate. The only drawback comes into play with marketplace and platform apps. The platform itself may already be using OAuth with their customer.

We could offer our customers both options and let them choose which one is best.

Stripe Connect & OAuth was something we thought about. It's definitely recognised as a more secure method and it's also low friction to integrate.

The only drawback comes into play with marketplace and platform apps. The platform itself may already be using OAuth with their customer.

We could offer our customers both options and let them choose which one is best.

Yeah, in essence it helps start ups integrate stripe without building their own backend

Startups would put in their restricted key - a secret key with only the access that is necessary.

In terms of pricing, a request is an api call. I can see your point with $5 to send 250 text messages. It does sound steep. The first 5000 requests are at $20 which should adequate for most startups. Majority of our customers don't use more than 750 right now.

If we find customers maxing out the limits too quickly we will definitely adjust our pricing

That's true, it doesn't make it obvious.

We handle security in a few ways;

- Clients are initialised with Key & ID - We advocate for keys to not be hardcoded

- The key is used for request encryption and are never sent to the server. Request hashes are also used to make sure Man In the Middle Attacks are avoided

- Custom Auth Tokens can be sent with requests - On the server side we use your provided auth callback to ensure it is valid

What do you think about the steps we take? Tokens are really important because they offer another layer of protection