bfl
Forum Replies Created
-
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Using with WooCommerce SubscriptionsHey @davekeller. This plugin does not support WooCommerce Subscriptions.
Forum: Reviews
In reply to: [Backend Payments for WooCommerce] Simple and effective pluginThank you!
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Not working after 2.8.7 updateI just released 2.8.8 to fix the issue.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Not working after 2.8.7 updateHey @greencode. Sorry about that. I changed the stable version back to 2.8.6 for now. I’m going to work on this. Thanks for informing me.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Prevent Duplicate PaymentsThat snippet does not cover that scenario. It would be more complicated to cover that.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Prevent Duplicate PaymentsYou can use the following snippet:
add_action( 'admin_enqueue_scripts', function ( $hook ) {
if ( $hook === 'woocommerce_page_wc-orders' ) {
?>
<script>
function confirmManualPayment( event ) {
event.preventDefault();
if (
( event.type === 'keypress' && event.keyCode === 13 && event.target?.matches( '#charge *' ) ) ||
( event.type === 'click' && event.target?.id === 'charge-btn' )
) {
if ( jQuery( '#_transaction_id' ).val() ) {
if ( ! confirm( 'There is already a payment on this order. Would you like to proceed?' ) ) {
event.stopPropagation();
}
}
}
}
document.addEventListener( 'keypress', confirmManualPayment, true );
document.addEventListener( 'click', confirmManualPayment, true );
</script>
<?php
}
} );This will only work if the customer paid using a payment method that fills out the WooCommerce Transaction ID field (which you can see when editing Billing fields on the order screen). It determines whether a payment has been made by checking if that field is filled out. If you use other payment methods that don’t use that field, you’ll need to determine whether the order has been paid by some other check. Gateways like Stripe use that field.
Also, this snippet depends on some internal implementation details of WooCommerce and Woo MP, so it may need to be updated if either plugin changes something relevant.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Stripe’s pre-built UI elementsHey @mattcasburn. Yes, this is a new Stripe restriction. At some point I will need to update the plugin to use Stripe Elements, but for now you must enable that setting.
You can uncheck the “Capture Payments” setting and then payments will only be authorized (and the log you mentioned will indeed reflect that). But there is currently no way to capture payments using this plugin, you have to do it from your payment gateway’s dashboard.
I wrote down the idea of having an option to capture or authorize per payment, but I don’t plan on adding any substantial features at the moment.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Possible inclusion of Moneris?Sorry, I’m not currently adding any new payment gateways.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] stripe connected accountsSorry, the plugin can’t be used with Stripe Connect.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Order information fieldsThe plugin currently puts the order number in the Invoice # field and the website name in the Description field.
As far as I’m aware, WooCommerce does not have a concept of an “invoice number”.
You can customize the data sent to Authorize.net using the
woo_mp_authorize_net_charge_requestfilter, like so:/** @param \WC_Order $order */
add_filter( 'woo_mp_authorize_net_charge_request', function ( $request, $order ) {
$request['createTransactionRequest']['transactionRequest']['order']['invoiceNumber'] = 'Put something else here...';
$request['createTransactionRequest']['transactionRequest']['order']['description'] = $order->get_order_number();
return $request;
}, 10, 2 );If you have some plugin that assigns invoice numbers to orders, you can put that where it says “Put something else here…”.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Swipe card on legacy mag stripe readerHey. This sounds like something that might be possible for your developer to do with a bit of JavaScript. Give them the exact format of the reader output and have them write some code to autofill the card fields based on that. You can try reading into Notepad or any other text editor to see exactly what the device is typing and then replace any sensitive numbers with zeros and copy/paste the whole thing.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Missing Data in Stripe Transaction ListHey.
For adding the order number to the description, see this support thread:
https://wordpress.org/support/topic/add-order-number-to-the-stripe-description/#post-16600408For the email address, see here:
https://wordpress.org/support/topic/zip-post-code-check/#post-18043902The metadata is unstructured (free-form), so the labels don’t have any effect. I originally used those labels because that is what the official Stripe plugin used at the time.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Setup for StripeMinimal permissions would be PaymentIntents Write and Charges Write.
However the error you received is not a permissions error, it means that the key is incorrect. Check to make sure the “Secret Key” setting contains just the correct restricted key.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Setup for StripeGo here to find your secret and publishable keys: https://dashboard.stripe.com/apikeys
Sorry about the outdated instructions. I’m going to work on updating them.