Facebook credits occasionally failing to call callback URL with "settled" status

239 Views Asked by At

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?

2

There are 2 best solutions below

0
On BEST ANSWER

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/

0
On

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.