# Verisign Payflow Scripts

**URL:** <https://www.ruby-forum.com/t/verisign-payflow-scripts/54224>\
**Category:** Rails\
**Created:** [December 23, 2005, 7:57pm UTC](https://www.ruby-forum.com/t/verisign-payflow-scripts/54224 "2005-12-23T19:57:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![HunterSs\_Lists](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/6bbea6/32.png) [@HunterSs\_Lists](https://www.ruby-forum.com/u/HunterSs_Lists)\
**Post date:** [December 23, 2005, 7:57pm UTC](https://www.ruby-forum.com/t/verisign-payflow-scripts/54224/1 "2005-12-23T19:57:27Z")

</div>

Here’s a link to the Verisign scripts we used… We customized ours a  
bit  
but this will get you going.

Graciously provided by Jon at Slantwise Design and posted with  
permission  
([http://www.slantwisedesign.com](http://www.slantwisedesign.com)), these may make it into some other  
format  
someday (gem? Plug in?).

Anyway, of course, no warranty with this code, use at your own risk and  
really no support - you’ll have to get that going on your own. Payment  
processing is not for the faint of heart.

Hope it is helpful.

[http://www.liberationmedia.com/payflow\_pro.tgz](http://www.liberationmedia.com/payflow_pro.tgz)

---

<div class="post-metadata">

**Author:** ![HunterSs\_Lists](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/6bbea6/32.png) [@HunterSs\_Lists](https://www.ruby-forum.com/u/HunterSs_Lists)\
**Post date:** [December 23, 2005, 11:19pm UTC](https://www.ruby-forum.com/t/verisign-payflow-scripts/54224/2 "2005-12-23T23:19:20Z")

</div>

Thanks for the code contribution…

I’ve been on and off the phone with our processor and it looks as though  
they may open the API for us … without paying the $2,000 or whatever  
they were wanting.

Definitely some finger crossing going on today.

-Chris

---

<div class="post-metadata">

**Author:** ![HunterSs\_Lists](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/6bbea6/32.png) [@HunterSs\_Lists](https://www.ruby-forum.com/u/HunterSs_Lists)\
**Post date:** [December 24, 2005, 12:55am UTC](https://www.ruby-forum.com/t/verisign-payflow-scripts/54224/3 "2005-12-24T00:55:36Z")

</div>

On 12/23/05, Chris G. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> Hunter’s Lists wrote:
> 
> > processing is not for the faint of heart.
> 
> * * *
> 
> Rails mailing list  
> removed\_email\_address@domain.invalid  
> [http://lists.rubyonrails.org/mailman/listinfo/rails](http://lists.rubyonrails.org/mailman/listinfo/rails)

But you still have to go through their binary. Someone needs to  
reverse engineer that. I would grab the Java version of the binary  
and decompile it. Alternately, you could ask them for source, or look  
at the PHP source, because I think it’s built into PHP.

–  
Kyle M.  
Chief Technologist  
E Factor Media // FN Interactive  
removed\_email\_address@domain.invalid  
1-866-263-3261

---

<div class="post-metadata">

**Author:** ![HunterSs\_Lists](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/6bbea6/32.png) [@HunterSs\_Lists](https://www.ruby-forum.com/u/HunterSs_Lists)\
**Post date:** [December 24, 2005, 1:43am UTC](https://www.ruby-forum.com/t/verisign-payflow-scripts/54224/4 "2005-12-24T01:43:42Z")

</div>

Yeah, the PHP build process relies on Verisign’s libraries at build time  
but  
they do have support for the process through that C library.l

> From: Kyle M. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
> Reply-To: [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
> Date: Fri, 23 Dec 2005 14:51:33 -0800  
> To: [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
> Subject: Re: [Rails] Verisign Payflow Scripts

But you still have to go through their binary. Someone needs to  
reverse

> engineer that. I would grab the Java version of the binary  
> and decompile it.  
> Alternately, you could ask them for source, or look  
> at the PHP source, because  
> I think it’s built into PHP.

–  
Kyle M.  
Chief Technologist  
E Factor

> Media // FN Interactive  
> removed\_email\_address@domain.invalid  
> 1-866-263-3261
