Google Pay™️

📘

Getting Started

We recommend checking out the introductory section to understand the basics of direct charge first. This guide assumes you’ve read that.

With Google Pay, Customers can make payments with cards linked to their Google accounts. They can choose from these linked cards to make one-touch payments on the modal. This payment experience elevates UX in your application.

🚧

Google Pay Acceptable Use Policy

All merchants using this payment method must adhere to the Google Pay APIs Acceptable Use Policy and accept the terms defined in the Google Pay API Terms of Service.

Prerequisites

Before starting your integration, you should:

1. Ensure that your Flutterwave account is live.
2. Register your business/app on Google Pay and Wallet Console.
3. Inform your customers whether Google Pay is available in their region. Here is a list of countries where you can use Google Pay.
4. Prompt your customers to link their cards to their Google account or confirm that they already have a linked card. Google Pay supports Visa, Mastercard, and American Express cards globally. It also supports regional cards like Discover (US 🇺🇸), Elo (Brazil 🇧🇷), Interac (Canada 🇨🇦), and Maestro (EU and Brazil).
5. Confirm that your browser supports Google Pay. You can see the full list of supported browsers here.

Payment Flow

While the customer pays with just one tap, the complexity of the payment has been abstracted from the customer. As a developer, here are the steps to follow:

1. Initiate the payment.
2. Redirect the user securely. (only redirect URLs with https TLS1.2 and above will be approved for use)
3. Complete the payment.

Step 1: Initiating the Payment

First, you'll need the customer's email. Combine that with the rest of the payment details to create the payload and send it to our charge endpoint. You'll need to specify amount, currency, fullname and a unique tx_ref. You can also pass more details, like the fullname and custom meta information. See the endpoint reference for all parameters that can be passed.

# Google Pay
curl --request POST\
   --url https://api.flutterwave.com/v3/charges?type=googlepay\
   --header'Authorization: Bearer YOUR_SECRET_KEY'\
   --header'content-type: application/json'\
   --data'{
     "amount": 100,
     "currency": "USD",
     "email": "[email protected]",
     "fullname": "Flutterwave Developers",
     "tx_ref": "BJUYU399fcd43_success_mock"
}'

Generating a payment link via standard would open a modal like this.

Step 2: Redirecting your Customers

After a successful charge, You'll get a response that looks like this:

{
   "status":"success",
   "message":"Charge initiated",
   "data":{
      "id":2615403,
      "tx_ref":"MC-TEST-1234568_success_mock",
      "flw_ref":"RQFA6549001367743",
      "device_fingerprint":"gdgdhdh738bhshsjs",
      "amount":10,
      "charged_amount":10,
      "app_fee":0.38,
      "merchant_fee":0,
      "processor_response":"Payment token retrieval has been initiated",
      "auth_model":"GOOGLEPAY_NOAUTH",
      "currency":"USD",
      "ip":"54.75.56.55",
      "narration":"Test Google Pay charge",
+     "status":"pending",
      "auth_url":"https://rave-api-v2.herokuapp.com/flwv3-pug/getpaid/api/short-url/XPtNw-WkQ",
      "payment_type":"googlepay",
      "fraud_status":"ok",
      "charge_type":"normal",
      "created_at":"2022-05-11T20:36:15.000Z",
      "account_id":20937,
      "customer":{
         "id":955307,
         "phone_number":null,
         "name":"Flutterwave Developers",
         "email":"[email protected]",
         "created_at":"2022-05-11T20:36:14.000Z"
      },
      "meta":{
         "authorization":{
            "mode":"redirect",
+           "redirect":"https://rave-api-v2.herokuapp.com/flwv3-pug/getpaid/api/short-url/XPtNw-WkQ"
         }
      }
   }
}

Let us take a closer look at the response:

• status is "successful", which means the charge was initiated successfully.
• data.status is "pending", meaning that the payment has been initiated but the payment has not yet authorized/approved by the User.
• meta.authorization contains the important details to complete the payment. The meta.authorization.redirect field has the redirect URL to complete the payment.

This redirect URL houses the Google Pay button. After redirecting your customers to the page, they should see the hosted page with the Google pay button.

On clicking the button, the Google Pay modal opens up and the customer selects their preferred card to complete the transaction.

Step 3: Completing the payment

After completing the payment, we'll send you a webhook response to your server. Here is an example webhook response:

{
	"event": "charge.completed",
	"data": {
		"id": 2615978,
		"tx_ref": "OD3fed90d2-b441-4998-8d72-fd537acd37f1098hs_success_mock",
		"flw_ref": "XIPY8364001385338",
		"device_fingerprint": "N/A",
		"amount": 1,
		"charged_amount": 1,
		"app_fee": 0.04,
		"merchant_fee": 0,
		"processor_response": "Payment token retrieval has been initiated",
		"auth_model": "GOOGLEPAY_NOAUTH",
		"currency": "USD",
		"ip": "54.194.143.237",
		"narration": "GooglePay Transaction FOR Flutterwave Developers",
		"status": "pending",
		"auth_url": "https://rave-api-v2.herokuapp.com/flwv3-pug/getpaid/api/short-url/rjNCjCm5K",
		"payment_type": "googlepay",
		"fraud_status": "ok",
		"charge_type": "normal",
		"created_at": "2022-05-19T08:17:02.000Z",
		"account_id": 718972,
		"customer": {
			"id": 955498,
			"phone_number": null,
			"name": "Anonymous customer",
			"email": "[email protected]",
			"created_at": "2022-05-19T08:17:01.000Z"
		}
	},
	"meta_data": {},
	"event.type": "GOOGLEPAY_TRANSACTION"
}

In your webhook implementation, on receipt of the hook, you must verify the payment and give value to the customer. See our guide to transaction verification for details

Testing Google Pay

You can find test credentials and mock data for your Integration tests in the testing helpers section.

Next Steps

That’s it! You’ve successfully implemented Google Pay. You can also improve your app's payment experience with

1. Google brand guide.
2. Google Pay UX best practices.