Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.OK, bear with me as I describe the symptoms.
Customer reports having had to go submit checkout form twice in order to complete transaction.
Payment records confirm this.
First attempt results in error message:
"The customer must be able to supply a billing address through the default address field of the core billing information customer profile to pay via PayPal WPP."
Second attempt results in a contradictory status:
Authorization and capture - Success
AVS response: Nothing matched; transaction declined
Paypal reports that the transaction has been charged successfully and order status is "Paid".
Billing info fields are all standard, and most customers are checking out with no issue.
The customer having to submit the checkout form twice is troublesome.
But the declined/success contradiction is most worrisome.
How can this even happen?
Is this something to do with auth/capture or AVS settings in paypal?
Please let me know if I can provide more information in order to debug this issue.
edit: "attempted" was not relevant.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | Screen Shot 2013-10-04 at 15.33.18.png | 14.75 KB | wemakewebsites |
Comments
Comment #1
rszrama commentedMy best interpretation of what you've presented is that the customer was missing some billing information, which resulted in the first failed payment attempt. This could have occurred on an outdated version of Commerce (I believe pre 1.4) that did not prevent payment attempts if there were errors on the page and this was a single page scenario where the billing information pane was on the same page as payment. (Or if the billing information pane appeared after the payment pane; they evaluate in order of appearance, so it would have to be first. However, since this happened only once, I'm guessing you don't have that configuration.)
The second transaction succeeded - what really matters is the status of the payment transaction, and in this case it was "Success" with a green check mark icon (my assumption; a screenshot would've helped). The AVS response (address verification) is separate from whether or not the transaction succeeded. If your PayPal fraud settings are low, then even though AVS returns a "Nothing matched; transaction declined" message, PayPal may still permit the transaction. This isn't good for you - you should configure PayPal to decline in these cases, because it means the customer used an incorrect address and may be trying to defraud you.
I don't think there's anything for us to change in the code for this. PayPal defines the AVS response codes and gives these messages for them.
Comment #2
wemakewebsites commentedI am only seeing the last problem - I get the contradiction:
Authorization and capture - Success
AVS response: Nothing matched; transaction declined
Seems like we logged a payment and the client is checking in PayPal.
Anyone have any idea why it's happening?
Comment #2.0
wemakewebsites commentededit: "attempted" was not relevant