The card holder will see a section of the Merchant’s name on their bank statement. The first 8 Characters are reserved for {Yoco *} as mandated by the schemes, then there are 12 remaining characters that will be used from the Merchant’s name. Customer will also see a unique reference number in their bank statement for each transaction, regardless of the amount or whether the merchant was the same.
Hello @elizabethhereandnowdigital, hello @webify24 SSL specific logs might contain false positive warnings. This can happen when site is visited using unsecured protocol http instead of https. For security reasons our plugin refuse to load when unsecured connection is detected. If SSL is properly configured this only affect single request – request that used http. Only when this error persist – that is there are many SSL errors in the logs, were every request result with this error then it might indicate something is wrong with the SSL certificate.
This is WooCommerce setting and Yoco plugin is not involved in order being automatically cancelled.
If customer have Yoco checkout url it can still pay for the order even after order being Cancelled by WooCommerce. After payment is done order status will be updated to Processing regardless of previous status.
This reply was modified 1 year, 10 months ago by Bartech.
I’ve checked the the WooCommerce filter implementation, it expects an array as a parameter. I suspect there must be incorrect implementation for woocommerce_available_payment_gateways filter somewhere in your codebase (other plugins, theme, custom code) Filter should always return array but it’s returning nothing. Filters are applied in the order. Our filter runs after the faulty one and instead of getting proper type array it’s getting null value.
You should search for the woocommerce_available_payment_gateways in you codebase and look for the method that have no return statement ot returns null.
If needed I can assist in pinpointing where is the incorrect filter implementation placed. For this I would need access to your codebase where I can search for the filter use.
