WHMCS custom function - update pay method error - whmcs

I'm trying to access UpdatePayMethod endpoint, but it always returns this error message :
Error Updating Remote Pay Method: Remote Storage Failed
I'm using stripe credit cards.
Can anyone give me a clue on what's happening?

Related

(ssg-wsg) Keep getting error with error code 403

i am in UAT Phase and try to call the UAT API but keep getting error with error code 403, what shd i do to be able to call the API, below pict is my code
enter image description here
There doesn't seem to be enough information to tell what is the problem. Since you are given UAT access, the proper channel would be to contact their service desk on your issue: https://developer.ssg-wsg.gov.sg/webapp/faq?anchor=WhoCanIContactIfIHaveQuestionsAboutTheseAPIs

Why am I getting - "Cannot call API for app 439150000328651 on behalf of user 1245010195894306"

This error message was generated right after a scheduled post on Heropost failed to upload. We are just an end user of Heropost and we are not the developer. We were suggested to raised this to the attention of the community.
#heropost #problemsseen8yearsago #hopingthatthiscanbefound

How to handle errors in PayPal smart button?

enter image description hereI want to handle the errors which Paypal returns when payment failed while using Paypal smart button. Here, I am using 'actions.order.authorize' method to make payment authorization. In this scenario, If I get payment failed or any payment errors I have to handle that, So I want to receive the error response as JSON object type. But I am not getting the error in JSON type. I need the error details like debug_id, description, links in JSON type to proceed with the error handling process from our app. Here is the error returns as callback Click to view image
There is some documentation here, though not much about handling errors on the client-side: https://developer.paypal.com/docs/checkout/integration-features/auth-capture/#integrate-authorize-capture
You can see if the "authorization" object has those error details, otherwise maybe the onError function will be called with them

Google Bigquery Backend Error with streaming inserts but not display in console

I am getting following error from Google bigquer while doing streaming inserts:
Error message Signet::AuthorizationError: Unexpected status code: 500. Server message: { "error": "internal_failure" }
I can understand that there can few errors but the same doesn't get reflected on console as shown below:
As you can see in above, image, there are no 500 errors but yet in real there were 10 500 internal_failure errors.
Can you tell me why these errors don't refect on console & how do I ensure they don't happen?
This looks like a failiure to get your authentication token. This failure would occur before the client code even attempts to call the bigquery api, so the console you are looking at is accurately representing traffic.
I suspect it is a failure on a request to https://accounts.google.com/o/oauth2/token. Perhaps monitoring on outgoing http requests could verify this? (For example, see Getting error 500 when trying to obtain access token from authorization code and Internal_failure while getting refreshtoken using code?)
Back to the BigQuery API: when it returns an http error code 500, the error string will be one of "backendError" or "internalError". (For the curious: "backendError" is usually retriable, while "internalError" is likely a permanent failure.)

Fusion table api migration

I am using fusion table APIs to insert/update data in my table. Last week I migrated my API to new version v1 as referred in this sample. But now, when I run the code, the following error displayed.
400 Bad Request
{
"error" : "unauthorized_client"
}
com.google.api.client.auth.oauth2.TokenResponseException: 400 Bad Request
{
"error" : "unauthorized_client"
}
at com.google.api.client.auth.oauth2.TokenResponseException.from(TokenResponseException.java:105)
at com.google.api.client.auth.oauth2.TokenRequest.executeUnparsed(TokenRequest.java:303)
at com.google.api.client.auth.oauth2.TokenRequest.execute(TokenRequest.java:323)
at com.google.api.client.auth.oauth2.Credential.executeRefreshToken(Credential.java:607)
at com.google.api.client.auth.oauth2.Credential.refreshToken(Credential.java:526)
at com.google.api.client.auth.oauth2.Credential.intercept(Credential.java:287)
at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:836)
at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:412)
at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:345)
at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.execute(AbstractGoogleClientRequest.java:463)
at com.prasanna.survey.pushapis.FusionPush.insertData(FusionPush.java:198)
at com.prasanna.survey.pushapis.FusionPush.main(FusionPush.java:96)
Java Result: 1
How to debug this error?
This error typically occurs if you change the client_id of an application.
The reason is, you already have an access token for the Fusion API that's based on the old client_id. When you request a refresh token (as you can see is happening in the stack trace) with the new client_id, you get that very unhelpful error message.
The easiest way to handle this is to clear the existing credential from the system so it has to receive a clean access token. You can do this programatically with the Google API Java Client, or you can just remove the file from your system. On my Ubuntu machine, it is located at ~/.credentials/<api-name>.json.