PayPal RESTful API Payment Module

[dbltoe]

Is it just me or is the following backwards?
Attachment 20812
If I select True, everyone can use CC from PayPal.

If I select False, only registered customers can use CC from PayPal.

Ther wording seems to be correct, but the action when selecting True or False seems to be reversed.

[lat9]

Is it just me or is the following backwards?
Attachment 20812
If I select True, everyone can use CC from PayPal.

If I select False, only registered customers can use CC from PayPal.

Ther wording seems to be correct, but the action when selecting True or False seems to be reversed.

I think it's just you.

true ... anyone checking out (guests included) can use credit cards
false ... no one can use credit cards
Account-Holders Only ... anyone with an account can use credit cards, i.e. guest customers cannot.

[dbltoe]

Do you consider the same results if you slightly modify what is being stated?

Essentially, it is say do you want to limit and the default is no. (false)

However, selecting that I do want to limit, gives access to all.

Perhaps "If you are using One Page Checkout, you can limit credit card payments. Who can access your store's credit card processing? Default Everyone.

Everyone

No One

Account Holders Only


That covers all the bases although I can't think of a scenario where a business would want to deny CC processing completely unless they're a street-corner, cash-only business.

I'm probably number 1189 on the top ten list of PHP knowledge but I do have an extensive English background with three English majors in the family. They all guessed that the selection of false let everyone process. All based on the emphasis on limit.

[Jeff_Mash]

Cindy - I posted this on the GitHub repository, but thought I'd include it here in case it helps get more attention:

Version v1.0.4.

I am noticing an issue in our system. When a customer places a PayPal order (not all the time, but a lot), the STATE that is being sent to PayPal is "California" where we are based.

For example, in ZenCart database, the address in both the Customer and the Orders Table is:

1234 Newbank Circle Suite 207
Dublin, OH 43017

But when I pull up PayPal to look if the address is verified, I see this on PayPal:

1234 Newbank Circle Suite 207
Dublin, CA 43017

I have seen this with multiple orders now, where the order looks fine in ZenCart, but when pulling it up on PayPal's website, they have "CA" as the state.

Is this a bug or perhaps is there something I need to check with my current installation?

I checked the "ipn_1732546861_MsKv7.log" file created for this example order and it shows "CA" as the state being pushed to PayPal, so something within our installation is sending that incorrect state to PayPal.

UPDATE: This doesn't seem to happen with every order.......but when it did, I noticed another WARNING LOG for the same transaction (ipn_1732546861_MsKv7-warning.log)

It seems that that warning log may indicate what is causing CA to be passed as the state to PayPal?

[lat9]

Cindy - I posted this on the GitHub repository, but thought I'd include it here in case it helps get more attention:

Version v1.0.4.

I am noticing an issue in our system. When a customer places a PayPal order (not all the time, but a lot), the STATE that is being sent to PayPal is "California" where we are based.

For example, in ZenCart database, the address in both the Customer and the Orders Table is:

1234 Newbank Circle Suite 207
Dublin, OH 43017

But when I pull up PayPal to look if the address is verified, I see this on PayPal:

1234 Newbank Circle Suite 207
Dublin, CA 43017

I have seen this with multiple orders now, where the order looks fine in ZenCart, but when pulling it up on PayPal's website, they have "CA" as the state.

Is this a bug or perhaps is there something I need to check with my current installation?

I checked the "ipn_1732546861_MsKv7.log" file created for this example order and it shows "CA" as the state being pushed to PayPal, so something within our installation is sending that incorrect state to PayPal.

UPDATE: This doesn't seem to happen with every order.......but when it did, I noticed another WARNING LOG for the same transaction (ipn_1732546861_MsKv7-warning.log)

It seems that that warning log may indicate what is causing CA to be passed as the state to PayPal?

PayPal RESTful doesn't make use of IPNs and none of its generated logs start with ipn_ ... so I'm not sure where those logs are coming from.

[Jeff_Mash]

PayPal RESTful doesn't make use of IPNs and none of its generated logs start with ipn_ ... so I'm not sure where those logs are coming from.

Yeah, I don't know either. I just noticed that at the exact same time as the PayPal transaction occurred (with the incorrect STATE being passed to PayPal), I had that corresponding IPN log file, which references the ipn_main_handler.php.

If you look at the contents of that IPN warning log, you can see that it references the PayPal IPN as well as the freeoptions.php.

When I look at my Payment Modules, only paypalr is enabled. The other two (paypaldp and paypalwpp) are orange (disabled). Perhaps I should actually REMOVE them and see if that helps?

[lat9]

Yeah, I don't know either. I just noticed that at the exact same time as the PayPal transaction occurred (with the incorrect STATE being passed to PayPal), I had that corresponding IPN log file, which references the ipn_main_handler.php.

If you look at the contents of that IPN warning log, you can see that it references the PayPal IPN as well as the freeoptions.php.

When I look at my Payment Modules, only paypalr is enabled. The other two (paypaldp and paypalwpp) are orange (disabled). Perhaps I should actually REMOVE them and see if that helps?

It depends on whether you have any orders paid with those payment modules that might need an update (i.e. a refund or a capture). If all orders paid with them are cleared, then removing them would (I think) also deactivate the ipn_main_handler.php operations.