Hi @corneliusw,
That’s my assumption at the moment, it’s based on the first part of the error logs where the card issuer is declining the transaction. The customer then needs to contact their bank/card issuer to try and clear that up to purchase from your site.
Hi @stevekatasi,
I think your next best option would be to use Stripe where the charges are authorized only. Just to be upfront Stripes authorization period is shorter than some other payment methods at 7 days, so when an order is placed that authorization lasts for 7 days before being cancelled.
But either way, no matter the payment method you can authorize a charge which doesn’t yet charge the customer. If the order isn’t cancelled you can then capture the charge on the 8th day to actually charge the customer. This gives you a “free trial” so to speak. 🙂
Hi @anthonytowey,
Please do send the log files from Stripe our way. In particular if you have a log file from the date when some failed orders happened. That’ll be very helpful, thanks!
@stevek28,
No problem on the system status, I understand the need to keep that private. 🙂
From what I can see so far this string is definitely within the Stripe plugin, there’s also a similar one within Subscriptions as well. It is confusing to me why that translation isn’t working, even when I’ve tried manually translating or using Loco Translate it doesn’t work for me.
I’ve gone ahead and created an issue for this in our Stripe repo to see what we’re doing wrong or perhaps missing. 😛
https://github.com/woocommerce/woocommerce-gateway-stripe/issues/1097
Hi @kartikparmar,
Thanks for that error log, it is essentially saying that a payment failed because a customer tried to pay with a non INR currency while using an address within India.
That seems to be not allowed by Stripe at the moment. 🙂
Hi @datastream,
I really wanted to highlight that sometimes when an error occurs the error banner may be blank. Wouldn’t it be better if some message could be displayed rather than the blank error banner?
Absolutely, I wanted to do some of that basic conflict testing to rule out a plugin or theme causing the empty error notice.
Once any sort of conflict could be ruled out, we can look at the next potential causes. Does that make sense?
Hi @corneliusw,
Thanks for sending those logs over, the first one sounds like it is coming from a Stamps.com plugin. For some reason it may be the defaulted log selected or shown when viewing the logs tab.
The second one from Stripe though is the important one. 🙂
The first part of it does make it sound like the customers card issuer blocked the payment. Which would mean they need to contact their bank/card issuer. It then mentions some Radar rules, do you have any specific ones setup in your Stripe.com account? –> https://dashboard.stripe.com/radar/rules
It mentions default rules, so it seems like they are just account enabled default rules for Radar.
Howdy @sveberes,
We haven’t heard back from you in a while, so I’m going to mark this as resolved – if you have any further questions, you can start a new thread.
Hi @susanlangenes,
So sorry, I didn’t realize our Square repo was private. I assumed since this was a free plugin open sourced on WordPress.org it was a public repo.
Either way, the issue is logged and will be worked on ASAP. 🙂
Hi @renz_r,
Woo! I’m glad that was the solution. Happy to help!
Hi @tonyzeoli,
Would you first be able re-enable the debug log for Square? That would be helpful to have since this is an error coming from Square. 🙂
Then if any errors are logged you’ll find those under WooCommerce > Status > Logs tab. There will be a Square log for every day that logging is enabled. Pick the appropriate date to find the logs from today.
Also, are you able to update to Square 2.0.7 and see if that helps anything. Let us know what you find in the logs from today and if updating helps.
Hi @admiraltuuvok,
I think if the product still allows backorders then it’s not truly out of stock. I think the confusion is that this snippet is looking for the Out of Stock status to add the Sold Out label.
The CSS stays the same from the Business Bloomer tutorial, but modify their PHP snippet to look for the backorder and backorder & notify statuses.
function bbloomer_display_sold_out_loop_woocommerce() {
global $product;
if ( $product->managing_stock() && $product->is_on_backorder( 1 ) ) {
echo '<span class="soldout">' . __( 'SOLD OUT', 'woocommerce' ) . '</span>';
}
}
add_action( 'woocommerce_before_shop_loop_item_title', 'bbloomer_display_sold_out_loop_woocommerce' );
Link to image: https://cld.wthms.co/EHgT9o
&
Link to image: https://cld.wthms.co/MzzE2m
-
This reply was modified 6 years, 7 months ago by Ryan Ray.
Hi Steve,
To go in one different direction, from the CSS provided ny @princebhalani143, you could use a plugin like the one from SkyVerge or follow the tutorial from Business Bloomer.
https://www.skyverge.com/product/woocommerce-remove-product-sorting/
https://businessbloomer.com/woocommerce-remove-default-sorting-dropdown/
While CSS does hide it, the functionality and code is still ran and rendered on every page load. It feels only slightly more proper to use PHP to remove it rather than hiding it via CSS.
Both are perfectly valid options though and will do what you’re after. 🙂
Hi @fotokart,
Thanks a ton for that system status. I’ve been able to recreate this with the Filter by Tag block, thus I created an issue for this over in the WooCommerce Blocks repo. –> https://github.com/woocommerce/woocommerce-gutenberg-products-block/issues/1234
I’d expect we’ll get a fix for this shortly, but I don’t have anything beyond that at the moment. 🙂
Thanks for helping discover and report this.
Hi @fmixell,
Glad you got things sorted out with WP Engine. I can confirm, at least in my test just now, that if you create a product in Square (give it a SKU, category, inventory, and price) and then tell your site to import products it will add that to your Woo store. 🙂
Link to image: https://cld.wthms.co/bvKhXK
