Search Overlay

Google Pay

Paysafe checkout allows customers to make payments using mobile-based payment methods such as Google Pay, which rely on card payments through the Paysafe Payments API.

Google Pay offers customers a seamless and secure payment experience, allowing them to pay with their preferred payment method. By integrating Google Pay through the Paysafe Payments API, you can offer a fast, secure, and easy payment option to your customers.

Customers add payment cards to a Google Pay wallet, and the wallet securely stores the card information. When making a purchase, the customer selects Google Pay as their payment method and pays using a saved card, removing the need to repeatedly enter card details for each transaction. 

Why use Google Pay with Paysafe Checkout

  • Seamless Experience: Let customers pay with their saved cards in Google Pay - no need to re-enter card details.

  • Secure Transactions: Utilizes tokenization to protect sensitive data during the payment flow. 

  • 3D Secure Support: Automatically handles scenarios requiring 3D Secure authentication.

  • Broad Currency Support: Google Pay is supported in many regions and currencies.

Supported Regions and Currencies

Regions Supported Currencies
North America SRD, MXN, NIO, BZD, CAD, USD
Europe CHF, SEK, NOK, RSD, RUB, RON, PLN, GBP, EUR, NOK, BGN, HRK, CZK, DKK
Africa YER, MAD, VUV, UZS, UYU, TZS, TND, SOS, SCR, SAR, RWF, NGN, NAD, MWK, MZN, MNT, LRD, AFN, DZD, BWP, XOF, BIF, CVE, KHR, XAF, CLP, XOF, GMD, GHS, GNF, XOF, GYD, HTG, HNL
Asia VND, UZS, AED, UAH, TRY, THB, TJS, TWD, KZT, KRW, KWD, BHD, ILS, INR, JPY, HKD, HUF, INR
Oceania AUD, NZD
South America BRL, BND, ARS, PYG, PAB
Central America CRC, GTQ, HNL

Key Benefits

  • PCI SAQ-A compliance. 

  • Quick and simple integration.

  • Support for payments and refunds. 

  • Compatible across modern devices and browsers. 

Supported Transaction Types

  • Payments
  • Refunds

Device Compatibility

Example Payment Form

<html>

<head>
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=0" />
<script src="https://hosted.test.paysafe.com/checkout/v2/paysafe.checkout.min.js"> </script>
</head>

<body style="width :'100%'">
<button onclick="checkout()"> Pay $25 </button>
</body>
<script>
function checkout() {
paysafe.checkout.setup("c3V0LTM0ODg2MDpCLXFhMi0wLTVkM2VjYjMwLTEtMzAyYzAyMTQyYTM3NjgxMmE2YzJhYzRlNmQxMjI4NTYwNGMwNDAwNGU2NWI1YzI4MDIxNDU1N2EyNGFiNTcxZTJhOWU2MDVlNWQzMjk3MjZjMmIzZWNjNjJkNWY=", {
currency: "USD",
amount: 2500,
locale: "en_US",
amountoptions: [500, 10000, 60000],
simulator: "EXTERNAL",
merchantRefNum: "193767720k213012",
canEditAmount: true,
billingAddress: {
street: "222333 Peachtree Place",
city: "Atlanta",
zip: "30318",
country: "US",
state: "GA"
},
environment: "TEST",
merchantDescriptor: {
dynamicDescriptor: "Paysafe test",
phone: "9505610677"
},
customer: {
firstName: "John",
lastName: "Smith",
email: "paysafe.user@paysafe.com",
phone: "3069443197",
dateOfBirth: {
day: 28,
month: 2,
year: 1975
}
},
displayPaymentMethods: [
'googlePay',
],
paymentMethodDetails: {
googlePay: {
accounts: {
CC: 100261480,
},
type: 'buy',
color: 'black',
requiredBillingContactFields: ['email'],
requiredShippingContactFields: ['name'],
merchantId: '012345678912345678',
label: 'My Company',
country: 'US'
}
}
},
function (instance, error, result) {
if (result && result.paymentHandleToken) {
console.log(result);
// make AJAX call to Payments API
// alert(result.paymentHandleToken + " - token to be used to make server to server call to Payments API");
instance.showSuccessScreen("Your goods are now purchased. Expect them to be delivered in next 5 business days.");
} else {
console.error(error);
// Handle the error
}
},
function (stage, expired) {
switch (stage) {
case "BeforePayment": // Handle the scenario
break;
case "DuringPayment": // Handle the scenario
break;
case "AfterPayment": // Handle the scenario
break;
default: // Handle the scenario
}
});
}
</script>

</html>

Testing Google Pay integration

To test in Sandbox, follow these steps:

  1. Enable Google Pay
    Ensure Google Pay is enabled for your test account and integrated into your Checkout SDK setup.

  2. Use a Dummy Merchant ID
    In Sandbox, you can use a dummy merchantId consisting of 12–40 numeric characters.
    Example: 012345678987654321

Setup Function and Object

Parameter Required Type Description
paymentMethodDetails true object Required if you are offering this payment method.

displayPaymentMethods

Optional array

Determines which available payment methods are displayed to the customer. The array values are displayed in the order in which they are passed.

Case-sensitive.

Sample values (varies with currency):

displayPaymentMethods:[ "googlePay", "applePay", "card", "mazooma", "skrill", "PaysafeCard", "neteller", "paysafecash", "instantach", "sightline", "vippreferred", "paypal"],

If this parameter is not included, all payment methods available to the customer are displayed.

paymentMethodDetails object
googlePay true object Required if you are offering this payment method.
googlePay object

accounts

conditional string Required if there are multiple Google Pay accounts with the same currency.
type false string

The text that will appear on the Google Pay button.

Supported values:

  • book
  • buy
  • checkout
  • donate
  • order
  • pay
  • plain
  • subscribe

The default value is pay. See Google Pay's guidelines.

merchantId true

string

length <= 40 chars

This is the numeric merchant domain identifier registered with Google Pay, which you must obtain from the Google Pay business portal.

label true string Displayed on the payment sheet.
color false string

The color of the Google Pay button. 

Supported values:

  • white
  • black

The default value is black. See Google Pay's brand guidelines.

requiredBillingContactFields false array

The customer must provide specific billing information fields to process the transaction. The cardholder’s name is included with the requested data and is passed as the holderName value, which is mandatory for 3DS authentication. If you are using 3DS 2.0, you must also request postalAddress to capture the State parameter, as this is required for 3DS authentication.

Supported values:

  • email
  • phone
  • postalAddress
requiredShippingContactFields false array

The fields of shipping information that the customer must provide to fulfill the order.

Supported values:

  • email
  • phone
country true string The two-uppercase-character ISO 3166 country code of the merchant’s country of settlement. 
accounts object

CC

true (conditional) string

The account number for which the payment handle will be created.

Required if there are multiple Google Pay accounts with the same currency.

AMEX

false string Additional account number for AMEX card payments.

For the complete list of parameter definitions, see Setup Function.

Support

For business portal access or integration questions: