playstore: custom type of refund reason - #337
Merged
Merged
Conversation
takecy
approved these changes
Jul 7, 2026
takecy
left a comment
takecy
left a comment
Member
There was a problem hiding this comment.
Thanks for the additional response!
LGTM 👍
There was a problem hiding this comment.
Pull request overview
This PR improves the Play Store RTDN model by introducing a dedicated RefundReason type for pendingRefundReviewNotification, aligning the payload structure more closely with Google’s documentation (Issue #335).
Changes:
- Added an exported
RefundReasonenum type for pending refund review notifications. - Introduced
RefundReasonChargebackconstant (value7) based on the Play RTDN reference. - Updated
PendingRefundReviewNotification.RefundReasonfromintto the newRefundReasontype.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related to Issue #335