Seller Data For Orders Cancelled By Google

[Brian]

Is there any way to retrieve the seller data that is set inside the JWT that's sent to Google for orders that are cancelled by Google?  Since orders cancelled by Google never reach the postback stage, there's no way for us to associate orders cancelled by Google with accounts in our database.

[Brian]

As an alternative, I took a look at the Javascript failureHandler callback as a possible way to link cancelled orders (due to fraud or otherwise) with accounts in our database, but the data sent to the callback doesn't have any such information.

Is there really no way to associate cancelled orders with accounts in our database?  I mean let's say we get several orders that were flagged for fraud and we want to subsequently lock that user's account to prevent further fraudulent purchase attempts?

[Mihai Ionescu [Google]]

Hi Brian,

Unlike incomplete transactions (i.e. user has decided to not go through with the transaction), cancelled or fraudulent orders still appear in the Merchant Center. One way to identify fraudulent accounts on your system is to try to match your data with the Merchant Center data for fraudulent transactions.

Probably the best option is to add a unique order ID to the description field in the JWT. This will appear in the Merchant Center order description as well and will allow you to uniquely identify the user.

Thanks,

Mihai

[Brian]

Mihai,

Isn't that exactly what the seller data field is supposed to be used for though?

I'd prefer not to have any of our plumbing (like unique order ID from our database) exposed to the user.  Putting our unique ID in the description might confuse the user because they'll see the Google order number and ours.  Also that means that every order would have a distinct description.  I don't know if that is not ideal at this point, but it just doesn't seem natural.

You suggestion should work, but it just seem ideal.  However, if seller data is never going to be exposed on the merchant center, then I guess I have no other choice.

[Brian]

Sorry, meant to say it seems like this would *not* be ideal.

[Ed Chavez]

I think the reason Mihai suggested using the description field is so that you do see (visually) something for you to identify (cross reference - visually)

The seller data field isn't visible - to anyone as far as I can tell (neither in Buyer or Seller view of order).....until an API for that (order inbox) comes up, perhaps some unique id on your end that doesn't get "matched" (because no postback) would work?

[Brian]

Correct, I understand where Mihai was going with his suggestion.  I believe it's something that would solve the problem but it seems hacky to me.  If there's no other solution then I'll just have to live with it.