Facebook 积分偶尔无法调用带有“已解决”的回调 URL地位
这种情况似乎很少发生,在大多数情况下,我们的 FB 积分回调似乎工作正常,但时不时我们会收到订单的“已放置”回调,但从未收到“已结算”回调。从用户的角度来看,他们点击了确认按钮,积分从他们的帐户中删除,然后没有产品被交付,通常会导致我们收到愤怒的投诉。当我们调查时,我们在 FB 回调服务器上没有发现任何错误,并且可以看到初始的“已放置”消息传入,但从未看到“已解决”消息,并且由于我们仅通过 FB 的“已解决”消息交付产品,因此该产品是从未给予。
这种情况似乎很少发生,并且至少在一个报告的案例中,用户表示他们必须购买更多 FB 积分才能完成交易。发生这种情况时,状态是否会出现一些差异?在这种情况下,Facebook 不会立即扣押资金吗?还有其他人看到这种情况发生吗?
This seems to happen pretty infrequently, for the most part our FB credits callback seems to work fine, but every so often we'll get a "placed" callback for an order, but never a "settled". From the user's perspective, they hit the confirm button and the credits are removed from their account, and then no product is delivered, usually leading to us getting an angry complaint. When we investigate, we find no errors on our FB callback server, and can see the initial "placed" message coming in, but never the "settled", and since we only deliver product on a "settled" from FB, the product is never given.
This seems to happen very rarely, and in at least one reported case the user says that they had to buy more FB credits in order to complete the transaction.. is there some difference in status that occurs when this happens? Does Facebook not capture the funds right away in this case? Has anyone else seen this happen?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
事实上,“已解决”状态已被弃用,您需要将产品归因于“已放置”回调。
来源:http://developers.facebook.com/blog/post/598/
In fact the "settled" status was deprecated, you need to attribute the product on the "placed" callback.
Source: http://developers.facebook.com/blog/post/598/
我建议检查您的服务器日志以查看 Facebook 是否正在调用您的服务器,但您的代码可能已异常并且无法处理请求。如果您的服务器日志没有显示该呼叫者的呼叫,但显示其他人的呼叫,那么您可能需要联系 Facebook 并记录错误。
I'd suggest checking your server logs to see if Facebook is calling your server, but your code might have exceptioned out and not process the request. If your server logs don't show the call coming in for the one, but shows others coming in, then you may want to contact Facebook and log a bug.