Forum OpenACS Q&A: Re: OACS 5.3, and ecommerce configuration problem/issue.

Collapse
3: Re: OACS 5.3, and ecommerce configuration problem/issue. (response to 1)
Posted by Steve Manning on 05/25/07 10:12 AM
Bill

You can check that the parameter PaymentGateway has been set correctly easily enough with a little ns_log debug after 'set payment_gateway' to see whats returned.

If thats OK then its going to be the acs_sc_binding_exists_p returning 0 thats tripping you up. If you look that up in the API browser it will take you back to the table its looking at. I don't use the PaymentGateway but it looks like a problem with the service contract probably when it was initialised during the install.

- Steve

Collapse
4: Re: OACS 5.3, and ecommerce configuration problem/issue. (response to 3)
Posted by Bill Millikin on 05/25/07 04:31 PM
Thank you. I'm thinking that the problem is knowing what to say the package 'key' is in the param in ecommerce.

My payment_gateway returned is 'authorizenet', and acs_sc_binding_exists_p is returning 0. 'authorizenet' is where I have Authorize.net Gateway mounted. Should it be some other string, like the actual package name?

From the site map, I have:

URL Instance Package Name
authorizenet Authorize Net Authorize.net Gateway

What I think I'm not understanding is what a 'package key' is as called for in the ecommerce parameters at the field PaymentGateway.