消費型アプリ内課金の払い戻しを検知する方法について
レシート情報をサーバに保存しておき、定期的に検証サーバに問い合わせ、レスポンスの「cancellation_date」に値が入っていたら払い戻しされたと考えて問題ないでしょうか?この方法が正しい場合、検証サーバにはどれくらいの頻度でリクエストを送って問題ないでしょうか?
別の方法がある場合はご教示いただけると助かります。
Saving receipt information on the server, checking with the detection server periodically, and considering it is refunded if the cancellation date has a value. Is this correct? If this method is correct, how often should a request be sent to the server?
If there is any other method, please let me know.
If I save the refund information, inquire to validation server periodically, and if there is a value inside cancellation_date of response, can I consider it reimbursed? If this method is correct, how often can I send the request to validation server?
If you know of other methods, please tell me.
Is that correct that we should save the receipt information, inquire the server regularly, and understand the refund has occurred when the number is displayed on the “cancellation_date” in the response? If the procedure is correct, how often could we send the request?
We would be grateful if you let us know when there are the other ways for that.
Is it all right determine it have been refunded if a reply in response to the regular query to the receipt validation server, which saves the receipt information, contains the value in the field of “cancellation date?”
If this method can be applicable, what is an interval between queries for not giving the validation server unwanted operation load?
I will be grateful if you could tell me any other method if you have.
申し訳ありません。最初の"How to detect a refund of the consumable in-app purchase detection?”の文章を"How to validate a refund of the consumable in-app purchase?に差換えてください。
もう一箇所。二行目の"Is it all right determine it have been refunded"の部分を"Is it all right to determine it have been refunded"に差換えてください。