Payment Reversal Notification flow
Stay organized with collections
Save and categorize content based on your preferences.
Payment reversal notifications are used to inform Google's risk engine and
the merchant that the integrator has incurred bad debt.
Typically, the integrator will represent this as a chargeback. However, Google does not accept chargebacks with this specification. That said, Google still wants
a signal to help understand how money is flowing, fraud rings are forming, etc.
In order to do that, Google provides two method calls the integrator can use
to inform us of inquiries and disputes.
The paymentInquiryNotification
method informs Google that an inquiry has started between the user and the
integrator. The
paymentDisputeNotification
method informs Google that a dispute has been finalized and a portion
or all of the original transaction has been reversed. A dispute can reference
an inquiry, or can be called independently of any inquiry.
It's critical to note that there is no monetary impact to any of the calls
above.
All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-09-03 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-09-03 UTC."],[[["\u003cp\u003ePayment reversal notifications inform Google's risk engine and the merchant of integrator bad debt, helping Google understand money flow and fraud patterns.\u003c/p\u003e\n"],["\u003cp\u003eIntegrators should use \u003ccode\u003epaymentInquiryNotification\u003c/code\u003e to signal an inquiry and \u003ccode\u003epaymentDisputeNotification\u003c/code\u003e to signal a finalized dispute with potential reversals.\u003c/p\u003e\n"],["\u003cp\u003eThese notifications have no monetary impact but serve as important signals for Google's risk assessment.\u003c/p\u003e\n"]]],["Integrators use `paymentInquiryNotification` to signal the start of an inquiry between a user and the integrator. They use `paymentDisputeNotification` to indicate that a dispute is finalized and some or all of a transaction has been reversed. These actions inform Google about money flow and potential fraud, though Google does not accept chargebacks. Importantly, neither method call involves any direct monetary impact; they serve purely informational purposes for Google's risk assessment.\n"],null,["# Payment Reversal Notification flow\n\nPayment reversal notifications are used to inform Google's risk engine and\nthe merchant that the integrator has incurred bad debt.\n\nTypically, the integrator will represent this as a chargeback. However, Google does not accept chargebacks with this specification. That said, Google still wants\na signal to help understand how money is flowing, fraud rings are forming, etc.\n\nIn order to do that, Google provides two method calls the integrator can use\nto inform us of inquiries and disputes.\n\nThe [`paymentInquiryNotification`](/standard-payments/payment-update-service-api/v1/TopLevel/paymentInquiryNotification)\nmethod informs Google that an inquiry has started between the user and the\nintegrator. The\n[`paymentDisputeNotification`](/standard-payments/payment-update-service-api/v1/TopLevel/paymentReversalNotification)\nmethod informs Google that a dispute has been finalized and a portion\nor all of the original transaction has been reversed. A dispute can reference\nan inquiry, or can be called independently of any inquiry.\n\nIt's critical to note that there is no monetary impact to any of the calls\nabove."]]