AI-generated Key Takeaways
-
Pass constraints can be set to control screenshot eligibility and NFC behavior.
-
screenshotEligibility
determines if screenshots of the pass are allowed on Android devices, with options for eligible or ineligible. -
nfcConstraint
allows restrictions on NFC interactions when the pass is open, such as blocking payments or closed-loop transit cards. -
The default behavior for screenshots is eligible, and there are no NFC constraints by default.
Container for any constraints that may be placed on passes.
JSON representation |
---|
{ "screenshotEligibility": enum ( |
Fields | |
---|---|
screenshotEligibility |
The screenshot eligibility for the pass. |
nfcConstraint[] |
The NFC constraints for the pass. |
ScreenshotEligibility
Defines if/how screenshots may be taken of a pass.
Enums | |
---|---|
SCREENSHOT_ELIGIBILITY_UNSPECIFIED |
Default value, same as ELIGIBLE. |
ELIGIBLE |
Default behavior for all existing Passes if ScreenshotEligibility is not set. Allows screenshots to be taken on Android devices. |
INELIGIBLE |
Disallows screenshots to be taken on Android devices. Note that older versions of Wallet may still allow screenshots to be taken. |
NfcConstraint
Defines possible NFC constraints for the pass.
Enums | |
---|---|
NFC_CONSTRAINT_UNSPECIFIED |
Default value, no specified constraint. |
BLOCK_PAYMENT |
Payment cards will not be conveyed while the pass is open. |
BLOCK_CLOSED_LOOP_TRANSIT |
Closed loop transit cards will not be conveyed while the pass is open. |