Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add updatePaymentMethod or similar method to SDK libraries #19

Open
nearapogee opened this issue Mar 15, 2021 · 4 comments
Open

Add updatePaymentMethod or similar method to SDK libraries #19

nearapogee opened this issue Mar 15, 2021 · 4 comments
Labels
enhancement New feature or request

Comments

@nearapogee
Copy link

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!

@lkorth
Copy link
Member

lkorth commented Mar 19, 2021

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 lkorth added the enhancement New feature or request label Mar 19, 2021
@gordonchanhk
Copy link

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.

@tuurbo
Copy link

tuurbo commented Oct 20, 2021

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

@nearapogee
Copy link
Author

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants