#daniyal_11692

1 messages · Page 1 of 1 (latest)

topaz thicketBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

static swift
#

Hello

#

Are you using the deferred-intent flow here?

#

Basically how are you rendering Payment Element?

brazen loom
#

paymentElement.mount('#payment-element');

static swift
#

How do you create your Elements object?

#

Do you pass a clientSecret to it, or no?

brazen loom
#

yes. const elements = stripe.elements({ clientSecret, stripeElementOptions });

static swift
#

Does that clientSecret come from a SetupIntent?

#

I assume yes

#

As that would be the only way this would show $0

brazen loom
#

yes

static swift
#

Gotcha then yeah there isn't a way to change that from showing $0 in this flow.

#

Since you aren't actually charging at that point -- you are just collecting the PaymentMethod.

#

Are you charging the customer immediately? If so, you may want to consider adjusting your flow and not using a SetupIntent.

#

As it is really only designed for setting up a PaymentMethod for future use.

brazen loom
#

can i hide this payment as it can confuse the customer ?

#

0.00 looks a bit confusing

static swift
#

No, unfortunately we have extremely limited control of what shows in the Google Pay payment modal.