[LRUG] Best Payments solution for Rails app?

[David Burrows]

Hi Cristoph,

That's really interesting, I was definitely getting that vibe off of
Paymill - we really need a EU Stripe but it's got to be reliable, hopefully
they can sort the teething troubles out. My experience so far with
Braintree is pretty good so it looks like I'll be going down that avenue,
will report back when I've (hopefully) gone through the whole process.

Best Regards,
David

-- 
David Burrows
079 1234 2125
@dburrows

http://www.designsuperbuild.com/ | @dsgnsprbld


On Thu, Feb 14, 2013 at 8:57 PM, Christoph Sassenberg <christoph at subscrib.co
> wrote:

> Hi David,
>
> we have been using Paymill for apprx. 1k GBP of live payments now.
> The gist: It is (was?) pretty young and rough. YMMV.
>
> My impressions so far:
>
> > I started working with Paymill a few weeks ago.  I found it pretty
> straightforward to understand their English documentation and integrate
> credit card subscriptions in my webapp (once I realised that a Paymill
> "offer" is what most people would call a "plan").
>
> The whole API is not really well documented in terms of possible failures
> and errors. Until last week creating subscriptions always succeeded even if
> the actual money transaction failed - providing no reasonable way to find
> out that it did. They quickly pushed out "webhooks" to mitigate that. I
> found a bug in the subscription cancellation regarding stale data in two
> consecutive requests, which is  resolved by now.
>
> The term "payment" refers to instances of "payment methods" (credit cards)
> and "transactions" are the actual payment transactions. I do not know why
> you are able to specify an amount along with a "payment".
>
> 3D Secure somehow disappeared - treated as normal now. Maybe something has
> changed since we implemented it.
>
> The documented auth failure card numbers in test mode are not working (as
> in: I cannot created a failed/declined transaction in test mode) - or at
> least I haven't found out how.
>
> > There's a good Ruby gem wrapping their API.  The API itself has all the
> key things in place but you still need to compose one or two higher-level
> things yourself, such as updating an existing recurring payment with a new
> credit card.  Hopefully this sort of thing will appear in the API in due
> course.
>
> The gem is _really_ basic, e.g. seconds-since-epoch-strings as date
> results. Personally, I like the whole approach of this[1] pull-request
> more, which was unfortunately declined.
>
> > So far I have found Paymill's non-technical support fast and helpful.
>  The technical support has been slow and less helpful – but perhaps I've
> just been unlucky.
>
> I can absolutely second that. At some point I just scheduled a phone call
> with a member of the technical team - which was indeed helpful.
>
> > In terms of actual money transactions I was off to an inauspicious
> start.  When the time came to move my first customer from my previous
> payment processor (FastSpring) to Paymill, I asked them to put their card
> info into my website.  Everything worked but the bank declined the
> transaction due to "banking risk issues". I asked Paymill to investigate
> and am awaiting a response.
>
> So far, most initial transactions from Lloyds' debit card customers have
> been declined - some were contacted by them and some needed to actively
> contact them to "approve" the transaction. One Mastercard guy (unknown
> bank) was rejected for risk reasons - he also needed to contact the bank.
> It is ok for now, as we can contact all the individuals, but might become a
> pain. Paymill say they cannot do anything about that.
>
> All payments are handled through "Lufthansa AirPlus Servicekarten GmbH" [2]
>
> Our first "Quadro de facturação" (statement?) was generated in the lovely
> language of Portugese. They are working on it ;)
>
>
> [1] https://github.com/dkd/paymill-ruby/pull/3
> [2] http://acceptance.de
>
>
> Regards,
> Christoph Sassenberg
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20130215/f14b7e89/attachment-0003.html>