#.cyberscribe

1 messages · Page 1 of 1 (latest)

candid harborBOT
wicked mountain
#

hi there!

#

are you using the Payment Element to collect the payment information?

visual patrol
#

right

#

the jsx that renders the form is:

                    <CheckoutForm stripePromise={props.stripePromise} clientSecret={props.clientSecret} loggedIn={props.loggedIn} />
                </Elements>```
#

I'm not sure if that is "Embedded form" or "Custom flow"

wicked mountain
#

and do you see a name field in the Payment Element?

visual patrol
#

Yes indeed

#

but user can leave it blank

#

(one just did)

#

any ideas? 🙂

wicked mountain
visual patrol
#

yes that looks like what we are using

wicked mountain
#

and which payment method are you using? for example for cards payment there would be no name field at all.

visual patrol
#

ah, I see the issue now--we had Google Pay also active, so it was displaying a name field for Google Pay but for cards it could be left blank

#

Can we request the cardholder name in the form? or do we have to request it outside the form?

#

I see a customer name field in risk insights -- is this coming from a field in the payment or in the customer?

wicked mountain
#

if you always want to collect a name, then you would need to add your own input field on the page.

visual patrol
#

ok, I see

#

and this gets sent with the rest of the form if wrapped in the <Elements> ?

wicked mountain
visual patrol
#

got it, thanks. so like:

  '{CLIENT_SECRET}',
  {
    payment_method: {
      card: cardElement,
      billing_details: {
        name: 'soma'
      }
    }
  }
);```
wicked mountain
visual patrol
#

great, thanks

#

now that I know it was Google Pay showing the name field I can make it work and make it required for credit cards

wicked mountain
#

perfect!

visual patrol
#

thanks so much!