
INSTANT CRYPTO PAYMENTS FOR WOOCOMMERCE
Instant Crypto Payments for WooCommerce compatibility with REEID Translate
Instant Crypto Payments for WooCommerce compatibility with REEID Translate is being evaluated from available plugin evidence. Integrates ICPay as a WooCommerce payment gateway for crypto transactions No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Instant Crypto Payments for WooCommerce.
Official documentation did not establish a visitor-facing content item within the supported scope for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Instant Crypto Payments for WooCommerce is documented in the WooCommerce 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 Instant Crypto Payments for WooCommerce 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
- Integrates ICPay as a WooCommerce payment gateway for crypto transactions
- Supports over 50 cryptocurrencies and tokens across multiple chains including Base and Internet Computer
- Provides real-time payment confirmations via webhooks with automatic order status updates
- Compatible with High-Performance Order Storage (HPOS) and Cart/Checkout Blocks
- Offers optional WalletConnect integration for mobile wallet connections
- Includes settings to filter allowed tokens by shortcode and edit metadata key/value pairs
- Renders a pay button on Checkout and Order Pay pages with an optional Express Checkout feature
- Operates as a non-custodial solution where funds are settled directly to the merchant's wallet
CONTENT BOUNDARY
Instant Crypto Payments for WooCommerce 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
- No visitor-facing translation surface was established for this integration.
COMMON QUESTIONS
Instant Crypto Payments for WooCommerce and REEID Translate FAQ.
What does Instant Crypto Payments for WooCommerce do according to the available plugin evidence?
Instant Crypto Payments for WooCommerce 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 Instant Crypto Payments for WooCommerce?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Instant Crypto Payments for WooCommerce?
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 Instant Crypto Payments for WooCommerce in a multilingual WordPress workflow.
REEID documents Instant Crypto Payments for WooCommerce 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.