Skip to main content

​
Using Google Pay with Revolv3

Revolv3 supports gateway-based Google Pay tokenization.
You must use: 
type: 'PAYMENT_GATEWAY'
Revolv3 does NOT support DIRECT tokenization for Google Pay.

​
Architecture Overview

Key Point:
Google encrypts the token for your processor.
Revolv3 forwards the encrypted payload.
The processor decrypts and authorizes it.

​
Prerequisites

  • Google Pay enabled on your Revolv3 merchant account
  • Processor supports Google Pay (Worldpay, Adyen, Nuvei, etc.)
  • Google Pay enabled on your processor account
  • Use PAYMENT_GATEWAY tokenization

​
Tokenization Setup (Worldpay Example)

​
Correct Configuration

const tokenizationSpecification = {
  type: 'PAYMENT_GATEWAY',
  parameters: {
    gateway: 'vantiv',  // Worldpay uses 'vantiv'
    'vantiv:merchantPayPageId': 'YOUR_PAYPAGE_ID',
    'vantiv:merchantOrderId': 'ORDER123',
    'vantiv:merchantTransactionId': 'TX123',
    'vantiv:merchantReportGroup': 'report-group'
  }
};

​
Why vantiv?

Worldpay’s Google Pay gateway identifier is: 
gateway: 'vantiv'
It is not 'worldpay'. Using the wrong gateway value will cause processor token registration failures.

​
Environment Configuration

​
TEST

environment: 'TEST',
merchantId: '01234567890123456789'
  • Google shared test merchant ID
  • Use processor TEST credentials
  • Use Revolv3 sandbox/UAT

​
PRODUCTION

environment: 'PRODUCTION',
merchantId: 'YOUR_GOOGLE_BUSINESS_CONSOLE_ID'
You must:
  • Register in Google Pay Business Console
  • Verify domain
  • Use production processor credentials
  • Use Revolv3 production API

​
Sale Request Example

Send the entire GooglePayPaymentDataResponse as a JSON string. 
{
  "IncludeRawProcessorResponse": true,
  "PaymentMethod": {
    "GooglePay": {
      "GooglePayPaymentDataResponse": "{...full Google response JSON...}"
    },
    "BillingFullName": "Joe Smith",
    "BillingAddress": {
      "AddressLine1": "381 Forest Ave",
      "City": "Laguna Beach",
      "State": "CA",
      "PostalCode": "92651",
      "Country": "US"
    }
  },
  "Invoice": {
    "MerchantInvoiceRefId": "ORDER-12345",
    "Amount": {
      "Currency": "USD",
      "Value": "12.20"
    }
  }
}
POST to: 
/api/payments/sale

​
Common Processor Error

​
”Unable to register low-value Google Pay token”

Caused by:
  • Using DIRECT instead of PAYMENT_GATEWAY
  • Wrong gateway value (must be 'vantiv' for Worldpay)
  • Wrong merchant credentials
  • Environment mismatch

​
Environment Alignment Matrix

Google PayRevolv3Processor
TESTSandbox/UATTest
PRODUCTIONProductionProduction
Mismatch will cause processor failures.

​
Script Examples

Revolv3 provides:
  • Google Pay HTML demo examples
  • Sandbox testing pages
  • Script-based examples for Worldpay (Vantiv)
  • TEST/PRODUCTION toggle examples
Contact Revolv3 Support if you need:
  • A working HTML prototype
  • Worldpay-specific script example
  • Processor credential guidance

​
Best Practices

  1. Always use PAYMENT_GATEWAY
  2. Use gateway: 'vantiv' for Worldpay
  3. Send full GooglePayPaymentDataResponse
  4. Align environments
  5. Test in sandbox before production

​
Additional Resources

  • Google Pay Web Docs — Official Google Pay API documentation
  • Contact Revolv3 Support for enablement

​
Next Steps