Trouble finishing transaction in Google digital wallet.
I recieve the first screen from Google wallet.
When I press "Buy" on this screen.
I then get
"
Uh oh. There was a problem.
We couldn't complete your purchase because of a technical issue.
Details of the problem below:
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.
130110 11:54:15-0500 F5HORI"
I have a posturl set up in my account, and the url is implemented on my server(i've used your java example) according to my server logs and diagnostics, the postback url is not getting called.
There is no auth on my server, the postback is running on port 8080.
Related
We've setup our app to receive webhook calls from Instagram when a user visits our conversation on Instagram Direct using ig.me link. We insert referral codes in ig.me links so we know where the user comes from (e.g. https://ig.me/m/testpagename?ref=website).
The problem we're facing is that IG is not calling the webhook for messaging_referral event, although we're subscribed to that event.
When we test the subscription on the dashboard, we do get the data, but in production, nothing comes in. Our app is live and the rest of it is working perfectly.
**Important note: the referral webhook is working perfectly for FB Messenger. It's only IG direct that is not working.
**
We raised this to Meta developer support, but no response!
Any thought please?
After some other issues we managed to go live with the PayPal REST integration. Sandbox works fine, by the way, so we assume that the code is o.k.
Well this is what happened on live System:
My first customer initiated her first payment via paypal.
The payment request shows as successfully executed on the Paypal Dashboard. No error!
But the customer always got the message that something is wrong with their creditcard.
According to Paypal customer support the credit Card is fine (and the customer successfully made other payments using the same credit Card with Paypal) but that somthing must be wrong with the payment request.
But as mentioned above I cannot see an error in the dashboard nor in the logfile.
Paypal Tech Support is not responding (since over a week), so maybe somebody here has seen this before and can advise?
Thanks a lot
Christoph
Even though I am using my buyer test account, when I run the paypal.billingAgreement.create, I am redirected to a page that states:
"This transaction has expired. Please return to the recipient's website to complete your transaction using their regular checkout flow."
My logs show no exceptions (partially shown below):
Billing Plan state changed to CREATED
For approving subscription via Paypal, first redirect user to: https://www.sandbox.paypal.com/cgi-bin/webscr?cmd=_express-checkout&token=EC-7TT13145TK360674X
Payment token is: EC-7TT13145TK360674X
Sequence of my code is:
paypal.billingPlan.create
paypal.billingPlan.update
paypal.billingAgreement.create
Does anyone know why this could be happening?
Thanks in advance.
I had this problem when using Cloud9 online IDE.
My best guess is that C9 is rotating IP addresses for each call, and PayPal is validating not only on the token but also the IP Address.
I am growing frustrated with the lack of features and poor documentation of the Google Wallet for digital goods subscription API.
My question is the following:
If Google wallet sends a postback to my URL, and I do not acknowledge the payment (send status 200), does the payment get refunded or not appear on the card statement in the first place?
It seems rather strange that there is no way to programmatically cancel subscriptions. A work around would be to manage subscriptions on my end and only accept the postback payment if their subscription is valid. This would of course be frustrating to a user if they canceled a subscription, yet they still see a charge to their card and then a refund. I would like to avoid that.
Thanks in advance again everyone.
I'm not a Googler so this is subject to being crucified :)
To get an official response, it would be best to contact Google directly - you should see a "HELP -> Contact Us" in your Wallet Merchant Center.
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.
REF: Official documentation on handling postbacks
This somehow/probably relates to the old question in credit card processing of the difference between an AUTHorization and an CHARGE (aka "capture").
An AUTH for x amount would need to be sent for processing. Otherwise, how would Google send you a positive result for the transaction (aka Google would send you a postback after such successful "Auth" transaction for x amount - re: does account have enough funds to cover x)?
So there would be a "pending AUTH" for x value on card holders' account, subject to "capture" (finalizing, turning that AUTH into a CHARGE) at some later time (perhaps after you successfully acknowledge the postback).
What Google does (e.g. "Void" or "never capture") to that pending AUTH if you don't acknowledge (aka "...transaction will be cancelled"), or whether or not the above scenario is actually what occurs in Wallet for Digital Goods, can only be answered by Google. The above is only a personal (mine and mine alone) insight to standard credit card processing...
Hth....
I am new to integrate Google Wallet and there are some confusion and questions related to that given below:
Is it possible to add multiple items for Google wallet?
How to handle discount by API?
What's the parameter in JWT response on postback URL for success and failure transaction?
Is refund functionality available for a transaction by API call?
Anyone have idea about this. Thanks in advance.
Can you clarify which specific API (Instant Buy or Wallet for Digital)?
Is it possible to add multiple items...
Digital - no, you can however "bundle", see this post for clarification.
Instant Buy - it's just a "layer" on top of your (pre) existing purchase/ordering processes and handles (just) the payment data of a Google Wallet user. The "order details" is something you control. See sample of data you send.
Discounts by API
By API - no. You can pass whatever (pre-calculated) value in both APIs.
Success vs. Failure Postback
Digital - Google will only send HTTP Post to your server URL on successful transaction. See #5: "Google sends an HTTP POST message to the postback URL whenever a purchase completes..."
Instant Buy - not relevant. You are processing the transaction, unlike in Digital where Google is. Instant Buy in a nutshell provides your web site, secure access to a Google Wallet user's data. You need to have your own merchant account/processor, be PCI compliant, etc. That said, you will have the success or failure info that you actually have to send to Google - they need to know if you have successfully processed or not (yup, it's the other way around).
Refund by API
By API - Unless a Googler says otherwise, AFAIK, not at this time, for both APIs.
On that note, for Instant Buy, it's actually unclear to me how to "inform Google" when performing a credit or refund. Its still a "private API" (not GA) so I actually haven't seen its "guts". It's understood that since the merchant uses their own processor that a credit/refund is the same procedure, but letting Google "know" about it (days/weeks after the fact) is something I personally have no actual info on..sorry...I can assume some "button" in merchant center for Instant Buy, but that's just a guess....
Hth....
W.r.t InstantBuy Refunds:
The Refund happens on the virtual one time card that is returned by the Google API. The refund on the card can be done by using any backend payment processor. Once the refund is made to the card, it hits the user's backing card.