AI-generated Key Takeaways
-
In redirect payments, users complete payment on a partner site and are redirected back to Google via the integrator.
-
Integrators must redirect users to the
callbackUrl
specified in the Begin Redirect request using an HTTPS GET request. -
The redirect response includes details like
redirectRequestId
,paymentIntegratorAccountId
, and an encryptedredirectResponse
parameter. -
The
redirectResponse
parameter contains information about the completed payment and is encrypted and signed using PGP or JWE+JWS before being base64url-encoded. -
Integrators must support URL lengths up to 2,048 characters, including all parameters which are UTF-8 encoded before URL-encoding.
As part of a redirect payment the user will be redirected to complete a payment in a partner's website. Once the payment is completed, the user should be redirected back to Google via the integrator. If the payment was completed on the issuer's portal, the user should be redirected to the integrator first, which in turn should redirect the user to Google.
The integrator must redirect the user to callbackUrl
, which is part of the
Begin Redirect request payload. The integrator must implement an HTTPS protocol
using GET. The GET parameters, outlined in
Redirect Response Parameters, will contain
information about the completed redirect payment.
The integrator must support URL lengths of 2,048 chars. This includes the scheme, host, port, path and parameters. All parameters will be UTF-8 encoded prior to being URL-encoded.
Redirect Response
Here's an example of the URL to which the user will be redirected as part of the Complete Redirect flow (also known as redirect response):
https://example.google.com/return/url?redirectRequestId=cmVxdWVzdDE&paymentIntegratorAccountId=InvisiRedirectPaymentUSA_USD&redirectResponse=VEhJU19JU19BTl9FTkNSWVBURURfUkVESVJFQ1RfUkVTUE9OU0VfUEFZTE9BRF9FWEFNUExFX1RIQVRfSVNfRU5DT0RFRF9XSVRIX2Jhc2U2NF9VUkwtU0FGRV9FTkNPRElORw==
The URL-decoded value of the redirectRequestId
parameter in this example is cmVxdWVzdDE
. The URL-decoded value of the paymentIntegratorAccountId
parameter in this example is InvisiRedirectPaymentUSA_USD
The redirectResponse
parameter is encrypted and signed using PGP
or JWE+JWS
before being base64url
-encoded.
Redirect Response Parameters
The HTTPS GET response must have the following query parameters:
Fields | |
---|---|
redirectRequestId
|
string
REQUIRED: The |
paymentIntegratorAccountId
|
string
REQUIRED: This is the payment integrator account identifier that identifies contractual constraints around this transaction. |
redirectResponse
|
RedirectResponse
REQUIRED: The |