wooq123

Issue still hasn’t been fixed by PayPal

Yep, still hasn’t been fixed by PayPal.

Thanks Niklas, it’s still occurring as of today so hopefully someone at PayPal is looking into the issue.

Update: I can confirm the issue started occurring on 9/14/22 just like mturner719 stated. It must be on PayPal’s end. I tried switching to the Angell Eye plugin and the same thing happens. Also tried rolling back to an older Woocommerce version and still same issue. Every “Advanced Credit Cards” payment comes through with “We have no postal address on file” message as of 9/14/22. Transactions before 9/14 show the address passed through perfectly. Issue has to be on PayPal’s end.

This is an urgent issue. Tried reverting to old version and no change. “Postal address not on file” for every advanced credit card order, which means no seller protection.

Yep same exact problem here. Started noticing it a few days ago. Nothing has been changed on my site either. All credit card form payments (under “PayPal Card Processing” tab) are coming through on Paypal with “no postal address on file”.

• This reply was modified 2 years, 6 months ago by wooq123.

Is there possibly a line that can be added to functions.php that would simply prevent any stripe scripts/api calls from running on all pages except cart and checkout? The same scripts on the official stripe woocommerce plug-in are able to be turned off with a few lines of functions.php code, so I assume this plug-in should be similar.

I’m on the newest (4.1.6.2). So this table isn’t even necessary unless I were to revert back to a version before 4.0? Sounds like I can disable auto load and even delete the table?

If I instruct the customer to use the paypal checkout button and the guest checkout feature, there is no issue with declines (this is if I catch them before they abandon the site entirely out of frustration). When the a card is processed through the credit card form on the checkout page, it’s HIGHLY sensitive to the way the billing details are typed and declines at a very high rate. I cannot find any distinct errors in the log file. However, I do frequently see these lines in the log:

Response Body: {“name”:”AUTHORIZATION_ERROR”,”debug_id”:”3e0f1******”,”message”:”Authorization error”,”information_link”:”https://developer.paypal.com/webapps/developer/docs/api/#AUTHORIZATION_ERROR”,”details”:[{“name”:”REFUSED_MARK_REF_TXN_NOT_ENABLED”,”message”:”This merchant account is not permitted to create Merchant Initiated Billing Agreement”}]}

The logs are riddled with constant “[code] => 201" "[code] => 200" "[code] => 204" messages also.

Are you guys having the issue specifically with the “card processing” credit card form at checkout? I just responded to a similar post. The Paypal system is being extremely particular with how billing addresses are typed. If something is abbreviated a certain way that the system doesn’t like, it will decline the payment. Very big issue & causing lost sales.

I have the same issue. Very frequent card declines. I determined it’s due to the PayPal system being extremely particular about the billing address. For instance, a customer changed his street from “lane” to “ln” and it worked. In another case “P.O. Box” was changed to “PO Box” and it went through. I’m losing sales over this issue – hopefully PayPal will adjust the system to not be this finicky.

The request that pagespeed insights and gt metric was seeing on every page, when the plug-in was enabled, is https://js.stripe.com/v3/?ver=3.0 . I can re-enable and take the screenshot if needed, but that’s the request the plug-in was making on every page, even on product pages where the request buttons were disabled.

Thanks Niklas, you’re awesome. I really appreciate the quick solution.

I’ve tried changing from “authorize” to “capture” and no emails are being sent other than the “new order” email to the website admin. Under Woocommerce > Settings > Emails, I have all emails enabled, including “processing” and “on-hold”. No emails are being sent to the customer when an order is placed. Anyone else have this issue?

• This reply was modified 3 years, 3 months ago by wooq123.

Ran into this issue when updating to the newest version. I’ve had to roll back to 1.13.1 due to this issue and multiple other issues that I can’t figure out.