PayPal RESTful API Payment Module

[siliconbug]

Zen Cart v1.58a
Paypal RESTful v1.0.2
Payment Action: Auth Only

I disable PayPal Express Checkout and enable Paypal RESTful today.

There are two orders. The 1st order is paid by PayPal Wallet, and the 2nd order is paid by Credit Card.

The 1st payment goes through, but the 2nd order gives me an error:

The payment module's observer (auto.paypalrestful.php) was not loaded; the payment module has been disabled. The payment module has been automatically disabled.

Both orders get this error when I capture the payments, but I can get correct $$ into my PayPal account:

Request URI: /ipn_main_handler.php, IP address: 173.0.81.140, Language id 1
--> PHP Warning: Use of undefined constant MODULE_PAYMENT_PAYPAL_ORDER_STATUS_ID - assumed 'MODULE_PAYMENT_PAYPAL_ORDER_STATUS_ID' (this will throw an Error in a future version of PHP) in /zencart/ipn_main_handler.php on line 475.

Something under PayPal Transactions doesn't look right.

Attachment 20651

Should I remove PayPal Express Checkout completely? Or any possible issue I missed?

[g2ktcf]

Why would I be getting an expired token? This is me trying to ENABLE the RESTful module.

2024-06-13 08:25:24: () validateCredentials: Checking ().
TokenCache::clear, clearing cached token.
The curlPost (v1/oauth2/token) request was unsuccessful.
{
"errNum": 401,
"errMsg": "An expired-token error was received.",
"curlErrno": 0,
"name": "n\/a",
"message": "n\/a",
"details": "n\/a",
"debug_id": "n\/a"
}
CURL Options: {
"78": 10,
"52": false,
"75": true,
"74": true,
"42": 0,
"19913": true,
"13": 45,
"47": true,
"10002": "https:\/\/api-m.paypal.com\/v1\/oauth2\/token"
}
************************************************

************************************************

2024-06-13 08:25:24: () validateCredentials: Checking ().
TokenCache::clear, clearing cached token.
The curlPost (v1/oauth2/token) request was unsuccessful.
{
"errNum": 401,
"errMsg": "An expired-token error was received.",
"curlErrno": 0,
"name": "n\/a",
"message": "n\/a",
"details": "n\/a",
"debug_id": "n\/a"
}
CURL Options: {
"78": 10,
"52": false,
"75": true,
"74": true,
"42": 0,
"19913": true,
"13": 45,
"47": true,
"10002": "https:\/\/api-m.paypal.com\/v1\/oauth2\/token"
}
************************************************

[g2ktcf]

Why would I be getting an expired token? This is me trying to ENABLE the RESTful module.

2024-06-13 08:25:24: () validateCredentials: Checking ().
TokenCache::clear, clearing cached token.
The curlPost (v1/oauth2/token) request was unsuccessful.
{
"errNum": 401,
"errMsg": "An expired-token error was received.",
"curlErrno": 0,
"name": "n\/a",
"message": "n\/a",
"details": "n\/a",
"debug_id": "n\/a"
}
CURL Options: {
"78": 10,
"52": false,
"75": true,
"74": true,
"42": 0,
"19913": true,
"13": 45,
"47": true,
"10002": "https:\/\/api-m.paypal.com\/v1\/oauth2\/token"
}
************************************************

************************************************

2024-06-13 08:25:24: () validateCredentials: Checking ().
TokenCache::clear, clearing cached token.
The curlPost (v1/oauth2/token) request was unsuccessful.
{
"errNum": 401,
"errMsg": "An expired-token error was received.",
"curlErrno": 0,
"name": "n\/a",
"message": "n\/a",
"details": "n\/a",
"debug_id": "n\/a"
}
CURL Options: {
"78": 10,
"52": false,
"75": true,
"74": true,
"42": 0,
"19913": true,
"13": 45,
"47": true,
"10002": "https:\/\/api-m.paypal.com\/v1\/oauth2\/token"
}
************************************************

So I have checked to make 100% sure that curl is enabled. This is a live site https://zc157d.dreamhosters.com

Do not let the zc157d tag confuse you, it is an old sandbox location and I just loaded 2.0.1 into that site.

[lat9]

So I have checked to make 100% sure that curl is enabled. This is a live site https://zc157d.dreamhosters.com

Do not let the zc157d tag confuse you, it is an old sandbox location and I just loaded 2.0.1 into that site.

My best guess is that your client-credentials are invalid.

[g2ktcf]

My best guess is that your client-credentials are invalid.

I did find an error, however, now I get a warning that the BRAND NEW CREDENTIALS I just created are invalid.

[g2ktcf]

I did find an error, however, now I get a warning that the BRAND NEW CREDENTIALS I just created are invalid.

Interesting that I had to go work on something else for a couple of hours. Came back and got the same error. Submitted a case to PP. Tried one more time and it worked...??? Is there some kind of time lag from setting up a new PP API App before the credentials are live???

[lat9]

Interesting that I had to go work on something else for a couple of hours. Came back and got the same error. Submitted a case to PP. Tried one more time and it worked...??? Is there some kind of time lag from setting up a new PP API App before the credentials are live???

I've no idea on the time-lag, but happy that you sussed it out.

[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.