Productive Merchant Approval - Google Pay

How to pass the Google Pay review for your integration with Ecart Pay. The guide documents the rules that Google applies when approving new merchants, the validations, and the technical adjustments required for integration after approval.

Table of Contents


❓ Why This Guide Exists

When you integrate Google Pay through Ecart Pay, Ecart Pay is the registered Payment Service Provider (PSP) with Google. The gateway ecartpay is already approved to process Google Pay transactions in production on behalf of every merchant using the Ecart Pay SDK.

That means, in most cases, you do not need to register your business or obtain your own merchantId in the Google Pay & Wallet Console to start accepting payments. Ecart Pay's gateway registration already covers you.

However, you may want to complete your own productive merchant approval in the following cases:

  • You want your own business name to appear on the Google Pay payment sheet (instead of the Ecart Pay default).
  • You process Google Pay across more than 50 domains.
  • Your business or platform requires its own merchantId for compliance or reporting reasons.

This guide contains the tips and steps to maximize the likelihood of getting your merchant approved when you choose to register your own profile.


🔑 Do You Need Your Own Merchant ID?

ScenarioOwn merchantId required?
Standard checkout using the Ecart Pay SDKNo — Ecart Pay's PSP registration covers you
You want your own business name on the payment sheetYes (optional)
You process Google Pay on more than 50 domainsYes
Compliance/reporting requires a dedicated merchantIdYes

Note: If none of the optional scenarios apply to you, you can skip this guide entirely. Just follow the Google Pay Integration Guide and start accepting payments — no Google Console registration required.


📇 Section 1 · Create Your Business Profile

1.1 Profile Tips

Before creating anything in the Google Console, validate that your profile meets the following criteria. Although these are not strict Google rules, they increase the likelihood of approval:

#Tip✅ Correct❌ Rejected
1Business name without forbidden wordsBruma Digital, Café Aurora, Librería VolanteMyShop_Test, Demo Store, Internal Payments, Sandbox Merchant, QA_Merchant_v2
2Domain-consistent business nameBruma Digital → brumadigital.mx; Café Aurora → cafeaurora.mxBruma Digital → mystore.com; Café Aurora → test-domain.net
3Valid HTTPS sitePublicly accessible websitePure HTTP, expired certificate, broken redirects
4Website represents a real businessHomepage with visible products, prices, and contact infoLanding "coming soon", blank page, "under construction"

1.2 Step by Step in the Google Pay & Wallet Console

  1. Go to https://pay.google.com/business/console.
  2. Sign in with the Google account for the business.
  3. Select Add merchant → choose your country (e.g., Mexico) and your type of business.
  4. Fill in the following fields with data consistent with your site:
Google Console fieldExpected valueExample
Business nameReal business nameBruma Digital
Merchant Category Code (MCC)Line of business5192
Corporate websiteMust match your sitebrumadigital.mx
Customer support URLYour site's support pagebrumadigital.mx/soporte
Customer support phonePhone number+52 55 4421 7345
  1. Submit to create the merchant. This creates a merchant profile you can use during the initial integration to create test charges.

Approval of the Business Profile takes a few minutes, so at the end of the process you should see a banner with the label Approved.


🚀 Section 2 · Request Productive Approval

To request production approval, you need the following elements:

  • The domain of your site.
  • The integration type — for Ecart Pay, choose Gateway.
  • Screenshots of your site's purchase flow.

Integration type: Ecart Pay integrates with Google Pay using the PAYMENT_GATEWAY tokenization type. When the console asks for your integration type, select Gateway and, if requested, use the gateway ID ecartpay.

2.1 Screenshots of the Purchase Flow

The Google Pay & Wallet Console requests a set of images that validate the integrity of your site and confirm you meet Google's brand criteria.

#ScreenshotWhen to capture itNotes
1Item selectionWhile the user is browsing an item or serviceHomepage with catalog or a listing with visible products
2Pre-purchase screenWhen the user is ready to make the purchaseCheckout page with order summary (amount, item, customer data) before selecting a payment method
3Payment method screenWhen the user selects Google Pay as a methodPage where the payment options (card, Google Pay, etc.) are visible and Google Pay is clearly available
4Google Pay API payment screenWhen the user sees the payment info saved in Google PayThe Google Pay sheet opened with Wallet cards. Google warns: Android does not allow screenshots of this sheet, so on mobile, take a picture of the screen with another device. On Chrome desktop you can take a normal screenshot.
5Post-purchase screenWhen the user has successfully completed the purchaseConfirmation page with a visible order ID, amount paid, and a success indicator

Reminder: To reach this step you must already have the Google Pay button integrated on your domain/app. If you have questions, review the Google Pay Integration Guide.

Once you have uploaded the required documentation, request access to production. This process takes 3–7 business days.

2.2 If You Are Rejected

Although the reason for the rejection is not always specified, the most common ones are:

Reason for rejectionWhat it meansFix
"Business Name inappropriate"Tip 1 (forbidden word)Change the business name — but be careful, see Section 3
"Business Website incomplete"Site with insufficient or missing legal contentComplete the site before retrying
"Domain mismatch"Business Website and submitted web domain do not matchAlign them
"Business Type unclear"The chosen category does not match what the site showsAdjust the category or clarify

🛠️ Section 3 · After Approval: Technical Settings

When the "Approved" email arrives with your productive merchantId (format BCR2DN...), you only need to make a couple of small adjustments to your Ecart Pay integration.

Key difference vs. a direct integration: Because Ecart Pay is your PSP, you do not manage tokenization keys, environment flags, or decryption yourself. You simply hand your merchantId to Ecart Pay and switch to the production SDK.

3.1 Send Your Merchant ID to Ecart Pay

Provide your productive merchantId to Ecart Pay support so it can be configured for your account. Once configured, the SDK automatically injects it into the Google Pay merchantInfo object in production.

You do not need to edit any tokenization or gateway code. For reference, this is the object the SDK builds internally once your merchantId is set:

{
  "merchantInfo": {
    "merchantId": "BCR2DN...",
    "merchantName": "Bruma Digital"
  }
}

Optionally, you can override the display name shown on the payment sheet directly from the SDK using the merchantName parameter (drop any "Test" suffix now that you are in production):

Pay.GooglePay.render({
  container: '#google-pay-button',
  orderId: 'YOUR_ORDER_ID',
  amount: 100.00,
  currency: 'MXN',
  countryCode: 'MX',
  merchantName: 'Bruma Digital', // your production business name
});

Note: The merchantId itself is configured on the Ecart Pay side, not in your frontend code. The SDK only attaches it to the payment sheet when the environment is PRODUCTION.

3.2 Switch to the Production SDK

The Google Pay environment (TEST vs. PRODUCTION) is controlled by which SDK script you load — you never instantiate PaymentsClient yourself. Switch from the sandbox script to the production script:

<!-- Before (testing) -->
<script src="https://sandbox.ecartpay.com/sdk/pay.js"></script>

<!-- After (production) -->
<script src="https://ecartpay.com/sdk/pay.js"></script>

The production SDK automatically sets the Google Pay environment to PRODUCTION:

// Handled internally by the Ecart Pay SDK — no action required
new google.payments.api.PaymentsClient({
  environment: 'PRODUCTION', // was 'TEST'
});

You're ready to process productive payments with Google Pay! 🎉


🔎 Resources

Google Pay Documentation

ResourceLink
Google Pay & Wallet Consolepay.google.com/business/console
Web Integration ChecklistIntegration Checklist
Web Brand GuidelinesBrand Guidelines
Acceptable Use PolicyAUP
Terms of ServiceToS

Ecart Pay Documentation

ResourceLink
Google Pay Integration GuideGoogle Pay Integration Guide
Apple Pay Integration GuideApple Pay Integration Guide
SDK JS Documentationdocs.ecartpay.com/docs/sdks
Orders APIdocs.ecartpay.com/docs/orders

Google Pay is a trademark of Google LLC.


Did this page help you?