PayFlow and XMLPay

[Russ Rollins]

I'm integrating ActiveMerchant with an in-house Rails CRM being
developed. A huge thanks for opening ActiveMerchant to the public. It
was a breeze to test and integrate it today though I did need to make
one change regarding the credentials for invoking the Payflow gateway--
my login is not the same as my vendor account. I thus changed a line
in payflow_common_api.rb:
xml.tag! 'Vendor', @options[:login]
to
xml.tag! 'Vendor', (@options[:vendor] || @options[:login])

The only other thing (issue?) I noticed is that the the response is
built with :authorization => @response[:pn_ref] but according to the
XMLPay API (page 38) the AuthCode entity contains the actual
authorization code. For now I'm snagging that from the response
params, but I thought I'd at least bring it up here.

Is this worthy of submitting a patch?

-Russ-

[Cody Fauser]

Russ,

The reason that we return the PN Ref as the authorization is because
that is what is required as a reference when capturing, voiding,
crediting, etc. The actual authcode doesn't serve any later purpose.

I just added the ability to use a :user option, which is basically
what you did, but the reverse. So, by default, the gateway will use
the :login for both the Vendor and User, unless you specifically
override it with the :user option.

--
Cody Fauser
http://shopify.com - e-commerce done right
http://www.codyfauser.com - blog
http://www.oreilly.com/catalog/rjsrails - RJS Templates for Rails

[Russ Rollins]

Cody,

Thanks for the clarification regarding PNRef. I think my primary point
of confusion was that when the response object was returned, and
success was false, there was still an authorization value where I had
expected it to be nil. I'll sort out our requirements with our
accounting department and adjust my code as needed.

Appreciate the quick response and the release of ActiveMerchant to the
Rails community!
-Russ-

On May 7, 7:32 pm, "Cody Fauser" <codyfau...@gmail.com> wrote:
> Russ,
>
> The reason that we return the PN Ref as the authorization is because
> that is what is required as a reference when capturing, voiding,
> crediting, etc. The actual authcode doesn't serve any later purpose.
>
> I just added the ability to use a :user option, which is basically
> what you did, but the reverse. So, by default, the gateway will use
> the :login for both the Vendor and User, unless you specifically
> override it with the :user option.
>