kristin_EverCharge

[warm stump]

Hi there! Not quite sure I follow. An amount is required when you create a PaymentIntent, even if the funds are being captured manually later

[static geyser]

The issue we are running into is to capture the maximum amount our service can provide the authorization amount is so high we're worried about deterring users from using our service, as most of them will incur less than half that amount

We're using the PaymentRequest button, which I believe is incompatible with a SetupIntent

Is there a way for us to utilize the PaymentRequest button and capture all funds later without having an authorization amount that exceeds the fees most of our customers will incur?

[warm stump]

So it is possible to use the Payment Request Button with SetupIntents.

you'd pass the SetupIntent's client_secret instead, and use confirmCardSetup on the frontend (instead of confirmCardPayment)

does this change your question?

[static geyser]

I think that does answer the specific question I asked, thank you