#crazy-android-cvcrecollection
1 messages · Page 1 of 1 (latest)
@wintry shoal do you have an exact request id req_123 to share so I can look it up?
crazy-android-cvcrecollection
@proud breach I can make a new one now. Gimme 5 minutes
@wintry shoal any luck?
@proud breach since we using SDK, not sure where I can look the request id. Hovewer here is the screenshot(cannot copy this as a text, I can only copy 1 value if u need) of the request to the stripe
Okay so you're a Connect platform, you seem to be using Direct Charges https://stripe.com/docs/connect/direct-charges which is where you create the PaymentIntent and make all requests directly on one of your connected account.
The problem is that the PaymentMethod id pm_123 you are passing in that call was created on the platform back in August.
You can't use a platform PaymentMethod id in that case that will never work. It also has nothing to do with CVC recollection specifically
@wintry shoal does that make sense?
I'm trying to understand what is the correct way of dealing with it
What are you trying to do? As a Connect platform using Direct Charges you can not use a platform's scope PaymentMethod id, this would have never worked
and trying to understand what so different about
ConfirmPaymentIntentParams.create
and
ConfirmPaymentIntentParams.createWithPaymentMethodId
so how are you doing this usually? Are you familiar with the concept of cloning the PaymentMethod? Because that's what you are missing here: https://stripe.com/docs/payments/payment-methods/connect#cloning-payment-methods
ConfirmPaymentIntentParams.create I assume this collects brand new card details on the screen?
it confirms paymentintent with client secret and PaymentMethod.Type.Card
I guess I need first to speak to my team mate about this
yeah ultimately if you want to re-use an existing PaymentMethod from the platform you have to clone it first, based on the link I shared above
it just weird that it works fine without cvv recollection and using "create" method instead of createWithPaymentMethodId
Maybe if I will do one which works, maybe u can tell me what that difference between the two?
isn't this what I explained earlier?
ConfirmPaymentIntentParams.create I assume this collects brand new card details on the screen?
if you use that one, you don't reference any existing card PaymentMethod anywhere, you just show a UI that collects card details right?
The problem is that you are switching to the other that uses a previously saved card PaymentMethod and asks only for CVC and you're passing the wrong id
I recommend watching https://www.youtube.com/watch?v=ri07uPos1gs
I do reuse the old one saved paymentmethod. The whole point was to ask user for CVV everytime he uses the saved card
I'm sorry, a lot of this is completely abstract with no actionable information
Can you show me a clear example where you reused a PaymentMethod without CVC and it worked?
give me 2 minutes
Looking at your logs you clearly are using clonign in other places
So I do think your teammate have built all of this but maybe you don't know that part and didn't realize and just passed in the wrong id from the platform
So if you pause, watch that video first, you will understand what you need to do to re-use a previously saved card
Ok. I will watch the video and talk to backend/engineer manager.
but overall the flow is
- Find the PaymentMethod on the platform
pm_123 - Clone it on the connected account and get
pm_ABCinstead - Use that
pm_ABCwith the CVC
thanks