newtreyes

[silent gyro]

Hey

[magic tiger]

@silent gyro Hello, Sir

[silent gyro]

Yep looks like the PaymentMethod type that you are dealing with is requiring phone and you aren't passing that per the error

[magic tiger]

This may be a problem on my side. It looks as if it's asking for the phone

which I am not providing

Yes!!!

Now, qq: previously we were using the Card Element

and the Card Element didn't require the phone

Do we need to request the phone now to use the Payment Element?

[silent gyro]

What payment method type are you creating?

Like Card doesn't require phone

[silent gyro]

Hmmm that should not require phone....

Is this the standard flow or are you using deferred-intent?

[magic tiger]

Deferred Intent

[silent gyro]

Hmm interesting.

Let me repro, one sec.

[magic tiger]

This is the PoC we are working on. At this point, the user has entered all the required info and we are about to create the payment method and then process the payment.

[silent gyro]

That isn't Address Element is it?

[magic tiger]

It is not

[silent gyro]

Cool, one sec.

[magic tiger]

That's the Payment Element. The rest of the fields are ours.

[silent gyro]

Okay yeah to me this is a bug. You shouldn't need phone so we shouldn't error there. I'll file that. That said, try doing fields: { billingDetails: { email: 'never', address: { postalCode: 'never', country: 'never' } } },

[magic tiger]

trying

Nice

it worked

thank you, Sir

[silent gyro]

👍