rscherf

7 ms·

31.
by rscherf 7y ago
Correct. Most user come from the e-commerce world and are willing to pay for the convenience of a simple, POS app.
32.
by rscherf 7y ago
That’s exactly right. Terminal solved a problem for me (I used to integrate Mattel card readers to a serious amount of pain). I worked with Stripe to help identify good ones, and they built easy to use APIs to integrate. This is exactly wha
33.
by rscherf 7y ago
Hey, Ryan here. I don’t want to be bought. And in the end if Stripe decides to shut off the source, there are plenty of other things to build. Not to mention, tons of companies to work for. Just fortunate to be in this time and place right
34.
by rscherf 11y ago
I'd be happy to answer any questions if you have them.
35.
Payment for Stripe(paidhq.com)
8 points by rscherf 12y ago|0 comments
36.
by rscherf 13y ago
Yeah, MediaTemple died at the most inappropriate time (again).
37.
by rscherf 13y ago
If I manipulated HN, I wouldn't know how I did it. Just luck of the draw I suppose, although there was much more traffic related to Paid today than there was last night. I don't know who the person is that submitted this. Why?
38.
by rscherf 13y ago
Yeah, a bug was exposed. We fixed it and submitted the fix to the AppStore today. The Stripe API is tricky, so we have to do some looping to get the data.
39.
by rscherf 13y ago
I think they're working on rolling out the platform to many more countries -- just haven't gotten there yet.
40.
by rscherf 13y ago
The monthly volume issue is a known bug -- something we missed while developing. We've submitted a 1.1 fix to the AppStore today that should resolve that. As for the transfer, we gather that right from Stripe's API. Could just be some misla
41.
by rscherf 13y ago
Just wanted to let everyone know that we submitted a 1.1 today, which includes better crash reporting and some adjustments to the way we aggregate your daily/monthly volumes.
42.
by rscherf 13y ago
Well I really appreciate you saying that. Lucky for you, you're getting a good deal! Who knows, maybe they'll be more features or something you can buy in-app in the future. Like the Forecasting stuff talked about below. I mean, you are wel
43.
by rscherf 13y ago
We'll take a look at this. We're about to push out a 1.1 with better crash reporting so we can look at this stuff. As for the OAuth with Stripe -- it's a little slow and hokey, so our arms are tied there. Glad to hear you got in though.
44.
by rscherf 13y ago
Well, it says both. You can manage your Stripe account, and btw, it's beautiful.
45.
by rscherf 13y ago
iOS as a first step, once it's solid, Wess and I may tackle an Android app as well. Who knows.
46.
by rscherf 13y ago
This is actually an awesome idea -- almost like a forecast of the money you'll earn? Should be simple to do it programmatically. I'm going to add something to our feature list to explore this.
47.
by rscherf 13y ago
Really sorry about that! Can you email wcope(at)me(dot)com with any crash reports/comments that you have? We'll take a look.
48.
by rscherf 13y ago
Thanks @billycoover. When I ran my business, I opted to use the web interface provided by Stripe instead of downloading PayPad. It just didn't do it for me, so we created the app we wanted to use. Not a whole lot more to it.
49.
by rscherf 13y ago
Functionality may not be all that different, but the design is certainly different as it's focused on user experience, and not just transactional events.
50.
Paid, an iOS app built on the Stripe API(paidhq.com)
3 points by rscherf 13y ago|5 comments