WebViews
, please note that platform specific
Android Google Pay APIs must be invoked.
Please refer to Google’s FAQ for more
information.POST /digital-wallets/google/session
API with the domain you want to host Google Pay on. This needs to be the full domain including any subdomains like www.
.
gateway
needs to be set to gr4vy
, and the value of gatewayMerchantId
needs
to be set to the value you received from our session API in the previous step.
merchantInfo
object. This authorized Gr4vy to accept Google Pay on your domain.
When setting the merchantInfo
object, make sure to set the token
returned from our session API, your merchant name, our Gr4vy merchant ID, and the full domain you passed to our session API (including any subdomains like www.
)
OR_BIBED_11
/ OR_BIBED_6
- If you were to encounter any kind of
OR_BIBED
error you likely did not pass the right domain to our API, or you
did not pass the same domain to our session API and the merchantInfo
object.onPaymentAuthorized
function
you will have a paymentData
that needs to be sent to the gateway. You can send
this object to our POST /transactions
endpoint either directly or via your server.
The payment method used needs to contain the data from the Google Pay payload.
redirect_url
, just in case any
connection is configured to use 3-D Secure. This URL will be appended with
both a transaction ID and status (e.g.
https://example.com/callback?transaction_id=123 &transaction_status=capture_succeeded
) after 3-D Secure has been completed.