bfl

This plugin already includes Accept.js from Authorize.net and is SAQ A-EP compliant. The only plugin I found that has made any such changes is SkyVerge Authorize.Net, which appears to have reverted whatever changes were made.

Hey. There is currently no officially supported way to do this. However, you can use a snippet like the following:

add_action( 'add_meta_boxes_shop_order', function () {
    if ( ! current_user_can( 'view_manual_payments' ) ) {
        remove_meta_box( 'woo-mp', 'shop_order', 'advanced' );
    }
}, 100 );

To make this work, you would need to create a view_manual_payments capability and add it to the roles you need. I’m not familiar with the plugin you mentioned, so I can’t really help with figuring that out.

This snippet relies on the internal workings of Woo MP, so it is not guaranteed to work with all future releases. However, it should not cause any errors if it doesn’t work.

A no-code alternative would be to find a plugin which lets you control which user roles can use a particular meta box.

Hey. Thanks for the feedback. I’m aware of this need from other requests. It’s on my list of future features, but I’m not currently working on it. The invoice would be a separate feature, which has also been requested before.

Hey. Sorry for the delay. Getting the Stripe fee would require a separate request to the Stripe API. It is not included in the PaymentIntent object returned from the payment_intents request that this plugin makes. That introduces some complexity, so I don’t plan on adding that. I’m adding this to my list of possible future features though. Thanks.

If they would forget to change the address, then they might forget to enter the address in the proposed fields. Maybe what you need is just a contextual reminder to remind the employee to change the billing address. We could work on a simple code snippet that would add such a reminder to a prominent location in the form. Maybe something like this would work?

The issue I see with adding those fields is that it would create a mismatch between the new numeric details and the rest of the address fields from the order. To resolve any contradictions, I would have to either only send the new details and omit all the other billing details from the order (which may be surprising to the user), or I would have to provide all the usual address fields (which would add a lot of duplication). I don’t really like any of these options.

The billing address and billing ZIP Code from the order are already sent to Authorize.Net. Do you mean that you need to send a different address and ZIP Code on a per-card basis? One workflow would be to change the order’s billing details before making the payment.

No, this plugin does not have the ability to save payment methods or to charge saved payment methods.