bfl
Forum Replies Created
-
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Issue with Auth.netHey @cmilleratlas. Most Authorize.Net plugins do not require the Client Key field. You will need to follow the instructions in step 2 to find your Client Key.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Compatibility with SquareHey @lifespa. As of now, gateways have to be included in the plugin. I’m not confident enough in the stability of the API to open it up for extension yet.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Authorize.net AVSThis is most likely due to the account’s AVS settings. You can read about it here.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Authorize.net AVSHey @ibtisamtahir. Are you getting any particular error?
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Add Stripe [receipt_url] to order_metaThat snippet requires WooCommerce 3.0.0 or above. What version are you on?
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Add Stripe [receipt_url] to order_metaCurrently, there is no good way to do this. I will consider adding an action hook. For now, you can use the following snippet:
add_filter( 'http_response', function ( $response, $r, $url ) { if ( doing_action( 'wp_ajax_woo_mp_process_transaction' ) && isset( $_REQUEST['order_id'] ) && $url === 'https://api.stripe.com/v1/payment_intents' ) { $decoded_body = json_decode( wp_remote_retrieve_body( $response ) ); if ( isset( $decoded_body->charges->data[0] ) ) { $order = wc_get_order( $_REQUEST['order_id'] ); if ( $order ) { $charge = $decoded_body->charges->data[0]; $order->add_meta_data( 'manual_payment_stripe_receipt_url', json_encode( [ 'charge_id' => $charge->id, 'receipt_url' => $charge->receipt_url, ] ) ); $order->save_meta_data(); } } } return $response; }, 10, 3 );This will add a new custom field for each payment containing the charge ID and the receipt URL. This requires version 2.4.0. Note that since this snippet relies on the internal workings of the plugin, it is not guaranteed to work in future versions.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] 3D SecureHey @facialflex. I released a new version of the plugin. There is a new Mark Payments as MOTO setting which will allow you to make use of the Mail Order / Telephone Order (MOTO) SCA exemption. Let me know if you have any issues. Thanks.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Total does not updateWooCommerce core doesn’t support partial payments for a single order. If an order has a status that allows the customer to make a payment, that payment will always be for the order total. This plugin doesn’t add anything to the visitor-facing part of your site. As of now, there is no way for the customer to pay a partial amount without changing the order total. Are you using WooCommerce Deposits? WooCommerce Deposits creates a new order for each payment.
Being able to set different statuses is a good idea. I may add action hooks in the future that would allow you to update the order in different ways depending on whether the order is fully paid for or partially paid for.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Total does not updateHey @nateadmin. That is the order total, not the amount owed. The order total never changes. Even payments made with regular payment gateways will not update that amount.
You may be interested in the Update Order Status When setting:
- Go to WooCommerce > Settings > Manual Payment
- Set the Update Order Status When setting
- Set the Update Order Status To setting
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] 3D SecureHey @facialflex. I am working on this. Stripe currently requires you to contact them to enable this feature on your account. Here’s the relevant section in the documentation. I’m in contact with Stripe and I’m trying to get this enabled on my own test account. I’ll get back to you when I have updates.
Yes, that snippet should work.
That should do it.
If the payment is captured, the
_stripe_charge_capturedfield needs to be set toyes.Hey @careyrob. The official Stripe plugin is only supposed to be used to refund payments made by that plugin. It expects certain metadata to be added to the order at the time of payment. One of those fields indicates whether the payment has been captured. This field is not set by our plugin (as it is not used by WooCommerce core), so when the Stripe plugin looks for it and doesn’t find it, it assumes that the payment was not captured. As a result, they do not send the refund amount to Stripe. This causes the payment to be fully refunded.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Issue with Auth.netHey @tsunamiecig. Have you resolved this issue?