#robert_iOS_EVcharge

1 messages · Page 1 of 1 (latest)

lunar needleBOT
crisp coral
#

Hey there

#

To clarify, you are using auth & capture here

#

You should see the same Webhooks fire regardless of Web versus iOS here

silent sable
#

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).

crisp coral
#

Yep so you are setting capture_method: 'manual'

silent sable
#

capture_method = manual, yes. I can post our intent.

crisp coral
#

Yep

#

Okay so

#

Can you better explain the confusion/issue here?

silent sable
#

{
"authorizationAmount": 2000,
"currency": "usd",
"ephemeralKey": "ek_test_...",
"paymentClientSecret": "pi_...",
"paymentIntentId": "pi_...",
"paymentCustomerId": "cus_..."
}

crisp coral
#

So the issue is that you aren't receiving a payment_method.attached event with your iOS flow, correct?

silent sable
#

Yes. We seem to be getting the wrong event back.

crisp coral
#

Well, not wrong, that event exists in your other flow too, you just handling it most likely.

silent sable
crisp coral
#

What iOS flow are you using?

#

Payment Sheet?

silent sable
#

yes

crisp coral
#

Okay and are you setting setup_future_usage on your PaymentIntent?

silent sable
#

we are not.

#

We don't have that in our web implementation.

crisp coral
#

Are you attaching the PaymentMethod ahead of time in your web implementation?

silent sable
#

Good question. I don't know.

crisp coral
#

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

silent sable
#

ok, finding one. Thanks so much for your help!

crisp coral
#

That's just a PaymentIntent

#

No PaymentMethod associated

#

Hasn't been confirmed

silent sable
#

ok, must not have completed. I'll look again.

crisp coral
#

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?

silent sable
#

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?

crisp coral
#

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

silent sable
#

Ok, thanks, that is EXTREMELY helpful.

crisp coral
#

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

silent sable
#

I'll hack on this today and come back. Thanks for having this Discord available. You've been very helpful.

crisp coral
#

That is the SetupIntent flow