Incluye la información relevante que pueda usarse para brindarte asistencia. La información más útil que se debe compartir es la dirección de correo electrónico del usuario afectado, el entorno, las marcas de tiempo aproximadas y una descripción detallada del error. Otros identificadores pertinentes, como los 4 últimos dígitos del número FPAN, los IDs de billetera y los IDs de referencia de token, entre otros, son útiles si están disponibles. No podemos buscar cuentas con el número FPAN o DPAN de los usuarios.
Asegúrate de NO hacer lo siguiente:
Enviar IIPS como los datos del titular de la tarjeta, el número FPAN, el CVV o la fecha de vencimiento (ni siquiera para las tarjetas de zona de pruebas o de prueba). Puedes enviar, como máximo, los primeros 8 dígitos o los últimos 4 dígitos si son pertinentes para la pregunta. No podemos buscar información con los números FPAN.
Iniciar solicitudes de asistencia enviando correos electrónicos a direcciones de Atención al cliente de Google o copiando esos alias en conversaciones
Cambiar de tema en una conversación de asistencia. En lugar de eso, envía una nueva solicitud y asegúrate de completar todos los detalles requeridos para el otro tema
Si necesitas asistencia con una API de Google Pay, como la de Push Provisioning, consulta la página de asistencia y la guía de solución de problemas específicas de esa API:
Si se te otorgó acceso a este contenido, asegúrate de ingresar con tu Cuenta de Google autorizada. Si eres un socio que necesita acceso, usa el siguiente botón para obtener instrucciones sobre cómo solicitarlo.
Todos los derechos reservados. Java es una marca comercial de Oracle o sus afiliados.
Última actualización: 2025-08-22 (UTC)
[null,null,["Última actualización: 2025-08-22 (UTC)"],[[["\u003cp\u003eTo get Google support, begin by identifying the correct channel for your specific issue and checking for existing solutions in the troubleshooting section.\u003c/p\u003e\n"],["\u003cp\u003eWhen requesting support, provide necessary details like user email, environment, timestamps, and error descriptions, excluding sensitive information like full cardholder data.\u003c/p\u003e\n"],["\u003cp\u003eFor API-related issues, consult the dedicated support resources and guides for the specific Google Pay API you are working with, like Android Push Provisioning.\u003c/p\u003e\n"],["\u003cp\u003eMarketing and branding questions regarding the Push Provisioning API have a designated support team, while other brand-related queries should be submitted through the Partner Marketing Hub contact form.\u003c/p\u003e\n"],["\u003cp\u003eAccessing certain support content may require logging in with an authorized Google account, with options available for partners to request access if needed.\u003c/p\u003e\n"]]],["When seeking Google support, route requests to the correct channel and check the troubleshooting page. Include user email, environment, timestamps, and error details; other identifiers are helpful if available. Avoid sending sensitive data like full card numbers, or using Google support email addresses. For new topics, initiate a new request. Direct Push Provisioning API branding inquiries to its support team and other marketing questions to the Partner Marketing Hub. API-specific issues should be directed to the corresponding support and troubleshooting page.\n"],null,["# Get help\n\nGetting support from Google\n---------------------------\n\nWhen seeking support **DO**:\n\n- Route your request to the [correct support channel](/pay/issuers/support/overview) for your issue.\n- Check if your issue is already covered on the [troubleshooting](/pay/issuers/support/troubleshooting) page.\n- Include relevant support information that can be used to assist you. The most useful information to share are the email address of the affected user, the environment, the approximate timestamps, and a detailed description of the error. Other relevant identifiers like the FPAN last 4, wallet IDs, token reference IDs, etc. are helpful if available. We cannot look up accounts by the users FPAN or DPAN.\n\nMake sure you **DON'T**:\n\n- Send SPII like cardholder data, FPAN, CVV, or expiry (even for sandbox or test cards). You may send at most the first 8 digits or last 4 digits if relevant to the question. We cannot look up information using FPANs.\n- Initiate support requests by emailing Google support email addresses or copying those aliases into threads.\n- Switch between topics on a support thread. Instead, file a new request and make sure to fill out all requested details for that other topic.\n\n### Marketing questions\n\nBranding questions related to the Push Provisioning API should be routed to the\n[Push Provisioning support team](#api_issues). All other marketing and branding\nquestions should be submitted through the\n[Partner Marketing Hub](https://g.co/pay/brand) contact form.\n\n### Google Pay API issues\n\nIf you need support for a Google Pay API like Push Provisioning, please\nrefer to the support page and troubleshooting guide specific to that API:\n\n- Android Push Provisioning: [troubleshooting](/pay/issuers/apis/push-provisioning/android/support/troubleshooting) and [support](/pay/issuers/apis/push-provisioning/android/support/get-help)\n\n### General questions\n\n| You must be logged in to see this section.\n\nIf you have been granted access to this content, make sure you are signed in with your\nauthorized Google account. If you are a partner who needs access, use the button below for\ninstructions on how to request access.\n[Sign in](https://accounts.google.com/AccountChooser?continue=https%3A%2F%2Fdevelopers.google.com/pay/issuers/support/get-help) [Request access](/pay/issuers/request-access)"]]