poglaa

Hi @mrclayton

That makes sense. Thanks for your quick replies! It’s just not that future proof solution. If in the future, you will add more gateways to the list, it will affect our site. But I think that’s not going to happen often.

• This reply was modified 1 year, 8 months ago by poglaa.

Also, could you please add a filter inside the “\WC_Braintree_Payment_Gateway::available_payment_gateways” method? We’d like to be able to filter the list of gateways that are being unset there.

Something like this would be great:

	public static function available_payment_gateways( $gateways ) {
		global $wp;
		if ( is_add_payment_method_page() && isset( $wp->query_vars['add-payment-method'] ) ) {
			$unset_gateways = apply_filters(
				'wcs_braintree_unset_payment_gateways_on_add_method_page',
				[
					'braintree_paypal',
					'braintree_applepay',
					'braintree_googlepay',
					'braintree_venmo',
				]
			);

			foreach ( $unset_gateways as $unset_gateway ) {
				unset( $gateways[ $unset_gateway ] );
			}
		}

		return $gateways;
	}

Hi @mrclayton

You are right but we are not using the default “Change payment method” WooCommerce Subscriptions functionality. We have a custom implementation for that.

Hi @mrclayton

Thanks for your quick reply. Here is one of our cases:

1. Customer have plenty active subscriptions. They used different PayPal accounts for each of them.
2. Customer wants to change PayPal payment method on a subscription. Let’s say they want to start paying subscription from their business account.
3. Customer adds a new PayPal method to their account via the “Add Payment Method” page.
4. Customer updates their payment method on one or all of their subscriptions.

In your plugin currently, the only way I see that the customer can do such thing is to create a new subscription so the new PayPal method gets saved. (I did not test this yet. I’m assuming.)

I personally do not se any reason why limiting gateways on the “Add Payment Method” page.

Cheers!

@michel-jongbloed Can you just post the solution here?

@mannweb It’s fixed now. Please update to version 1.0.1.

@danabel

There is a better solution for this. No need to touch the plugin’s code.

add_filter( 'wc_braintree_api_request_data', 'allow_duplicate_card' );
public function allow_duplicate_card( $request_data ) {
 if ( isset( $request_data['options'], $request_data['options']['failOnDuplicatePaymentMethod'] ) ) {
  $request_data['options']['failOnDuplicatePaymentMethod'] = false;
  }
 return $request_data;
}

• This reply was modified 5 years, 9 months ago by poglaa.