bfl
Forum Replies Created
-
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Issue with Auth.netHey @tsunamiecig. There are three settings that are required: Login ID, Transaction Key, and Client Key. The Client Key is not used by all Authorize.Net plugins, so comparing the settings with another plugin’s settings may mislead you. You can find instructions for getting the Client Key here.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] PayPal / BrainTree GatewayI don’t currently have any plans for this, however it is one of the gateways I’ve been considering.
Hey @swatts. It looks like there is some code on your site that is outputting some data that is getting in the way. Try deactivating all plugins besides WooCommerce and this one, and then process another payment.
This part should not be here:
Array ( [0] => completed )It is the result of a call to the
print_rfunction from something outside this plugin.Forum: Reviews
In reply to: [Backend Payments for WooCommerce] Really useful simple pluginForum: Plugins
In reply to: [Backend Payments for WooCommerce] Square GatewayI don’t have any plans to add it at this time, however it is one of the gateways I’ve been considering.
Glad you resolved it. Thanks for the review.
Forum: Everything else WordPress
In reply to: “Tested up to: 5.2” not workingOK, I see. Thanks.
Forum: Everything else WordPress
In reply to: “Tested up to: 5.2” not workingThanks @joyously. The first beta has already been released though, do you know at what point they will accept a value of “5.2”?
Forum: Everything else WordPress
In reply to: “Tested up to: 5.2” not workingCan you try going to the WordPress Updates page and clicking Check Again? There was an issue with the WordPress.org plugin directory which I’ve resolved, so it could be that.
Hey @captainbeat. That’s correct, but it doesn’t matter anymore because I’ve just released a new version that fixes the bug.
Thanks, that screenshot helped me find the issue. It’s a bug. I’m going to release a new version soon that will fix it.
For now, you can actually charge cents using a full stop, just ignore the formatted amount on the charge button.
Hey @captainbeat. If you’re referring to the charge amount field, you should be able to use a full stop (.) to separate dollars from cents (for example, “9.99”).
The reason I’ve made it work like that is because this plugin doesn’t actually add its own WooCommerce payment methods and it doesn’t assume which gateway plugin the store is using for standard customer-initiated payments on the visitor-facing side of the site. If I set the payment method to “stripe” then I would be assuming that the store is using a gateway plugin that adds a payment method with the ID “stripe”. Not all Stripe plugins use “stripe” as the payment method ID. This one for instance uses “eh_stripe_pay”. What I can do is add a setting that lets you choose which payment method it should set for the order. I’ve thought about this in the past and I’ll consider it some more.
For now, you can use the following snippet to automatically set the payment method:
add_action( 'woo_mp_payment_complete', function ( $order ) { $order->set_payment_method( WC()->payment_gateways->payment_gateways()['stripe'] ); $order->save(); }, 10, 1 );Let me know how it goes. Thanks.
Hey @careyrob. On my test site with the official Stripe gateway, I’m able to get the payment method properly set by using “stripe” as the Title on the WooCommerce > Settings > Manual Payment > Stripe page. Can you please provide your WooCommerce status report? For privacy purposes, you can email it to bfl.wordpress.org@gmail.com.