Something went wrong, please try again or contact support.

Hi @logitem,

Glad you reached out! Happy to help.

Anytime there’s a payment error in the front-end, there’s a more detailed message in the back-end under Donations → Tools → Logs. Click the eye icon next to any recent error message, and then copy and paste the full error message in your next reply.

Here’s a screencast on how to get error logs: https://screencast-o-matic.com/watch/c3eD0AVFgVG.

This will give us more details about the error.

Please don’t hesitate to contact us should you need more instructions or other concerns.

Thank you for your prompt reply. Here is the error generated.

{ “formId”: 1376761, “gateway”: “PayPal Donations”, “error”: “{\”error\”:\”invalid_token\”,\”error_description\”:\”Access Token not found in cache\”}” }

Hi, @logitem.

I have some recommendations that will help with that issue you are seeing.

The fix here is a bit technical, so I’ll include as much detail as possible, but you may need to reach out to your web developer or web support person to implement these recommendations.

Your issue here is caused by some caching happening somewhere in the process. If you’re unfamiliar with caching, it saves server resources by storing copies of a page, resource, query, or site so that the next visitor’s visit doesn’t trigger a call to the server at all; they get the saved copy. Instead of the site needing to recreate the page from scratch, it sends a copy, allowing it to load faster.

We put together this deep dive into what caching is and how it can cause problems:?https://givewp.com/documentation/resources/caching/

Caching works well for speeding up sites, but when a saved copy of the site has sensitive information (like donor info), it’s essential that GiveWP not share that with the next visitor. If GiveWP is not convinced that the browser requesting the data is correct, it defaults to not showing the data.

Caching is handled differently on various sites and web hosts. This could mean a caching plugin, or caching could be in a security solution. Hosting providers also have settings for server-level caching settings, and they can help make adjustments for you there. Most caching solutions have a setting or section for excluding specific URLs or parts of URLs (called “slugs”) from caching. At the very least, you should exclude the following slugs from caching:

/donations/
/donation-confirmation/
/donor-dashboard/*
any page with a donation form on it

Also, the following query strings (if your caching solution has a setting for them):

give-embed=donor-dashboard
giveDonationFormInIframe=1
give-listener=paypal-commerce
give-listener=ipn
give-listener=stripe

Your host or the caching plugin/solution can help with that. Some may require a “wildcard” like /donations/* to capture all subdirectories under the /donations/ folder.

Some folks prefer to customize the URLs to their site pages, so you may find that your URLs don’t have the slugs mentioned above, even though they contain the same content. In such cases, we recommend whitelisting the page, not just the slug; that way, the pages with those essential pieces of information are still excluded from caching. This is especially important for URLs of pages with donation forms on them.

One helpful tip: Check in with your hosting provider. Most hosts have caching at the server level, and they will be able to adjust this for you. You can also temporarily disable caching on the site to confirm that the uncached site isn’t showing the problem.

Many security solutions also include caching options, so be sure to give those settings a look.

While fine-tuning the cache falls outside the scope of the support we can provide, your success with online donations is our number one priority, and we’re happy to provide any tips.

Also, please disconnect and connect your PayPal Donations account.

This was quite a bit of information to share. If you have any questions about this, let me know. I’m happy to help.

Hello, thank you for your reply. I’ll try it out.

This button works

But this one gives me an error message.

how to remove the green button or make both work.
Thanks

• This reply was modified 1 month ago by Logitem.
• This reply was modified 1 month ago by Logitem.