Rails - Dec 2005 - Payflow Pro (was Re: FatWreck.com - New Rails Site)

Several years ago, before PHP introduced their built-in pfpro functions, I
rolled my own crappy interface, which of course delegated to the commandline
payflow client. I could certainly do the same in Ruby today.

Thinking back on it, I realized at the time, and realize again now, that
delegating this functionality to a commandline app is a security risk unless
you''re the *only* user on the server.

What we should really like to see is a library similar to PHP''s pfpro
library, wherein the financial transaction data gets SSL treatment before
leaving our apps, and communication happens directly between our apps and
the payflow server. I know a guy who''s written some C/C++ Ruby
extensions,
and he might be willing to pull this off for a price. If I end up hiring
this out and getting it done, I will make it available to the community, of
course. I''m not sure how timely it''ll be, as I won''t
need this library until
next summer when I plan rewrite our ecommerce system.

Hunter... do you work directly for FatWreck? If so, your organization and
mine have worked together before ;-) Please feel free to contact me
off-list, regardless.

Everyone else... if you have experience using Payflow Pro''s service and
would be interested in seeing a native Ruby library, I''d love to hear
from
you, too.

On 12/21/05, Hunter''s Lists
<lists-HAWAbpnI61OZ1JSuHaJ1sQC/G2K4zDHf@public.gmane.org>
wrote:
>
> Well, it works totally different than the Payment gem code for
> Authorize.net (which I used in another project and also works well).
>
> I have no problem with it, only issue is that it is heavily based on code
> I got from someone else so I need to ask first.
>
> Keep in touch with me and we''ll get this figured out.
> ------------------------------
> *From: *David Rose <doppler-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> *Reply-To: *<rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org>
> *Date: *Tue, 20 Dec 2005 19:43:55 -0600
> *To: *<rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org>
> *Subject: *Re: [Rails] FatWreck.com - New Rails Site
>
> Oooh. Would you be willing to share your Payflow code? I''ll be
rewriting
> an ecommerce app next spring, and I''d love to not have to reinvent
a wheel
> you''ve already created ;-)
>
> Actually, it''d be great to integrate it into the Payment gem.
>
> David Rose
>
> On 12/20/05, *Hunter''s Lists*
<lists-HAWAbpnI61OZ1JSuHaJ1sQC/G2K4zDHf@public.gmane.org> wrote:
>
> Sorry, I forgot to respond to this.
>
> This site uses Verisign Payflow Pro.
>
> The connection is made using their command line scripts. We created some
> based heavily on some scripts that came from this list.
>
> Works pretty darn well actually.
>
> > From: Chris Grant
<rails-kAWxc+pSD0cqcZcGjlUOXw@public.gmane.org>
> > Organization: InterHive
> > Reply-To: < cgrant-kAWxc+pSD0cqcZcGjlUOXw@public.gmane.org
<mailto:cgrant-kAWxc+pSD0cqcZcGjlUOXw@public.gmane.org><cgrant@interhive.net>>,
<
> rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org>
> > Date: Tue, 20 Dec 2005 15:44:58 -0600
> > To: <warrens-uf+uqdaZT6qTt3WsUyM9gg@public.gmane.org 
<mailto:warrens-uf+uqdaZT6qTt3WsUyM9gg@public.gmane.org><warrens@actcom.net.il>>,
<
> rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org>
> > Subject: Re: [Rails] FatWreck.com - New Rails Site
> >
> > Definitely interested in this question, as well...
> >
> > Using Authorize.net <http://Authorize.net>
<http://Authorize.net> ?
> >
> > Thanks,
> > Chris
> >
> > Warren Seltzer wrote:
> >
> >> How do you connect your store to the payment system and to the
merchant
>
> >> account at the
> >> bank?
> >>
> >> Warren Seltzer
> >>
> >>
> >> -----Original Message-----
> >> From:
rails-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
>
<mailto:rails-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org><rails-bounces-1W37MKcQCpISTaT7VFAJlw@public.gmane.orgils.org>
> >>
[mailto:rails-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org]<rails-bounces-1W37MKcQCpI5u/9nSYX9/w@public.gmane.orgnrails.org%5D>On
> >> Behalf Of Hunter''s Lists
> >> Sent: Thursday, December 15, 2005 11:39 PM
> >> To: Rails
> >> Subject: [Rails] FatWreck.com - New Rails Site
> >>
> >>
> >> After months of design and development, we''ve launched
our second Rails
> >> site, http://www.fatwreck.com 
<http://www.fatwreck.com><http://www.fatwreck.com> (assuming your
DNS is updated - the pink site
> >> is the old one).
> >> ...
> >>
> >>
> >> _______________________________________________
> >> Rails mailing list
> >> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> >> http://lists.rubyonrails.org/mailman/listinfo/rails
> >>
> >>
> >>
> >
> > _______________________________________________
> > Rails mailing list
> > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> > http://lists.rubyonrails.org/mailman/listinfo/rails
>
>
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
>
> ------------------------------
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
>
>

_______________________________________________
Rails mailing list
Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
http://lists.rubyonrails.org/mailman/listinfo/rails

David,

First of all, thanks for the willingness to share ... that''s how we all
get to where we need to be. =)

I am going to voice what I believe is needed...

Rather than focus on a particular payment gateway (ie. PayFlow Pro), we 
should work toward an open, extensible payment module.  Something that 
could easily be tailored for any one of the various gateways that are 
available (ie. Authorize.net, PayPal Processing, RBS Lynk, etc.).  The 
protocols of these various providers, for the most part, are very 
similar and usually differ only in the names and formatting of the 
particular variables that are passed to the gateway.

They usually follow the same processes:
1) URL of gateway.
2) HTTPS communication with gateway.
3) Credentials to identify merchant (eg. terminal ID, merchant ID, etc.)
4) Order details.

Sure, some gateways offer more options and that''s where customization 
would be required.

I''ve only recently begun working with Rails (and Ruby) and find the 
framework/language/community/workflow amazing.  There should be some way 
to release updated gateways, as they become available.  For instance, I 
am currently working with my processor (RBS Lynk) to get the API that''s
necessary to communicate with their gateway.  It''s going to cost a 
pretty penny but it''s worth it for us, as we can reduce our
clients''
initial investments and reappropriate portions of the savings toward 
additional features, etc.

I guess the only problem may be ... how do you design something like 
this that would fit most developers/gateways?

It may be a case similar to that of the login generators ... how do you 
please everyone and still have a useful feature/plugin?

-Chris

David Rose wrote:
> Several years ago, before PHP introduced their built-in pfpro 
> functions, I rolled my own crappy interface, which of course delegated 
> to the commandline payflow client. I could certainly do the same in 
> Ruby today.
>
> Thinking back on it, I realized at the time, and realize again now, 
> that delegating this functionality to a commandline app is a security 
> risk unless you''re the *only* user on the server.
>
> What we should really like to see is a library similar to PHP''s
pfpro
> library, wherein the financial transaction data gets SSL treatment 
> before leaving our apps, and communication happens directly between 
> our apps and the payflow server. I know a guy who''s written some
C/C++
> Ruby extensions, and he might be willing to pull this off for a price. 
> If I end up hiring this out and getting it done, I will make it 
> available to the community, of course. I''m not sure how timely
it''ll
> be, as I won''t need this library until next summer when I plan
rewrite
> our ecommerce system.
>
> Hunter... do you work directly for FatWreck? If so, your organization 
> and mine have worked together before ;-) Please feel free to contact 
> me off-list, regardless.
>
> Everyone else... if you have experience using Payflow Pro''s
service
> and would be interested in seeing a native Ruby library, I''d love
to
> hear from you, too.
>

From: "Chris Grant"
<rails-kAWxc+pSD0cqcZcGjlUOXw@public.gmane.org>
>
> Rather than focus on a particular payment gateway (ie. PayFlow Pro), we 
> should work toward an open, extensible payment module.  Something that 
> could easily be tailored for any one of the various gateways that are 
> available (ie. Authorize.net, PayPal Processing, RBS Lynk, etc.).  The 
> protocols of these various providers, for the most part, are very 
> similar and usually differ only in the names and formatting of the 
> particular variables that are passed to the gateway.
Found these on rubyforge, haven''t tried them yet:

http://rubyforge.org/projects/paypal/
  Library aiding with Paypal IPN from web applications.

http://rubyforge.org/projects/transact/
  A simple yet powerful means of creating and submitting transactions
  to secure payment gateways. Currently supports the Linkpoint gateway.
  PayPal and authorize.net support forthcoming (takes so long to setup
  a test account with them it''s ridiculous).

Sounds like transact is hoping to become the sort of module you''re
describing.


Regards,

Bill

There''s also the payment gem, which is designed to do what you  
indicated you''d like in the original email (abstraction of multiple  
payment gateways).  Currently works with authorize.net.

http://rubyforge.org/projects/payment/

On Dec 22, 2005, at 1:54 AM, Bill Kelly wrote:
> From: "Chris Grant"
<rails-kAWxc+pSD0cqcZcGjlUOXw@public.gmane.org>
>>
>> Rather than focus on a particular payment gateway (ie. PayFlow  
>> Pro), we should work toward an open, extensible payment module.   
>> Something that could easily be tailored for any one of the various  
>> gateways that are available (ie. Authorize.net, PayPal Processing,  
>> RBS Lynk, etc.).  The protocols of these various providers, for  
>> the most part, are very similar and usually differ only in the  
>> names and formatting of the particular variables that are passed  
>> to the gateway.
>
> Found these on rubyforge, haven''t tried them yet:
>
> http://rubyforge.org/projects/paypal/
>  Library aiding with Paypal IPN from web applications.
>
> http://rubyforge.org/projects/transact/
>  A simple yet powerful means of creating and submitting transactions
>  to secure payment gateways. Currently supports the Linkpoint gateway.
>  PayPal and authorize.net support forthcoming (takes so long to setup
>  a test account with them it''s ridiculous).
>
> Sounds like transact is hoping to become the sort of module you''re
> describing.
>
>
> Regards,
>
> Bill
>
>
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails

There is also ActiveMerchant

http://home.leetsoft.com/am/wiki

Current supporting  Authorized.net and  Moneris, with LinkPoint and
TrustCommerce under development.

-eric

Fortunately, this application is dedicated to its own server.

You¹re right though, I wouldn¹t feel great about this on a shared server.

The other Rails based commerce site we did, we had the customer use
Authorize.net explicitly because of the Ruby integration...

SEE MERCHANTS!! RUBY SUPPORT WILL WIN YOU CUSTOMERS!

From: David Rose <doppler-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Reply-To: <rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org>
Date: Wed, 21 Dec 2005 23:28:25 -0600
To: <rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org>
Subject: Payflow Pro (was Re: [Rails] FatWreck.com - New Rails Site)

Thinking back on it, I realized at the time, and realize again now, that
delegating this functionality to a commandline app is a security risk unless
you''re the *only* user on the server. 



_______________________________________________
Rails mailing list
Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
http://lists.rubyonrails.org/mailman/listinfo/rails

We used this on a different project and it worked great. The customer went
with Authorize.net just because of this reason.

> From: Steven Smith <ssmith-ykxUa7oIpO9Wk0Htik3J/w@public.gmane.org>
> Reply-To: <rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org>
> Date: Thu, 22 Dec 2005 08:30:39 -0600
> To: <rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org>
> Subject: Re: Payflow Pro (was Re: [Rails] FatWreck.com - New Rails Site)
> 
> There''s also the payment gem, which is designed to do what you
> indicated you''d like in the original email (abstraction of
multiple
> payment gateways).  Currently works with authorize.net.
> 
> http://rubyforge.org/projects/payment/
> 
> On Dec 22, 2005, at 1:54 AM, Bill Kelly wrote:
> 
>> From: "Chris Grant"
<rails-kAWxc+pSD0cqcZcGjlUOXw@public.gmane.org>
>>> 
>>> Rather than focus on a particular payment gateway (ie. PayFlow
>>> Pro), we should work toward an open, extensible payment module.
>>> Something that could easily be tailored for any one of the various
>>> gateways that are available (ie. Authorize.net, PayPal Processing,
>>> RBS Lynk, etc.).  The protocols of these various providers, for
>>> the most part, are very similar and usually differ only in the
>>> names and formatting of the particular variables that are passed
>>> to the gateway.
>> 
>> Found these on rubyforge, haven''t tried them yet:
>> 
>> http://rubyforge.org/projects/paypal/
>>  Library aiding with Paypal IPN from web applications.
>> 
>> http://rubyforge.org/projects/transact/
>>  A simple yet powerful means of creating and submitting transactions
>>  to secure payment gateways. Currently supports the Linkpoint gateway.
>>  PayPal and authorize.net support forthcoming (takes so long to setup
>>  a test account with them it''s ridiculous).
>> 
>> Sounds like transact is hoping to become the sort of module
you''re
>> describing.
>> 
>> 
>> Regards,
>> 
>> Bill
>> 
>> 
>> _______________________________________________
>> Rails mailing list
>> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
>> http://lists.rubyonrails.org/mailman/listinfo/rails
> 
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails

I contacted Authorize.net, but it seems they only allow US businesses.

Does anyone know of an international payment gateway that would be
easy to integrate with a Rails app?

On 12/23/05, Hunter''s Lists
<lists-HAWAbpnI61OZ1JSuHaJ1sQC/G2K4zDHf@public.gmane.org>
wrote:
> We used this on a different project and it worked great. The customer went
> with Authorize.net just because of this reason.

I don''t know about international support specifically, but  
TrustCommerce is an excellent outfit, with good Ruby support.

On Dec 23, 2005, at 12:01 AM, Carl-Johan Kihlbom wrote:
> I contacted Authorize.net, but it seems they only allow US businesses.
>
> Does anyone know of an international payment gateway that would be
> easy to integrate with a Rails app?
>
> On 12/23/05, Hunter''s Lists
<lists-HAWAbpnI61OZ1JSuHaJ1sQC/G2K4zDHf@public.gmane.org> wrote:
>> We used this on a different project and it worked great. The  
>> customer went
>> with Authorize.net just because of this reason.
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails