PayPal RESTful API Payment Module

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

[g2ktcf]

Making progress. But I did learn the Paypal's developer tools are really good. I have a new error and the error is fully detailed

https://drive.google.com/file/d/1K35...usp=drive_link

Now this is clearly NOT a RESTful PayPal but an account issue at PayPal. But below this link is the full JSON Request and Response. Very nice!

Now if I can just figure out how to set up my account to take credit cards (never had issues with the older system).

[g2ktcf]

I forgot that the new plugin is both Pro AND Express. We do not have a Pro account so we do not take credit cards directly. I set up the plugin to accept them so I appear to be mistaken in that regard. We have to go the PayPal site to enter and use CCs. I was able to verify a new order and refund it completely.

And no, I do not like how PP responds overall. It now FORCES you to create a PP account. But this particular site does not have a huge amount of traffic right now and we cannot pay monthly fees for PP Pro so this is just how it has to go.