[iTMG]

We're using the E-xact hosted checkout plugin straight from the default core system but its config does not appear to work with what Chase requires –
x_login
x_fp_sequence
x_fp_timestamp
x_amount
x_fp_hash
x_show_form

but some of this appears nowhere in the config for this LS payment method – some, obviously would be automated, but can LS confirm that this payment method is confirmed working with the Chase E-xact system as is? The errors we're receiving seem to suggest to the Chase people, that we're not sending over proper params.

Thanks

[iTMG]

Follow up detail : the E-xact method also provides for a relay response key, but when we enter the key in and save, the save say that it's successful but never shows up the next time we view the E-xact configuration tab.

Is it even saving?

[Aleksey]

Hi, iTMG!

The relay response key is a password-type value. We never send password values back to browsers, because then they could be saved into the browser cache and stolen.

Regarding the fields issues - I will contact you by email. Thanks!