--You received this message because you are subscribed to the Google Groups "HeatSync Labs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to heatsynclabs...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
PayPal works the majority of the time, and everybody seems to have it. But when it fails you, it fails HARD. Here's the answer I found at Hour 8 of implementing PayPal's API for us: https://www.x.com/developers/paypal/forums/nvp/subscription-profiles-not-supported (English: people who use the yellow Pay with PayPal buttons are second class citizens.)
I'd like people to check out http://hslbilling.herokuapp.com/customers however. Do you think Stripe's credit card form is acceptable?
Good points, all. Yes this form would initiate a recurring $50 charge per month, which currently isn't clear. I think I can fix that.
All the data associated with payments would be very accessible; by using the customer ID you see on the main page, everything from transaction history and last 4 of the cc#, to next payment date and balance are available.
I'm not sure if it's possible to make two payments in one day; if you used this form to do so, you'd be signing up for two memberships.
Class fees and donations would be a separate form and thus a separate bucket. The reporting capability is very good.
Good news about losing ~5% of our payers: that's only 2.6 people. There are about 52 active PayPal subscriptions at the moment (not including people who do a manual PayPal payment, etc). I'm not sure what to do about oddballs, but in any case it's the volume of payers that makes this a pain; if we get almost everyone to switch it should still be fine.
Mark: I share your concern, I'm brainstorming ways to encourage switching without encouraging cancellation.
There are CSV downloads but they'd be a kludge and it still requires Chad and usually myself to sit down and enter the data into our systems. I figure if we can automate the "who is a member / how many members do we have" data, then our treasurers can maybe ignore those bits and focus on the raw money of it. (QuickBooks API also seems to be a pain in the butt; we'll see.)
Basically, CSV could turn a 2 hour job into a 30 minute job, but the hard part about HeatSync is usually getting people (including myself) to show up in the first place.
--
You received this message because you are subscribed to a topic in the Google Groups "HeatSync Labs" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/heatsynclabs/134_KA5xEpg/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to heatsynclabs...@googlegroups.com.
> Does it handle a declined charge gracefully? Or will the declined entry look like a successful one? What if they then turn around and use a different card that gets approved?
I'll have to check but the status info is pretty detailed. I'm sure at some point manual intervention may be required but I'll see what I might have to do to handle issues gracefully.
> Hopefully clarifying that this is for recurring payments will take care of most of the issue, but can a test be inserted to see if someone's already at the given membership level and thus avoid the double billing?
This should be handled by ensuring people don't sign up for multiple members.hsl accounts. One account, one billing profile (which you can modify as needed.)
> How does someone change membership levels? If I want to move from $25->50, I'd hope the system would end the old payment and then add the new one. Likewise if I move from $50->25.
In stripe, "customers" have a "plan" which you can switch as desired. I'm sure this is handled gracefully but I'll check. It's nice that I don't have to program this logic myself.
> If we stay with PayPal, could multiple addresses be used to do some bucketing and then parse a CSV further? (not sure if PayPal supports multiple addresses to a single account, or if it would break it out in the CSV differently)
This idea has been brought up; it's not the best option but it's a tool at our disposal. Problem with CSV is, it's just another manual process so it doesn't really solve many problems. It's better to just "know" member payment info and financial info instead of having to spend precious volunteer time doing data entry to figure it out.
--
You received this message because you are subscribed to the Google Groups "HeatSync Labs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to heatsynclabs...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Good insight. The good news is that Stripe is highly-structured data. You pop some lines of code into your website and suddenly the website (or database) automatically knows basically everything about your payments. Stripe even gives you code samples in different languages.
<rant>
I think logging into PayPal weekly is something that will not happen at HeatSync. Recently Chad and Marita have done enough work that we've lately been getting SEMI-MONTHLY REPORTS which is really exciting and I'm sincerely grateful for. I know businesses are run a certain way, but being an all-volunteer co-op is different; how much time could YOU honestly, regularly commit to doing that work for HSL? That answer is usually the same for us volunteers. We've all got busy lives, so we fit in volunteer time where we can. I'm actually amazed that HYH is such a resounding success; regular members sweep the floor and clean the bathroom every other week! Ask any other community organizer, this is amazing stuff and we have an amazing community.
The good news is that we've tried to structure HSL in such a way that it can live with and thrive under this type of volunteerism; but finances and computer systems don't really jive with a crowdsourced approach so I'm trying my best to automate those bits so as not to burn out the volunteers assigned those duties.
</rant>
I agree that a slow "encouraged" transition is probably better for retention than a quick mandatory one. That's the kind of transition I was planning.
There is no automatic way of grabbing a CSV from PayPal that I know of; I could write scripts, but you'd still have to feed the data in by hand every month and there would be errors. It's feasible but with all the awesome stuff we're trying to do I don't feel like it's up to the task. PayPal also offers some kind of payment notification API but I'm not sure I want to spend a third night up til 4am just to see if it compares to Stripe...
I mostly want to make sure Stripe is an acceptable option for people. If it's not, I can keep banging my head against 90's technology ;)
> I log into our paypal like, every other day. I can pull out a CSV pretty easily.
Wat. It appears we need to chat before I continue further :P
The rest of this thread: any objections to Stripe itself, regardless of what we do with PayPal? The lack of an SSL icon in the address bar not freaking anyone out?
--
Steve: good thing I didn't let my cursing out here on the group! IPN is one alternative I've considered, however I haven't tried it yet.
One reason IPN isn't appealing is because I have limited hours of volunteer dev time, and IPN seems to be notification-only, so for example when a member wants to up/downgrade their subscription, they would still have to login to paypal, (FIND and) cancel their recurring profile, and then login to our website to click the button on their member profile again -- an unintuitive workflow. More advanced integrations like querying subscriber status and accounting for fees charged also seem quite difficult. Finally, Stripe's API is just so damn easy to integrate it seems like more bang for my development buck. I find it unacceptable that PayPal doesn't seem to have full-fledged APIs or upgrade paths for their easy-to-use buttons and I just spent 8 hours chasing a white rabbit...
I just chatted with Chad and it seems like the best option is to move towards ADDING Stripe as an option and gently encouraging people to switch, and working from there.
If anyone likes PayPal/Dwolla/Stripe/etc or just wants to help, your help during Backend and Treasury Hacknights would really be appreciated.
(Edit: if anyone likes PayPal/etc and wants to help implement other stuff like IPN/CSV/etc, it is a low priority for me, so your help is requested to make things like that happen... general programming help is also appreciated. Keep your ears out for hacknights!)
>> from having to do data entry by hand :P
Mark, I don't see a tab like that, how do you get there, and does it work?
Doug: the main problem is that they're piling new technology on top of 90's-era technology, so they don't have one unified service. It's pretty easy for consumers, of course, otherwise they'd go out of business. But for payees it's an unwieldy dinosaur compared to their new (finally!) competitors.
I’d love it if PayPal were ditched and there was another automatic recurring payment option.
I have been looking at Stripe and from a merchant perspective it is stupid simple to manage. The code to make a site that can be customer managed doesn't seem to hard if you know JS (I am JS r-tarded) I am playing around with making a site but I found I don't need it for my purposes since I would be handling all the CC info anyway.
I agree; I really want it to be recurring automatically.
From: heatsy...@googlegroups.com [mailto:heatsy...@googlegroups.com]
On Behalf Of Jacob Rosenthal
Sent: Wednesday, May 01, 2013 11:53 AM
To: heatsy...@googlegroups.com
Subject: Re: [HSL] Feedback: Ditching PayPal
probably ^lose
On Wednesday, May 1, 2013 11:51:55 AM UTC-7, Jacob Rosenthal wrote:
If we do it lets be decisive about it, pick something we wont have to change again for another 3-5 years at least, and lets get it right the first time.
The beauty of recurring payments is people are too lazy to cancel them. That lazyness will be outweighed quickly when we start sending annoying emails for a month straight telling them they need to go here, click this, cancel this, resign up here. We will probably at least 5% of our recurring payments during this swap.
But better now than a year from now when we want to move and we can't take that hit.
On Wednesday, May 1, 2013 11:41:03 AM UTC-7, Nate Plamondon wrote:
Looks like it will do the trick.
One concern is that it's not clear whether this will be a recurring payment or I'll have to come back and do it again next month. "Pay $50" seems to imply that it's a one-time payment.
--
Nate Plamondon
On Wed, May 1, 2013 at 11:19 AM, Will Bradley <bradle...@gmail.com> wrote:
PayPal works the majority of the time, and everybody seems to have it. But when it fails you, it fails HARD. Here's the answer I found at Hour 8 of implementing PayPal's API for us: https://www.x.com/developers/paypal/forums/nvp/subscription-profiles-not-supported (English: people who use the yellow Pay with PayPal buttons are second class citizens.)
I'd like people to check out http://hslbilling.herokuapp.com/customers however. Do you think Stripe's credit card form is acceptable?
On May 1, 2013 8:44 AM, "Ryan Mcdermott" <blh...@gmail.com> wrote:
I'll pay you however you want me to.
I am confused about paypal hate, though. I use paypal a *lot*, (I use it for everything I buy online, if I can), and have never had a problem with it.
Is it just the fees or something?
-Ryan
On Wed, May 1, 2013 at 8:37 AM, Corey Renner <vand...@gmail.com> wrote:
" PayPal really sucks"
I don't know if I said it here or on another forum, but my thought was this:
"If the Nazis created an online payment system, it would still be slightly less evil than PayPal."
I welcome the replacement.
cheers,
c
On Wed, May 1, 2013 at 3:14 AM, Will Bradley <bradle...@gmail.com> wrote:
Hey all! I tried my best to lighten our bookkeeping workload by hooking our member database into PayPal, but it turns out that PayPal really sucks. I've found an alternative but want your input (especially input from people who give HeatSync money.)
--
You received this message because you are subscribed to the Google Groups "HeatSync Labs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
heatsynclabs...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "HeatSync Labs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
heatsynclabs...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "HeatSync Labs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
heatsynclabs...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.