[ic] Authorize.Net "Unknown charge type:"
emailgrant at gmail.com
Sun Jul 30 13:40:17 EDT 2006
> > > > There is actually a long list of variables in the [payment] module. So, any
> > > > values that aren't passed to the charge tag explicitly are pulled from
> > > > the session's [value]s if possible?
> > > >
> > > No. None of the [charge] parameters will be pulled from the $Values
> > > space, as that would be far too insecure. Default parameter values can
> > > be stored in a Route or in Variables. Variables must be prefixed with
> > > "MV_PAYMENT_". The Route name must match the name given in the [charge]
> > > tag's "route" parameter.
> > >
> > Well, the following values must be pulled:
> > mv_credit_card_number
> > mv_credit_card_exp_month
> > mv_credit_card_exp_year
> There is a difference between the tag parameters, which will not
> be pulled from $Values space, and values, which cannot be passed
> as parameters. From the context of this thread, I thought we were
> talking about parameters.
> > I'm not passing them to the charge tag explicitly, but if I don't
> > submit them on the page I get the appropriate error responses.
> You can set keys in the $Value hashref before calling [charge],
> if you want to avoid using a HTML <form> for some reason. I can't
> think of a reason for doing that.
I'm just trying to get a handle on the way it work since I'm kind of
building my own virtual terminal. So, the following three variables
can not be passed as charge tag parameters and must be in the $Values
hashref when the charge tag is called?
> > Also, how can I get the values of the $result variables on my IC page?
> > For example:
> > x_response_reason_text
> > x_trans_id
> > x_avs_code
> > I've tried all kinds of stuff with no luck.
> I have a UserTag that you can use for that sort of thing. You can
> either use it directly or examine the code and use the same technique
> in your code.
> You can get the [payment-result] UserTag from this page:
Great tag. Much better than what I was doing. Thanks Kevin.
More information about the interchange-users