Title: bfl's Replies | WordPress.org

---

# bfl

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

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

 Search replies:

## Forum Replies Created

Viewing 15 replies - 1 through 15 (of 285 total)

1 [2](https://wordpress.org/support/users/bfl/replies/page/2/?output_format=md) 
[3](https://wordpress.org/support/users/bfl/replies/page/3/?output_format=md) … 
[17](https://wordpress.org/support/users/bfl/replies/page/17/?output_format=md) 
[18](https://wordpress.org/support/users/bfl/replies/page/18/?output_format=md) 
[19](https://wordpress.org/support/users/bfl/replies/page/19/?output_format=md) 
[→](https://wordpress.org/support/users/bfl/replies/page/2/?output_format=md)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Backend Payments for WooCommerce] Using with WooCommerce Subscriptions](https://wordpress.org/support/topic/using-with-woocommerce-subscriptions-2/)
 *  Plugin Author [bfl](https://wordpress.org/support/users/bfl/)
 * (@bfl)
 * [2 months, 3 weeks ago](https://wordpress.org/support/topic/using-with-woocommerce-subscriptions-2/#post-18822759)
 * Hey [@davekeller](https://wordpress.org/support/users/davekeller/). This plugin
   does not support WooCommerce Subscriptions.
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[Backend Payments for WooCommerce] Simple and effective plugin](https://wordpress.org/support/topic/simple-and-effective-plugin-41/)
 *  Plugin Author [bfl](https://wordpress.org/support/users/bfl/)
 * (@bfl)
 * [6 months, 2 weeks ago](https://wordpress.org/support/topic/simple-and-effective-plugin-41/#post-18693457)
 * Thank you!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Backend Payments for WooCommerce] Not working after 2.8.7 update](https://wordpress.org/support/topic/not-working-after-2-8-7-update/)
 *  Plugin Author [bfl](https://wordpress.org/support/users/bfl/)
 * (@bfl)
 * [6 months, 3 weeks ago](https://wordpress.org/support/topic/not-working-after-2-8-7-update/#post-18691097)
 * I just released 2.8.8 to fix the issue.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Backend Payments for WooCommerce] Not working after 2.8.7 update](https://wordpress.org/support/topic/not-working-after-2-8-7-update/)
 *  Plugin Author [bfl](https://wordpress.org/support/users/bfl/)
 * (@bfl)
 * [6 months, 3 weeks ago](https://wordpress.org/support/topic/not-working-after-2-8-7-update/#post-18691078)
 * Hey [@greencode](https://wordpress.org/support/users/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](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Backend Payments for WooCommerce] Prevent Duplicate Payments](https://wordpress.org/support/topic/prevent-duplicate-payments/)
 *  Plugin Author [bfl](https://wordpress.org/support/users/bfl/)
 * (@bfl)
 * [11 months, 2 weeks ago](https://wordpress.org/support/topic/prevent-duplicate-payments/#post-18490153)
 * That snippet does not cover that scenario. It would be more complicated to cover
   that.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Backend Payments for WooCommerce] Prevent Duplicate Payments](https://wordpress.org/support/topic/prevent-duplicate-payments/)
 *  Plugin Author [bfl](https://wordpress.org/support/users/bfl/)
 * (@bfl)
 * [11 months, 3 weeks ago](https://wordpress.org/support/topic/prevent-duplicate-payments/#post-18483061)
 * You can use the following snippet:
 *     ```wp-block-code
       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](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Backend Payments for WooCommerce] Stripe’s pre-built UI elements](https://wordpress.org/support/topic/stripes-pre-built-ui-elements/)
 *  Plugin Author [bfl](https://wordpress.org/support/users/bfl/)
 * (@bfl)
 * [1 year, 1 month ago](https://wordpress.org/support/topic/stripes-pre-built-ui-elements/#post-18384866)
 * Hey [@mattcasburn](https://wordpress.org/support/users/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.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Backend Payments for WooCommerce] Choose between Authorize and Authorize/Capture and Capture](https://wordpress.org/support/topic/choose-between-authorize-and-authorize-capture-and-capture/)
 *  Plugin Author [bfl](https://wordpress.org/support/users/bfl/)
 * (@bfl)
 * [1 year, 2 months ago](https://wordpress.org/support/topic/choose-between-authorize-and-authorize-capture-and-capture/#post-18353806)
 * 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](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Backend Payments for WooCommerce] Possible inclusion of Moneris?](https://wordpress.org/support/topic/possible-inclusion-of-moneris/)
 *  Plugin Author [bfl](https://wordpress.org/support/users/bfl/)
 * (@bfl)
 * [1 year, 2 months ago](https://wordpress.org/support/topic/possible-inclusion-of-moneris/#post-18351169)
 * Sorry, I’m not currently adding any new payment gateways.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Backend Payments for WooCommerce] stripe connected accounts](https://wordpress.org/support/topic/stripe-connected-accounts/)
 *  Plugin Author [bfl](https://wordpress.org/support/users/bfl/)
 * (@bfl)
 * [1 year, 3 months ago](https://wordpress.org/support/topic/stripe-connected-accounts/#post-18283037)
 * Sorry, the plugin can’t be used with Stripe Connect.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Backend Payments for WooCommerce] Order information fields](https://wordpress.org/support/topic/order-information-fields/)
 *  Plugin Author [bfl](https://wordpress.org/support/users/bfl/)
 * (@bfl)
 * [1 year, 5 months ago](https://wordpress.org/support/topic/order-information-fields/#post-18188691)
 * The 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_request`
   filter, like so:
 *     ```wp-block-code
       /** @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](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Backend Payments for WooCommerce] Swipe card on legacy mag stripe reader](https://wordpress.org/support/topic/swipe-card-on-legacy-mag-stripe-reader/)
 *  Plugin Author [bfl](https://wordpress.org/support/users/bfl/)
 * (@bfl)
 * [1 year, 5 months ago](https://wordpress.org/support/topic/swipe-card-on-legacy-mag-stripe-reader/#post-18182024)
 * Hey. 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](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Backend Payments for WooCommerce] Missing Data in Stripe Transaction List](https://wordpress.org/support/topic/missing-data-in-stripe-transaction-list/)
 *  Plugin Author [bfl](https://wordpress.org/support/users/bfl/)
 * (@bfl)
 * [1 year, 5 months ago](https://wordpress.org/support/topic/missing-data-in-stripe-transaction-list/#post-18133797)
 * Hey.
 * 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-16600408](https://wordpress.org/support/topic/add-order-number-to-the-stripe-description/#post-16600408)
 * For the email address, see here:
   [https://wordpress.org/support/topic/zip-post-code-check/#post-18043902](https://wordpress.org/support/topic/zip-post-code-check/#post-18043902)
 * The 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](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Backend Payments for WooCommerce] Setup for Stripe](https://wordpress.org/support/topic/setup-for-stripe/)
 *  Plugin Author [bfl](https://wordpress.org/support/users/bfl/)
 * (@bfl)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/setup-for-stripe/#post-18111208)
 * Minimal 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](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Backend Payments for WooCommerce] Setup for Stripe](https://wordpress.org/support/topic/setup-for-stripe/)
 *  Plugin Author [bfl](https://wordpress.org/support/users/bfl/)
 * (@bfl)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/setup-for-stripe/#post-18098034)
 * Go here to find your secret and publishable keys: [https://dashboard.stripe.com/apikeys](https://dashboard.stripe.com/apikeys)
 * Sorry about the outdated instructions. I’m going to work on updating them.

Viewing 15 replies - 1 through 15 (of 285 total)

1 [2](https://wordpress.org/support/users/bfl/replies/page/2/?output_format=md) 
[3](https://wordpress.org/support/users/bfl/replies/page/3/?output_format=md) … 
[17](https://wordpress.org/support/users/bfl/replies/page/17/?output_format=md) 
[18](https://wordpress.org/support/users/bfl/replies/page/18/?output_format=md) 
[19](https://wordpress.org/support/users/bfl/replies/page/19/?output_format=md) 
[→](https://wordpress.org/support/users/bfl/replies/page/2/?output_format=md)