#transpile

1 messages · Page 1 of 1 (latest)

mortal atlasBOT
arctic harness
#

Generally, a lot of issuers don't requires AVS for payments so we don't collect it

granite mortar
#
const paymentResult = await stripe.confirmCardPayment(clientSecret, {
      payment_method: {
        card: elements.getElement(CardElement),
        billing_details: {
          name: invoiceFullName,
          email: invoiceEmail,
          phone: invoicePhone,
        },
      },
    });
arctic harness
#

You'd pass the billing fields when you use confirmCardPayment, like:

stripe.confirmCardPayment('pi_foo_secret_bar', {
  payment_method: {
    card: cardElement,
    billing_details: {
      ...
    },
  },
})```
granite mortar
#

Ok, U mean with this i can build a custom UI and have fields for card name, card number and card billing address?
so the values will be passed into the billing_details object for confirmation before the payment is confirmed ?

arctic harness
#

Yes, exactly. Or update and use the newer Payment Element w/ Address Element which will handle all this for you

granite mortar
#

The issue i am having with that payment element is the request url

#

the model requires that a request url is required and redirect users after payment is made to the success page or another

#

We dont wanna do that one our web app

#

Thats why i choose to use cardElement

arctic harness
#

Sorry, don't really understand that part. But sure, still fine to use the Card Element you'll just need to collect the billing details separately (as outlined)

granite mortar
#

I am working on doing that

#

Thanks

mortal atlasBOT