AI-generated Key Takeaways
-
This documentation details the possible results for a transfer request made using the Google Pay E-Wallets API.
-
Results can indicate success, various failure reasons (limits, insufficient funds, account issues, risk), or require token refresh/further action.
-
Each result type has a corresponding JSON representation, providing structured data about the outcome.
-
Some result types, like
TokenRefreshRequired
,PayeeProxyNotRegistered
,DeclinedByBusinessRule
, andRiskDeclined
, allow for an optionalrawResult
field for more detailed information. -
The
rawResult
field can be used by integrators to communicate specific decline codes or other data to Google for risk analysis and analytics.
Results for transfer
JSON representation |
---|
{ // Union field |
Fields | |
---|---|
Union field result . REQUIRED: The result of the transfer. result can be only one of the following: |
|
success |
Successful transfer. |
chargeExceedsTransactionLimit |
This transfer request's |
chargeExceedsDailyLimit |
This account cannot be used for transfers right now as it has exceeded its daily limits. |
chargeExceedsMonthlyLimit |
This account cannot be used for transfers right now as it has exceeded its monthly limits. |
chargeUnderLimit |
This transfer request's |
insufficientFunds |
This account does not have sufficient funds to guarantee this transfer. |
accountDoesNotSupportCurrency |
This account does not support the requested currency. |
accountClosed |
The user's account held with the integrator has been closed. Returning this value will cause the user's instrument to be closed with Google. The user will be forced to add a new instrument by going through the association flow again. |
accountClosedAccountTakenOver |
The user's account with the integrator has been closed, suspected account take over. Returning this value will cause the user's instrument to be closed with Google. The user will be forced to add a new instrument by going through the association flow again. |
accountOnHold |
The account is on hold. |
accountClosedFraud |
The user's account held with the integrator has been closed because of fraud. Returning this value will cause the user's instrument to be closed with Google. The user will be forced to add a new instrument by going through the association flow again. |
googlePaymentTokenInvalidatedByUser |
The account is active, but the GPT has been invalidated by the user on the integrator's side. Returning this value will cause the user's instrument to be closed with Google. The user will be forced to add a new instrument by going through the association flow again. |
tokenRefreshRequired |
Returning this requires the user to go through a refresh flow. |
payeeProxyNotRegistered |
The payee proxy is not registered. |
declinedByBusinessRule |
The transaction was declined due to business rule violations on the integrator's side. This is a permanent failure for this payment, but does not cause the user's instrument to be closed at Google. |
riskDeclined |
The transaction was declined due to a risk check on the integrator's side. This is a permanent failure for this payment, but does not cause the user's instrument to be closed at Google. |
TokenRefreshRequired
Returning this requires the user to go through a refresh flow.
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 |
RiskDeclined
The transaction was declined due to a risk check on the integrator's side.
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 |