#walpoletim-paymentelement
1 messages · Page 1 of 1 (latest)
how does this tie into the <PaymentsElement /> react node though
if U use both I get error saying not able to create multiple nodes
you pass it into <PaymentElement options={...} /> though I don't have a specific example to hand right now
could you share the exact code and error message?
I tried this <PaymentElement id="payment-element" onChange={handleChange} options={{ fields: { billingDetails: { // name: 'never', // email: 'never', postalCode: 'never' } }} } />
but this still presented the postcode element
postalCode should be inside an address object like the structure in the reference I linked
not sure what you mean
wouldn't it be
billingDetails: {
address: {
postalCode:"never"
}
}
?
yeah because name and email are top level
postal code is in the address object, like it says in the link I posted