graphql-api icon indicating copy to clipboard operation
graphql-api copied to clipboard

Add updatePaymentMethod or similar method to SDK libraries

Open nearapogee opened this issue 3 years ago • 4 comments

Seems like updating payment methods is possible in the SDK libraries, but doesn't have an equivalent in GraphQL.

Can you add an updatePaymentMethod or updateCreditCard similar to: https://developers.braintreepayments.com/reference/request/payment-method/update/ruby

Much thanks!

nearapogee avatar Mar 15 '21 18:03 nearapogee

Is there something specific you're looking to update on the payment method? The API currently has updateCreditCardBillingAddress. Most of the other existing options you can supply via the SDKs relate to verification time (cvv, 3DS), but I could see adding updateCreditCardExpiration and maybe updateCreditCardCardholderName, although it might be better to create a new payment method in some of those cases.

Please let us know what items you're looking to update and we can look further into supporting them.

lkorth avatar Mar 19 '21 21:03 lkorth

Hi @lkorth , For merchants who would offer option for customer to define which vaulted payment method as default, it would need function like mark default option for a payment method.

gordonchanhk avatar Jun 08 '21 04:06 gordonchanhk

@lkorth Any update on this? This is the last api call that I'm stuck making through the braintree SDK. I allow customers to update their card exp, holder name, cvv, and their billing address.

Instead of having a separate updateCreditCardExpiration and updateCreditCardCardholderName mutation, I would prefer to simple call updatePaymentMethod and pass the payment id and a nonce token that contains only the holder, exp, and cvv.

Screenshot 2021-10-20 011501 .

tuurbo avatar Oct 20 '21 05:10 tuurbo

updateCreditCardExpiration and updateCreditCardCardholderName could work.... but I don't see why you don't have a parallel option to your own REST API and to be compatible when switching from other gateway vendors. I would prefer not to have to make 2 or 3 requests when the user updates a form that includes address, name, and expiration dates - which are all non-controlled fields. I would prefer updateCreditCard.

I would tend to agree that if you are changing the card number that should be a new payment method. If any controlled data needs to be passed seems like @tuurbo's request is reasonable as well.

Our clients like to reduce friction and causing the user to have to pull out their credit card to update a cardholder name or expiration date causes sales conversions to drop. Hope that makes sense!

Cheers!

nearapogee avatar Oct 20 '21 22:10 nearapogee