When true, indicates that the view is an accessibility element. By default, all the touchable elements are accessible.
Provides an array of custom actions available for accessibility.
Overrides the text that's read by the screen reader when the user interacts with the element. By default, the label is constructed by traversing all the children and accumulating all the Text nodes separated by space.
Accessibility Role tells a person using either VoiceOver on iOS or TalkBack on Android the type of element that is focused on.
Accessibility State tells a person using either VoiceOver on iOS or TalkBack on Android the state of the element currently focused on.
An accessibility hint helps users understand what will happen when they perform an action on the accessibility element when that result is not obvious from the accessibility label.
Represents the current value of a component. It can be a textual description of a component's value, or for range-based components, such as sliders and progress bars, it contains range information (minimum, current, and maximum).
In some cases, we also want to alert the end user of the type of selected component (i.e., that it is a “button”). If we were using native buttons, this would work automatically. Since we are using javascript, we need to provide a bit more context for TalkBack. To do so, you must specify the ‘accessibilityComponentType’ property for any UI component. For instances, we support ‘button’, ‘radiobutton_checked’ and ‘radiobutton_unchecked’ and so on.
Indicates to accessibility services whether the user should be notified when this view changes. Works for Android API >= 19 only. See http://developer.android.com/reference/android/view/View.html#attr_android:accessibilityLiveRegion for references.
Controls how view is important for accessibility which is if it fires accessibility events and if it is reported to accessibility services that query the screen. Works for Android only. See http://developer.android.com/reference/android/R.attr.html#importantForAccessibility for references.
Possible values: 'auto' - The system determines whether the view is important for accessibility - default (recommended). 'yes' - The view is important for accessibility. 'no' - The view is not important for accessibility. 'no-hide-descendants' - The view is not important for accessibility, nor are any of its descendant views.
A Boolean value indicating whether the accessibility elements contained within this accessibility element are hidden to the screen reader.
Accessibility traits tell a person using VoiceOver what kind of element they have selected. Is this element a label? A button? A header? These questions are answered by accessibilityTraits.
A Boolean value indicating whether VoiceOver should ignore the elements within views that are siblings of the receiver.
Sets the Apple Wallet/Google Pay button style. If the button is placed over a dark background, set this to 'onDarkBackground', otherwise set to 'onLightBackground'.
The image asset to use as the Google Pay button. Downloadable from https://developers.google.com/static/pay/issuers/apis/push-provisioning/android/downloads/flutter/2022_googlepay_flutter_buttons.zip
iOS only. Set this to true until shipping through TestFlight || App Store. If false, you must be using live cards, and have the proper iOS entitlement set up. See https://stripe.com/docs/issuing/cards/digital-wallets?platform=react-native#requesting-access-for-ios
Details of the Issued Card you'd like added to the device's wallet
The primary_account_identifier value from the issued card.
The card holder name (used only on iOS)
A user-facing description of the card. Required on Android.
Last 4 digits of the card, only used on iOS
Optional, only used on iOS
Used by stripe to securely obtain card info of the card being provisioned.
When accessible is true, the system will try to invoke this function when the user performs an accessibility custom action.
When accessibile is true, the system will invoke this function when the user performs the escape gesture (scrub with two fingers).
When accessible is true, the system will try to invoke this function when the user performs accessibility tap gesture.
When accessible is true, the system will invoke this function when the user performs the magic tap gesture.
Called when the flow completes. If the error field is null, then the card was successfully added to the user's native wallet.
Generated using TypeDoc
Add to wallet button component props