Customers suddenly can't use square in checkout on my website

Questions
1

Hi, customers are getting this error now when they go through checkout, but not when they use another payment method:

–

Error in charge [GONE]: The request could not be completed since access to the target resource is no longer available.

Payments worked great before, but now just suddenly stopped.

I have WordPress website. I use a membership script, aMember, which is also installed on my hosting account server.

Customers click payment button on website, get sent to shopping cart, and have payment options (square in one). They can enter their card info on checkout, but get the error above when they try to submit payment.

How can I resolved this so I can accept square payment again?

2

Here is screenshot of error customers are getting:

Screenshot_20260812_173211_Chrome
Screenshot_20260812_173211_Chrome1080×2340 165 KB

4

Hi @dsellers - since this was working previously and suddenly is no longer working, please check the following:

  • Verify that your aMember Square plugin is up to date and generating a new payment token for each transaction.
  • Confirm your app’s OAuth token is still active (check in your Square Developer Dashboard).
  • Check if your app is using the older Transactions API (/v2/transactions) - this API has been retired. We would recommend migrating to the Payments API if this error continues.
5

how do I verify is aMember is generating a new payment token for each transaction?

how do confirm your app’s OAuth token is still active?

6

@dsellers To verify that aMember is generating a new token, you can watch it happen live in two methods: either check the aMember plugin logs, or open browser dev tools > Network tab. Go through the checkout flow twice, and you should be able to see two different payment tokens appear (cnon: …)

Any external apps using your Square account via OAuth should appear here. aMember should be listed here and connected.

Please confirm if your app is using Payments API - we have previously seen this error associated with continued use of Transactions API and recommend migrating to Payments API right away.

7

here, you can see the my square account. I’m assuming this means it’s active?

Also, in the aMEmber script, you can see how it’s configured, although I don’t know is app is using Payments API

sq1
sq11541×662 31.2 KB

sq2
sq21343×907 74 KB

8

@dsellers If you are unable to inspect the configuration of your app, please reach out to your implementation partner for further assistance since we are unable to control how your aMember integration behaves. Feel free to share this thread with them to follow the same troubleshooting steps to determine the root cause.

9

Hi, they (aMember team) are asking me for the migration guide to newes API. Do you perhaps have a link for this?

10

is this the migration guide to newest API?

11

@dsellers - Feel free to share the following:

12

I’m waiting to hear back from aMember team.

I do have question - when automatic payment is created with square through website app, like a script built into membership script in wordpress, for example one $50 payment every 30 days, should this still work even through recieving new orders is being blocked? I’m asking because I have customers who’s montly payments are not going though, and I’m getting emails that payment failed with that same ‘error in charge’ error.

I’m asking, because if it should be running automatically with square, and it’s not, perhaps there is something within my square account (not the membership script), that is causing issues?

13

Since aMember is a membership script, it is possible that the errors you are receiving for those payments are still connected to an error relating to the aMember integration. If the integration developer does find an issue, they are welcome to reach out to us for support!

14

they updated plugin within aMember and it now seems to work - thank you