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

can't confirm payment intent when adding payment_consent_id #105

Open
2 of 14 tasks
leesegundo opened this issue Feb 7, 2024 · 0 comments
Open
2 of 14 tasks

can't confirm payment intent when adding payment_consent_id #105

leesegundo opened this issue Feb 7, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@leesegundo
Copy link

leesegundo commented Feb 7, 2024

Describe the bug I am trying to make a payment transaction using the customer's existing payment method using consent. I can't confirm payment intent if I add a payment_consent_id instead of element but the confirmPaymentElement() method still looking for the element eventhough I use a payment_consent_id

To Reproduce

  1. On triggerConfirm() function, update the confirmPaymentIntent to:

confirmPaymentIntent({
payment_consent_id: 'your_payment_consent_id'
id: intent_id,
client_secret,
},
})

Expected behavior This should confirm the paymentIntent

Screenshots
image

Integration information:

  • language

    • angular
    • cdn
    • node
    • react
    • react-ts
    • ReactNative
    • vue
  • element

    • hpp
    • dropIn element
    • card element
    • split card element
    • full featured card element
    • applePay element
    • googlePay element
      Contexts:
  • Browser (e.g. stock browser, safari):

  • Language:

@leesegundo leesegundo added the bug Something isn't working label Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant