bfl

1. Can you confirm that the publishable key configured for Backend Payments is the same as the one shown in the Stripe dashboard (https://dashboard.stripe.com/apikeys)?
2. Is this issue happening for any of your other clients?
3. Do you know more precisely when the issue started? Did anything change with the Stripe account or were any new plugins added to the website or was the website changed in some other way?

I’ve looked into this some more and I haven’t been able to produce that error without having the “Enable card data collection…” setting disabled. Can you have Stripe confirm from their end that that setting is definitely enabled for your account? It really shouldn’t be possible to get that error from Stripe if the setting is really enabled.

Go to https://dashboard.stripe.com/settings/integration and check “Enable card data collection with a publishable key…”.

Thank you!

Hey @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.

You 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.

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.

Sorry, the plugin can’t be used with Stripe Connect.