EPASSCARD (GOOGLE WALLET, APPLE WALLET, AND MORE)
EpassCard (Google Wallet, Apple Wallet, and more) compatibility with REEID Translate
EpassCard (Google Wallet, Apple Wallet, and more) compatibility with REEID Translate is being evaluated from available plugin evidence. Issues Apple Wallet passes in standard `.pkpass` format (iPhone/iPad/Apple Watch) and Google Wallet passes from a single template mapping workflow. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for EpassCard (Google Wallet, Apple Wallet, and more).
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
EpassCard (Google Wallet, Apple Wallet, and more) is documented in the Membership category with 8 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How EpassCard (Google Wallet, Apple Wallet, and more) compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Issues Apple Wallet passes in standard `.pkpass` format (iPhone/iPad/Apple Watch) and Google Wallet passes from a single template mapping workflow.
- Automatically creates wallet passes for membership/subscription-related events such as signup, renewal, and mapped data changes (and for some integrations, level assignment/activation/approval/status changes).
- Updates existing wallet passes via the EpassCard API when membership/subscription data changes, keeping passes in sync.
- Distributes passes to members via delivery links (including email links) and supports members opening passes from their account area.
- Supports template mapping from membership/event/gift-card fields to pass template fields, including QR code and barcode fields when present in the template.
- Provides push notification/reminder rules aligned with membership timing (e.g., reminders around expiry/renewal) delivered as wallet pass notifications on supported devices.
- Maintains an admin-facing “Issued passes” list/table that is searchable and includes delivery links for issued passes.
- Connects to the EpassCard pass API using either an API key or email/password sign-in to the EpassCard pass API, and uses the configured credentials to validate and create/update passes.
CONTENT BOUNDARY
EpassCard (Google Wallet, Apple Wallet, and more) capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
EpassCard (Google Wallet, Apple Wallet, and more) and REEID Translate FAQ.
What does EpassCard (Google Wallet, Apple Wallet, and more) do according to the available plugin evidence?
EpassCard (Google Wallet, Apple Wallet, and more) has 8 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for EpassCard (Google Wallet, Apple Wallet, and more)?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for EpassCard (Google Wallet, Apple Wallet, and more)?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate EpassCard (Google Wallet, Apple Wallet, and more) in a multilingual WordPress workflow.
REEID documents EpassCard (Google Wallet, Apple Wallet, and more) functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.