WalletAvailability
Why a device-wallet button may or may not be drawn.
Deliberately four states and not a Boolean. A Boolean collapses three completely different situations — the merchant id was never provisioned, the hardware/OS cannot do wallets at all, and the user simply has no card in their wallet yet — into one "false" that the UI can only answer by hiding the button silently. Each of these wants a different response: a build-time error, nothing at all, and an "add a card" affordance respectively.
NOT_CONFIGURED is the state that exists because of the placeholder contract: while a __PROVISION_*__ sentinel is still in place the seam reports it, so the app refuses to draw a working-looking button that would fail at the exact moment money is on the line.
Entries
Device and config are fine, but the user has no card in the wallet. Offer "add a card".
This device/OS cannot present the wallet at all. Show nothing — there is no user action.
A provisioning value is still a sentinel. A developer error, never a user-facing state.
Companion properties
Returns an immutable kotlin.enums.EnumEntries list containing the constants of this enum type, in the order they're declared.
Companion functions
Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)
Returns an array containing the constants of this enum type, in the order they're declared.