Title: Bartech's Replies | WordPress.org

---

# Bartech

  [  ](https://wordpress.org/support/users/bartech/)

 *   [Profile](https://wordpress.org/support/users/bartech/)
 *   [Topics Started](https://wordpress.org/support/users/bartech/topics/)
 *   [Replies Created](https://wordpress.org/support/users/bartech/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/bartech/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/bartech/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/bartech/engagements/)
 *   [Favorites](https://wordpress.org/support/users/bartech/favorites/)

 Search replies:

## Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Yoco Payments] Transaction on Customer Bank Statement](https://wordpress.org/support/topic/transaction-on-customer-bank-statement/)
 *  Plugin Support [Bartech](https://wordpress.org/support/users/bartech/)
 * (@bartech)
 * [1 year, 3 months ago](https://wordpress.org/support/topic/transaction-on-customer-bank-statement/#post-18315966)
 * 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.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Yoco Payments] plugin temporary suspended due to SSL certificate issue](https://wordpress.org/support/topic/plugin-temporary-suspended-due-to-ssl-certificate-issue/)
 *  Plugin Support [Bartech](https://wordpress.org/support/users/bartech/)
 * (@bartech)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/plugin-temporary-suspended-due-to-ssl-certificate-issue/#post-18272565)
 * Hello [@elizabethhereandnowdigital](https://wordpress.org/support/users/elizabethhereandnowdigital/),
   hello [@webify24](https://wordpress.org/support/users/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.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Yoco Payments] Order to Cancelled Status](https://wordpress.org/support/topic/order-to-cancelled-status/)
 *  Plugin Support [Bartech](https://wordpress.org/support/users/bartech/)
 * (@bartech)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/order-to-cancelled-status/#post-17898820)
 * This is WooCommerce setting and Yoco plugin is not involved in order being automatically
   cancelled.
 * ![](https://i0.wp.com/i.imgur.com/LQh4ZaZ.png?ssl=1)
 * 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](https://wordpress.org/support/users/bartech/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Yoco Payments] CRITICAL Uncaught TypeError](https://wordpress.org/support/topic/critical-uncaught-typeerror-5/)
 *  Plugin Support [Bartech](https://wordpress.org/support/users/bartech/)
 * (@bartech)
 * [1 year, 12 months ago](https://wordpress.org/support/topic/critical-uncaught-typeerror-5/#post-17822413)
 * Hello Robin,
   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.

Viewing 4 replies - 1 through 4 (of 4 total)