Viva.com Support
Forum Replies Created
-
Hello @hardline1988 ,
Based on the error message and the steps you’ve already taken, this is a webhook communication issue, most likely due to network-level restrictions or firewall settings.
To resolve this, you need to whitelist Viva.com’s webhook IPs in all layers that may restrict inbound traffic, including:
- Hosting/server firewall
- Web application firewall (WAF)
- Content Delivery Network (CDN)
- Security plugins
Refer to our official documentation for the IP list:
🔗 https://developer.viva.com/webhooks-for-payments/#whitelist-the-viva-addressesThis ensures your endpoint can receive POST requests from Viva’s webhook service.
Once the whitelist is applied, retry the connection from the plugin.
Kind regards,
Viva E-commerce Support TeamHello @rederijker ,
Thank you for your message. We apologize for the delay and thank you for your patience.
To assist you better, please reach out to us via email at [email protected] or via the Live Chat option (which can be found at the bottom-right of the main Viva.com site, or in your Production Viva.com self-care account)
Kind regards,
Viva E-commerce Support TeamHello @onuproy01 ,
Thank you for your message.
To assist you better, please reach out to us via email at [email protected] or via the Live Chat option (which can be found at the bottom-right of the main Viva.com site, or in your Production Viva.com self-care account)
Kind regards,
Viva E-commerce Support TeamHello @bobbivd
Thank you for your message. We apologize for the delay and thank you for your patience.
To assist you better, please reach out to us via email at [email protected] or via the Live Chat option (which can be found at the bottom-right of the main Viva.com site, or in your Production Viva.com self-care account)
Kind regards,
Viva E-commerce Support TeamForum: Reviews
In reply to: [Viva.com | Smart Checkout for WooCommerce] Waste of timeThanks for reaching out and for using our plugin across your WooCommerce stores. Just to clarify—our Standard [no longer supported or actively developed] and Smart Checkout plugins are separate, so if both are installed, it’s expected that you’ll see both active.
If you’re looking to move fully to Smart Checkout, please check out our migration guide.
To help with the large logo issue, could you let us know which theme you’re using? And when you say “it does not work,” are payments failing entirely, or is the issue more about layout or user experience?
Happy to assist once we have more details.
Best,
Viva.com SupportHello @bobbivd ,
Thank you for your message. We apologize for the delay and thank you for your patience.
To assist you better, please reach out to us via email at [email protected] or via the Live Chat option (which can be found at the bottom-right of the main Viva.com site, or in your Production Viva.com self-care account)
Kind regards,
Viva E-commerce Support TeamHello @oscarbugaric,
Thank you for your message. We apologize for the delay and thank you for your patience.
In the Viva.com WordPress plugin, the Smart Checkout language is determined based on the following logic:
- User-selected language preference:
If the customer manually selects a language during the Smart Checkout process, this preference is stored in their browser. On future visits, the checkout will automatically appear in the chosen language to provide a consistent experience. - No user selection (first-time use):
If no manual selection has been made, the plugin includes a language value when creating the order. This is based on the language configured in the WordPress environment and is passed to Smart Checkout asrequestLang. - Country-based fallback:
If neither of the above is available, the checkout will use a language based on country information from the merchant.
Kind regards,
Viva E-commerce Support TeamForum: Plugins
In reply to: [Viva.com | Smart Checkout for WooCommerce] Viva Fatal Error at CheckoutHi @zelenius,
Appreciate you flagging this.
Looking at the error trace, it seems number_format() is receiving a string instead of the expected float. Based on our checks, our plugin is passing the correct float value from its core logic, so this might be caused by a theme (like WoodMart) or another plugin modifying the value before it reaches that point.
When you have a chance, could you try testing with a default WooCommerce theme (like Storefront) and only essential plugins active? That would help pinpoint whether it’s a theme or plugin conflict.
Let us know what you find—we’re happy to help further.