Design

Google Pay API for Passes boarding pass template
  1. class.logo
  2. class.eventName
  3. class.venue.name
  4. class.dateTime.start (date portion)
  5. class.dateTime.start (time portion)
  6. class.heroImage
  7. class.gateLabel / class.customGateLabel
  8. object.seatInfo.gate
  9. class.sectionLabel / class.customSectionLabel
  10. object.seatInfo.section
  11. class.rowLabel / class.customRowLabel
  12. object.seatInfo.row
  13. class.seatLabel / class.customSeatLabel
  14. object.seatInfo.seat
  15. object.barcode.type

    object.barcode.value

  16. object.barcode.alternateText
  17. class.hexBackgroundColor
  18. object.ticketHolderName
  19. class.venue.address
  20. class.dateTime.doorsOpen
  21. class.dateTime.start
  22. class.dateTime.end
  23. *.imageModulesData.mainImage
  24. object.ticketType
  25. object.ticketNumber
  26. class.confirmationCodeLabel / class.customConfirmationCodeLabel
  27. object.reservationInfo.confirmationCode
  28. object.faceValue
  29. class.finePrint
  30. *.messages[0].header
  31. *.messages[0].body
  32. *.textModulesData.header
  33. *.textModulesData.body
  34. *.infoModuleData.labelValueRows[0].columns[0].label
  35. *.infoModuleData.labelValueRows[0].columns[0].value
  36. *.linksModuleData.uris[0]
  37. *.linksModuleData.uris[1]

Priority of fields and values shown on Pass header

There are fields and values that can change the design of an event ticket Pass depending on what values are set.

Field 16 rendering logic: value under barcode image

If the object.barcode.alternateText field isn't set, field 16 doesn't render.

Envoyer des commentaires concernant…

Google Pay for Passes