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
- Do You Need Your Own Merchant ID?
- Section 1 · Create Your Business Profile
- Section 2 · Request Productive Approval
- Section 3 · After Approval: Technical Settings
- Resources
❓ 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
merchantIdfor 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?
| Scenario | Own merchantId required? |
|---|---|
| Standard checkout using the Ecart Pay SDK | No — Ecart Pay's PSP registration covers you |
| You want your own business name on the payment sheet | Yes (optional) |
| You process Google Pay on more than 50 domains | Yes |
Compliance/reporting requires a dedicated merchantId | Yes |
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 |
|---|---|---|---|
| 1 | Business name without forbidden words | Bruma Digital, Café Aurora, Librería Volante | MyShop_Test, Demo Store, Internal Payments, Sandbox Merchant, QA_Merchant_v2 |
| 2 | Domain-consistent business name | Bruma Digital → brumadigital.mx; Café Aurora → cafeaurora.mx | Bruma Digital → mystore.com; Café Aurora → test-domain.net |
| 3 | Valid HTTPS site | Publicly accessible website | Pure HTTP, expired certificate, broken redirects |
| 4 | Website represents a real business | Homepage with visible products, prices, and contact info | Landing "coming soon", blank page, "under construction" |
1.2 Step by Step in the Google Pay & Wallet Console
- Go to https://pay.google.com/business/console.
- Sign in with the Google account for the business.
- Select Add merchant → choose your country (e.g., Mexico) and your type of business.
- Fill in the following fields with data consistent with your site:
| Google Console field | Expected value | Example |
|---|---|---|
| Business name | Real business name | Bruma Digital |
| Merchant Category Code (MCC) | Line of business | 5192 |
| Corporate website | Must match your site | brumadigital.mx |
| Customer support URL | Your site's support page | brumadigital.mx/soporte |
| Customer support phone | Phone number | +52 55 4421 7345 |
- 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_GATEWAYtokenization type. When the console asks for your integration type, select Gateway and, if requested, use the gateway IDecartpay.
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.
| # | Screenshot | When to capture it | Notes |
|---|---|---|---|
| 1 | Item selection | While the user is browsing an item or service | Homepage with catalog or a listing with visible products |
| 2 | Pre-purchase screen | When the user is ready to make the purchase | Checkout page with order summary (amount, item, customer data) before selecting a payment method |
| 3 | Payment method screen | When the user selects Google Pay as a method | Page where the payment options (card, Google Pay, etc.) are visible and Google Pay is clearly available |
| 4 | Google Pay API payment screen | When the user sees the payment info saved in Google Pay | The 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. |
| 5 | Post-purchase screen | When the user has successfully completed the purchase | Confirmation 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 rejection | What it means | Fix |
|---|---|---|
| "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 content | Complete the site before retrying |
| "Domain mismatch" | Business Website and submitted web domain do not match | Align them |
| "Business Type unclear" | The chosen category does not match what the site shows | Adjust 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
merchantIdto 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
merchantIditself is configured on the Ecart Pay side, not in your frontend code. The SDK only attaches it to the payment sheet when the environment isPRODUCTION.
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
| Resource | Link |
|---|---|
| Google Pay & Wallet Console | pay.google.com/business/console |
| Web Integration Checklist | Integration Checklist |
| Web Brand Guidelines | Brand Guidelines |
| Acceptable Use Policy | AUP |
| Terms of Service | ToS |
Ecart Pay Documentation
| Resource | Link |
|---|---|
| Google Pay Integration Guide | Google Pay Integration Guide |
| Apple Pay Integration Guide | Apple Pay Integration Guide |
| SDK JS Documentation | docs.ecartpay.com/docs/sdks |
| Orders API | docs.ecartpay.com/docs/orders |
Google Pay is a trademark of Google LLC.
Updated about 14 hours ago