AI-generated Key Takeaways
-
The
chargebackReversedNotification
API notifies Google that a chargeback is being reversed, signifying Google won the dispute. -
Integrators send a POST request to the endpoint with details about the reversed chargeback, including the amount and a unique identifier.
-
Google responds with an
EchoResponse
for successful requests or anErrorResponse
for errors. -
The request body includes fields like
requestHeader
,paymentIntegratorAccountId
,chargebackRequestId
,amount
,rawResult
, andchargebackReversalDate
. -
The response body contains a
responseHeader
and aresult
field indicating the outcome of the notification.
- HTTP request
- Request body
- Response body
- ChargebackReversedNotificationResponse
- ChargebackReversedNotificationResultCode
Notifies Google that a chargeback is being reversed.
This signifies the reversal of a chargeback. This means Google won the dispute and the funds taken with the chargeback can be represented to Google. If this was the first chargeback for a transaction the user or issuer may request a second chargeback with new or additional information.
If the endpoint encounters an error while processing the request, the endpoint will return HTTP 4xx or 5xx and the HTTP body will either be of type ErrorResponse
or contain a generic error (e.g. a message similar to "There was an error. Please try again later.").
The generic error is used in situations where an ErrorResponse
with a clear description could be used to help an attacker understand the payment integrator account identifier of other integrators. In these situations, where either the signing key doesn't match, the payment integrator identifier was not found, or the encryption key was unknown, this method will return a generic error. If the request signature could be verified, additional information regarding the error will be returned in an ErrorResponse
.
An example request looks like:
{
"requestHeader": {
"protocolVersion": {
"major": 1,
"minor": 0,
"revision": 0
},
"requestId": "8de12c67-6458-4a8a-b3d5-a10ecdbb3354",
"requestTimestamp": "1488722866000"
},
"paymentIntegratorAccountId": "SpeedyPaymentsIndia_INR",
"chargebackRequestId": "fe640ae3-d9af-4075-90a1-7b90f436b3c0",
"amount": "728000000",
"rawResult": {
"scope": "VISA",
"rawCode": "03"
},
"chargebackReversalDate": "1488585600000"
}
An example response looks like:
{
"responseHeader": {
"responseTimestamp": "1488722868230"
},
"result": "SUCCESS"
}
HTTP request
POST https://vgw.googleapis.com/gsp/e-wallets-v1/chargebackReversedNotification/:PIAID
Request body
The request body contains data with the following structure:
JSON representation |
---|
{ "requestHeader": { object (RequestHeader) }, "paymentIntegratorAccountId": string, "chargebackRequestId": string, "amount": string, "rawResult": { object (RawResult) }, "chargebackReversalDate": string } |
Fields | |
---|---|
requestHeader |
REQUIRED: Common header for all requests. |
paymentIntegratorAccountId |
REQUIRED: This is the payment integrator account identifier that identifies contractual constraints around this transaction. |
chargebackRequestId |
REQUIRED: A unique identifier for the chargeback that is being reversed. This is the |
amount |
REQUIRED: The amount being reversed, in micros of the currency unit. This must be greater than zero and less than or equal to the amount in the |
rawResult |
REQUIRED: The raw result from the network on why the chargeback is being reversed. Used for informational purposes. |
chargebackReversalDate |
REQUIRED Timestamp of the date that the chargeback was reversed. If the date is not known, then this is the date that the payment integrator received the notification for the reversal. It is represented as milliseconds since epoch. This is a date and therefore should be the first millisecond of the day in the America/Los Angeles timezone. If it is not the first millisecond of the day the date will be assumed to be the day the specified millisecond falls on in the America/Los Angeles time zone. |
Response body
This method supports multiple return types. For additional information about what 4XX or 5XX HTTP status code to return with an ErrorResponse
, consult the ErrorResponse
object and HTTP status codes documentation.
Possible response messages | |
---|---|
HTTP 200 Status | |
HTTP 4XX / 5XX Status |
|
ChargebackReversedNotificationResponse
Response object for Google hosted e-wallets-v1.chargebackReversedNotification method.
JSON representation |
---|
{
"responseHeader": {
object (ResponseHeader)
},
"result": enum ( |
Fields | |
---|---|
responseHeader |
REQUIRED: Common header for all responses. |
result |
REQUIRED: Result of this call. |
ChargebackReversedNotificationResultCode
Result codes for the chargebackReversed
method.
Enums | |
---|---|
UNKNOWN_RESULT |
Do not ever set this default value! |
SUCCESS |
Chargeback reversed notification was successfully processed. |