Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Usar un ID de agrupación
De forma predeterminada, agregar múltiples pases a un solo
El vínculo Agregar a la Billetera de Google no agrupará esos pases en
la app de la Billetera de Google del usuario. Sin embargo, los pases se pueden agrupar haciendo
asegurarte de que todos tengan el mismo ID de agrupación. Los pases agrupados aparecerán juntos
en la app de la Billetera de Google. Cuando se selecciona un grupo de pases, cada pase
mostrarse en un carrusel.
Para agregar un pase a un grupo, la propiedad groupingInfo.groupingId de
se debe establecer el objeto pass. Todos los objetos de pase con el mismo
El valor de groupingId se agrupará automáticamente, incluso si
se agregaron por separado.
En el siguiente ejemplo, se muestran una tarjeta de lealtad y una oferta que se agrupan para
para motivar al usuario a usar ambos en su próxima compra.
A veces, las tarjetas de embarque se usan en un grupo y no de manera individual. Un problema común
En este caso, se trata de un grupo de boletos para vuelos con escalas o varios
paradas.
Las tarjetas de embarque tienen una lógica adicional que agrupará automáticamente los pases
si tienen los mismos valores para las siguientes propiedades:
FlightClass.flightHeader.carrier.carrierIataCode
FlightClass.flightHeader.flightNumber
FlightClass.localScheduledDepartureDateTime
FlightObject.reservationInfo.confirmationCode
La sección del ID de entidad emisora de FlightObject.id
Si alguna de las propiedades anteriores es diferente para dos tarjetas de embarque, se consideran
no se agrupan (a menos que lo hagas con groupingInfo). Como puedes ver, tanto la clase
y las propiedades de los objetos
afectan la agrupación automática. Esto habilita las tarjetas de embarque
de clases diferentes para agrupar (por ejemplo, cuando vuelos
en un mismo viaje tengan distintas empresas de transportes).
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Falta la información que necesito","missingTheInformationINeed","thumb-down"],["Muy complicado o demasiados pasos","tooComplicatedTooManySteps","thumb-down"],["Desactualizado","outOfDate","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Problema con las muestras o los códigos","samplesCodeIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-04 (UTC)"],[[["\u003cp\u003eMultiple passes added to a single Google Wallet link can be grouped together using the same \u003ccode\u003egroupingId\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eGrouped passes are displayed together in the Google Wallet app and can be provisioned together or grouped later via update/patch methods.\u003c/p\u003e\n"],["\u003cp\u003eBoarding passes have automatic grouping logic based on shared flight details, but using the \u003ccode\u003egroupingInfo\u003c/code\u003e property overrides this automatic grouping.\u003c/p\u003e\n"]]],["Passes in Google Wallet can be grouped by assigning them a shared `groupingId` property, ensuring they appear together in the app. This grouping can occur during the initial provisioning or via `update` or `patch` methods. Boarding passes also have automatic grouping based on properties like carrier code, flight number, departure time, and confirmation code. Setting a `groupingInfo` overrides this automatic logic. A loyalty card and offer could be grouped using the same `groupingId`.\n"],null,["# Group multiple Boarding passes\n\nUse a grouping ID\n-----------------\n\n\nBy default, adding multiple passes to a single\n**Add to Google Wallet** link will not group those passes in the\nuser's Google Wallet app. However, passes can be grouped together by making\nsure they all have the same grouping ID. Grouped passes will appear together\nin the Google Wallet app. When a group of passes is selected, each pass will\nbe shown on a carousel.\n\nPasses can be grouped together:\n\n- During initial provisioning\n- By using the [`update`](/wallet/tickets/boarding-passes/rest/v1/flightobject/update) or [`patch`](/wallet/tickets/boarding-passes/rest/v1/flightobject/patch) methods\n\n\nTo add a pass to a group, the `groupingInfo.groupingId` property of\nthe pass object must be set. All pass objects with the same\n`groupingId` value will be automatically grouped together, even if\nthey were added separately.\n\n\nThe following example shows a loyalty card and offer being grouped together to\nentice the user to make use of both in their next purchase. \n\n```carbon\nloyaltyObject = {\n \"classId\": \"ISSUER_ID.GIFT_CARD_CLASS_SUFFIX\",\n \"id\": \"ISSUER_ID.GIFT_CARD_OBJECT_SUFFIX\",\n \"state\": \"ACTIVE\",\n \"groupingInfo\": {\n # Note the same groupingId value\n \"groupingId\": \"combinedGiftCardAndOfferId\",\n \"sortIndex\": 1\n },\n \"barcode\": {\n \"type\": \"QR_CODE\",\n \"value\": \"QR code\"\n },\n \"accountId\": \"Account id\",\n \"accountName\": \"Account name\",\n \"loyaltyPoints\": {\n \"label\": \"Points\",\n \"balance\": {\n \"int\": 800\n }\n }\n}\n\nofferObject = {\n \"classId\": \"ISSUER_ID.OFFER_CLASS_SUFFIX\",\n \"id\": \"ISSUER_ID.OFFER_OBJECT_SUFFIX\",\n \"state\": \"ACTIVE\",\n \"groupingInfo\": {\n # Note the same groupingId value\n \"groupingId\": \"combinedGiftCardAndOfferId\",\n \"sortIndex\": 2\n },\n \"barcode\": {\n \"type\": \"QR_CODE\",\n \"value\": \"QR code\",\n },\n}\n```\n\nBoarding pass automatic grouping\n--------------------------------\n\n| **Note:** The `groupingInfo` property of a pass will always take precedence over the automatic grouping logic used by Boarding passes.\n\nSometimes boarding passes are used in a group rather than individually. A common\nscenario for this is grouping of tickets for flights with layovers or multiple\nstops.\n\nBoarding passes have additional logic that will automatically group passes\ntogether if they have the same values for the following properties:\n\n- `FlightClass.flightHeader.carrier.carrierIataCode`\n- `FlightClass.flightHeader.flightNumber`\n- `FlightClass.localScheduledDepartureDateTime`\n- `FlightObject.reservationInfo.confirmationCode`\n- The Issuer ID portion of `FlightObject.id`\n\nIf any of the above properties are different for two Boarding passes, they are\nnot grouped (unless you do so using `groupingInfo`). As you can see, both class\nand object properties affect automatic grouping. This enables Boarding passes\nof different classes to be grouped together (such as when different flights\nin the same trip have different operating carriers)."]]