AI-generated Key Takeaways
-
This documentation details the JSON representation and fields for handling insufficient funds errors in payment integrations.
-
It outlines how integrators can provide Google with raw result data for analysis and risk assessment.
-
The
currentBalance
field enables displaying the user's available balance in messaging, whileremedyMethod
suggests actions like topping up funds to address the issue. -
RemedyMethod
provides guidance for insufficient funds, suggesting a top-up action if the account lacks sufficient balance for a transfer.
This account does not have sufficient funds to guarantee this capture.
JSON representation |
---|
{ "rawResult": { object ( |
Fields | |
---|---|
rawResult |
OPTIONAL: Raw result of this event. Used to help inform Google's risk engine and analytics. In decline code–mapping situations, data is sometimes lost. The integrator can choose to give Google a raw code. For example, a credit card gateway (the integrator) may use this field to communicate to Google the exact decline code that was received from the VISA network. In that case, the |
currentBalance |
OPTIONAL: This is the current available balance for the account. If provided, this value will be included in user-facing messaging. |
remedyMethod |
OPTIONAL: This is the remedy method to be applied for the user to help with the insufficient funds issue. |
RemedyMethod
Remedy method for InsufficientFunds
.
JSON representation |
---|
{ // Union field |
Fields | |
---|---|
Union field remedy_method . REQUIRED: Oneof remedy method for InsufficientFunds . remedy_method can be only one of the following: |
|
topUp |
This account does not have sufficient funds to guarantee this transfer. The user should be recommended to top-up. |