If the billing address and payment method (Commerce Authorize.Net) are on the same page and the billing address pane is before the payment method pane then the billing address shows up on the Authorize.Net back-end. Otherwise, if the billing address comes after the payment method (even on the same checkout page) the billing address does not come through on the Authorize.Net back-end.

It seems as though this was only coded for one scenario which is that the payment method pane is one review page (which i'm fine with for now but a "one-page-checkout" would be great) and the billing address was entered before this.

This seems to be a bug to me. Please correct me if this is wrong.

=>Pete<=

Comments

rickmanelius’s picture

rickmanelius commented

Seems related to #1328762: Credit card rejected/declined, order goes through anyway, although this one has a more descriptive/accurate title. If it's not possible to fix this programmatically, we might have simply warn the user (my suggestion in the other thread).

rszrama’s picture

rszrama commented
Category: bug » support
Status: Active » Closed (works as designed)

Yeah, this isn't a bug but merely a constraint of the checkout form. It processes checkout pane data in their order of appearance on the form with no way of knowing that the Payment pane depends on data found further down the page. This is primarily a problem because we aren't simply retaining payment data to process upon checkout completion but attempt to process payment immediately. I'll document this right now.