#robert_iOS_EVcharge
1 messages · Page 1 of 1 (latest)
Hey there
To clarify, you are using auth & capture here
You should see the same Webhooks fire regardless of Web versus iOS here
I don't know what that means. auth & capture. We want pre-auth then later capture (EV charging, show possible largest amount, then charge for power they used).
Yep so you are setting capture_method: 'manual'
capture_method = manual, yes. I can post our intent.
{
"authorizationAmount": 2000,
"currency": "usd",
"ephemeralKey": "ek_test_...",
"paymentClientSecret": "pi_...",
"paymentIntentId": "pi_...",
"paymentCustomerId": "cus_..."
}
So the issue is that you aren't receiving a payment_method.attached event with your iOS flow, correct?
Yes. We seem to be getting the wrong event back.
Well, not wrong, that event exists in your other flow too, you just handling it most likely.
yes
Okay and are you setting setup_future_usage on your PaymentIntent?
Are you attaching the PaymentMethod ahead of time in your web implementation?
Good question. I don't know.
Feel free to give me a PaymentIntent ID from your web implementation and I can look at exactly what you are doing
That might be easiest
ok, finding one. Thanks so much for your help!
ok, must not have completed. I'll look again.
So looking at a different one on that account, looks like you are collecting card details ahead of time via a SetupIntent and then charging them later
Is this the expected flow for your model?
You aren't expecting to authorize at time of PaymentMethod collection?
I see those events for setup_intent. Both the cloud guy and me didnt' code the existing web flow.
We expect to pre-auth for a value then charge later. Are we not doing that with our web implem?
Doesn't look like it no
What you are doing in livemode in that account is collecting card details up front via a SetupIntent and then charging that card later
You aren't using capture_method: manual
Ok, thanks, that is EXTREMELY helpful.
If that is the flow you want for iOS then all you need to do is create a SetupIntent and pass the SetupIntent's client secret to PaymentSheet config
And the eph key and Customer ID
And then you create/confirm the PaymentIntent later server-side like you are doing with the web flow
But I would recommend syncing with your team for exactly what you want here to make sure you are aligned lol
I'll hack on this today and come back. Thanks for having this Discord available. You've been very helpful.
That is the SetupIntent flow