I am trying to setup a Google sandbox payment system and all is fine up until Google tries to send data to my system and then comes back with the following warning message:
Unfortunately, we could not confirm your purchase with the merchant's server. Your order has been canceled. Please contact the merchant if this problem continues.
I see that Google tried to contact my server:
[22/Sep/2014:14:05:18 -0400] "POST /walletresponse/purchase HTTP/1.1" 301 657 "-" "Google-In-App-Payments; (+http://www.google.com/payments)" 20255
Looking in the chrome->console->network->preview I see the JWT token which works if manually sent to the site. Any ideas on how to debug this?
You'll need to debug server-side and check if you are responding correctly to the postback (within 10 seconds). If you send it manually, what is the response of/from your server?
Important: If you specify a postback URL, your server must respond promptly and correctly to the HTTP POST messages that Google sends for each transaction. Otherwise, the transaction will be canceled.
Responding to the postback
Your server must send a 200 OK response for each HTTP POST message that Google sends to your postback URL. To send this response, your server must:
Decode the JWT that's specified in the jwt parameter of the POST message.
Check to make sure that the order is OK.
Get the value of the JWT's "orderId" field.
Send a 200 OK response that has only one thing in the body: the "orderId" value you got in step 3.
Hth...
Googles servers came back online and now it seems to be working
Related
there was an investigation task that was assigned to me by a collegue to check if it is possible to execute HTTP Requests and handle the response in the emails that we are sending. The emails are created using Mustache.js and we have buttons which call a GET request in the BE. To my understanding there is no way to execute JS in the email client as they do not allow it. Does anyone know if it is possible to send an http request and handle the response in the email client?
I've set up a ZAP so that when a subscriber is added to my aweber email list they are automatically added to a product in my membership plugin called DAP or digital access pass.
As per the instructions of the membership plugins developers, I am using a webhook in the zapier 'post' section.
It's not working. Quite simply the webhook doesn't appear to be calling anything.
Now, weird thing is that zapier logs show the webhook has been sent and has had success. But from DAP's end nothing is being received.
The support team at DAP tell me that the script isn't being called, because nothing appears in their logs.
They show me this by putting the webhook URL into a browser and calling it that way, and THEN the relevant info arrives in the DAP logs.
Zapier told me they do not trouble shoot and so advised that I post here.
Would appreciate any help. Thank you very much.
Dan
You can easily test if Zapier is making a call or not by sending the request to http://requestb.in
Steps:
Create a request bin and copy the URL.
Request bin screenshot
In Zapier, replace the webhooks post URL with the requestb.in URL.
Now, whenever the Webhook makes a post request, you should be able to visit the inspect page of your bin and check if a request was received. Just add ?inspect to the end of the URL. For example, if your Request bin URL is https://requestb.in/wbto8jwb then you should visit https://requestb.in/wbto8jwb?inspect
The inspect page will show all the requests received.
With this, you will know if Zapier is sending the requests. If the requests are being received by request bin then there is something which needs to be fixed by DAP.
Note that it could also be something in the configuration of the Webhook that is causing the request to not be recognised by DAP. It will help if you add more details to your question - what format is the DAP team expecting to receive the data in?
Below is a sample Webhook implementation in Zapier.
I have added a hook to POST data to a request bin (https://requestb.in/wbto8jwb)
Webhook POST screenshot
When I test this step, the request is received in the Request Bin Inspect page (https://requestb.in/wbto8jwb?inspect).
Request Bin Screenshot
More reading:
https://zapier.com/help/webhooks/
Update:
You can also make a direct call to the DAP API by using a tool like https://www.hurl.it/. From the drop down in destination, select POST and put the URL here. Click on Add body and paste the raw data from request bin. Now ask the DAP team to check if the request was received.
I set the webhook of my Telegram Bot and it seems to work fine, but the bot doesn't reply when I try to write him. The code of the file I indicated as webhook is correct (I checked it with getupdates method) and the server where it's hosted has the SSL certificate.
Trying to see the result of the method getWebhookInfo I checked up that the error was "Wrong response from the webhook: 410 Gone".
Anyone could help me to find out where the problem is?
I recommend you to copy the url you received from getWebhookInfo and then POST some valid JSON to it (e.g. on linux with curl, examples here: Telegram Guide).
WRON RESPONSE FROM WEBHOOK indicates that there is a problem with your web server configuration or something elso on the way in.
"410 Gone" is returned by your webserver, so maybe your .httaccess config is wrong (if using Apachee).
I'm using the DocuSign API to POST to the Post Recipient View URL.
I receive a response URL, but if I follow the URL it tells me: ...?event=ttl_expired.
Example URL: https://demo.docusign.net/Signing/startinsession.aspx?t=66e01470-4fcb-xxxx-xxxx-2f9029036d21
I'm using the URL within seconds, so is there a reason I'm getting this error?
TTL does indeed refer to "Time to Life" so if you're getting that error and you're positive it's within the 5 minute TTL window (2 seconds sounds well inside :]) then I would guess one of three things:
You're requesting a signing URL on an invalid envelope (ie you're not the sender or do not have rights on it)
You're requesting for a recipient that is not properly embedded.
You're requesting on a completed envelope or other terminal state (like voided).
Please confirm it's not one of these 3 things causing your error.
Hi I am new to Docusign integration to salesforce. I have to change the status of envelope to "Correction" and I have gone through "POST" method provided in the Docusign RestAPI guide.
Doing so, the docusign returns a correction url to activate the correction status. As of now, I am manually pasting that url in the browser to activate correction view.
My question is, how to hit that URL to browser in background through Apex in-order to activate the correction status? (or) Is there anyway to activate correction view of envelope other than hitting URL to browser?
I have tried using HTTP get requests to run that URL . The first request will redirect to another link with status code 302 ("Found"), if i use another request on that using reponse.getHeader('Location') it is redirecting to member login page, (So i have passed another request to login which responded as Status "OK"), if i hit another request on member login page response.getheader('Location') the response of this latest request is "OK"(because i have already logged in using the previous request) and response.getHeader('Location') for this latest request is null and Status of envelope is not changed to "correction".
I know using these many requests is not at all a best practice, could anyone suggest me a perfect way to activate the correction view of envelope? I am in real need of this answer. Please help. Thanks.
The correction view is possible but you have to authenticate your web service request in order to get to it. You can't just find a URL and go to it without authentication - that would violate the security of the transaction.
You can get the correction view URL by doing a POST here
https://{server}/restapi/{apiVersion}/accounts/{accountId}/envelopes/{envelopeId}/views/correct
You would also need to provide these headers:
X-DocuSign-Authentication: <DocuSignCredentials><Username>{name}</Username><Password>{password}</Password><IntegratorKey>{integrator_key}</IntegratorKey></DocuSignCredentials>
Accept: application/json
Content-Type: application/json