You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{// EventTicketObject"ticketHolderName": string,"ticketNumber": string,// should we generate UUIDs rather than just numbers? Might be a better idea"id": string,// issuerID.identifier, we need to pick the identifier which can just be that UUID"classId": string,// issuerID.identifier"state": "ACTIVE","barcode": {"type": "QR_CODE","value": string,// JWT"alternateText": string// chuck the name - UUID there so we can check it in the db if barcode doesn't work}}
{// EventTicketClass"eventName": "Kimberley College Prom","eventId": string,// just a UUID....?"logo": object(Image),"venue": object(EventVenue),"dateTime": object(EventDateTime),"finePrint": object(LocalizedString),// terms of sale?"id": string,// same UUID? one used in EventTicketObject"issuerName": "Kimberley College Prom 2022","locations[]": object(LatLongPoint),"reviewStatus": "draft"||"underReview"||"approved",// underReview goes to approved automatically"heroImage": object(Image),// banner}
Am now approved for Google Pay for Passes, so this can be completed. If anyone is interested in taking on this issue, let me know and I'll invite you to the Google Pay business.
Add GPay support for the QR tickets
The text was updated successfully, but these errors were encountered: