billycoover

Joined 15 years ago

Karma

Submissions

Member since

Jan 3

Recent submissions

I had the same question "What's this even about?" but I decided to read the article and magically my question was answered.

Comment · 12 years ago

I never heard of this until just now and this is my good friend that wrote the post.

It reminds me of Halo from the show Continuum. The early alpha version before it gets deeply integrated into your physical being.

Fast-forward 10 years and we'll be wearing these things, only they'll be called iBod and it will be a combination iWatch and iGlasses and freakishly integrated in our lives.

Ready Player One!

Comment · 13 years ago

Congrats on the launch!

Comment · 13 years ago

It looks great @rscherf. Happy to see some competition for Pay Pad!

Comment · 13 years ago

I've got 99 problems but too many push notifications telling me I made money, ain't one. :)

I have a couple things in the works that can help reduce the number of push notifications you get. For example, for my account, I'm only getting notifications for charges over $100.

Ping me ([email protected]) and do some wizardry behind the scenes for you if filtering on the dollar amount would help you out.

Comment · 13 years ago

1) No it's not open-source but I do plan on opening up the Stripe lib I've built. 2) Negative. That would be a great option but some Pay Pad users want the full featured access, including accepting payments from the device.

I think about this a lot... For example, from Pay Pay, what would be the ramifications if someone stole your phone and had access to your Stripe account?

Well there are three things that are pretty scary. They could 1) add new charges to your existing customers 2) refund existing customers, and 3) get names and email addresses of your customers.

Could you prevent this? Yes. Password protect your phone. If it does get stolen, go to Stripe and revoke access to the third party apps.

But I want to do better. One user left a review the other day and asked for the ability to "lock" the app. I haven't decided yet how I'll implement it but I do want to add an "optional" locking feature that adds yet another layer of protection to your Stripe account from the Pay Pad app.

Ping me if you have any thoughts on alternatives.

Comment · 14 years ago

Fixed. Thanks for pointing that out!

Comment · 14 years ago

Parse is cool, but the pricing is a deal breaker for me. According to their plans page (https://www.parse.com/plans), I'd need a pro account to enable multi-app push. Pay Pad is three apps actually so the combination of UrbanAirship and Webscript.io end up being a very cheap solution if I wanted to ditch my current implementation on Heroku.

Although I suppose you could get around the multi-push-certificate restriction with multiple Parse accounts. If you had two iOS apps, then you'd be making two web requests out to Parse. Although I do this now with UrbanAirship so there would not really be a difference. Interesting.

Comment · 14 years ago

Thanks for the feedback. The app has since been approved. Blog post updated with details: http://coovtech.com/posts/the-apple-reaper/

Comment · 14 years ago

I confirmed with Apple this morning that this is not the case. Update the blog post: http://coovtech.com/posts/the-apple-reaper/

Comment · 14 years ago

Update: Apple reached out to me about this incident. They've approved the app! http://itunes.apple.com/us/app/pay-pad-for-stripe-for-iphone...

I'll update the blog post in the morning with details.

Comment · 14 years ago

Here's what I wrote in my appeal. I tried to speak in the most simple terms as possible. I hope it works:

" The rejection states that "if the purchasable content, functionality, or services are intended to be used within the app, they must be purchased through IAP, within the app" - This is absolutely not the case. Pay Pad for Stripe allows USERS to accept payments from their customers with their iPhone & iPad. Nothing that the user is accepting payments for would be used within the app.

Pay Pad for Stripe is companion app to the Stripe API (http://www.stripe.com).

I am not selling anything inside of the app. There are no subscriptions inside of the app. There is no exchange of a fee or subscription money between myself and a Pay Pad for Stripe user. They cannot buy any content, products, or services from my while inside the app.

The most straight-forward way I can describe how someone might use Pay Pad for Stripe is this: My wife has a Stripe account which allows her to accept credit card payments. She downloads Pay Pad for Stripe so that she can manage her Stripe account and accept mobile payments. She takes our daughters to the local grocery store to sell girl-scout cookies. A customer of hers want's to buy a box of thin-mints. She uses Pay Pad for Stripe to take a credit card payment from the customer for those thin-min cookies.

That's it. The feature is identical to what you will find in the popular Square and Pay Pal apps. This is not in-app purchasing. This in enabling B2C business transactions. There is no money exchanged between myself and the Pay Pad for Stripe users. "

Comment · 14 years ago

That's what he's telling me.

Comment · 14 years ago

Lots fo suggestions for this one :)