#crazy-android-cvcrecollection

1 messages · Page 1 of 1 (latest)

white mistBOT
proud breach
#

@wintry shoal do you have an exact request id req_123 to share so I can look it up?

#

crazy-android-cvcrecollection

wintry shoal
#

@proud breach I can make a new one now. Gimme 5 minutes

proud breach
#

@wintry shoal any luck?

wintry shoal
#

@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

proud breach
#

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?

wintry shoal
#

I'm trying to understand what is the correct way of dealing with it

proud breach
#

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

wintry shoal
#

and trying to understand what so different about
ConfirmPaymentIntentParams.create
and
ConfirmPaymentIntentParams.createWithPaymentMethodId

proud breach
#

ConfirmPaymentIntentParams.create I assume this collects brand new card details on the screen?

wintry shoal
#

it confirms paymentintent with client secret and PaymentMethod.Type.Card

#

I guess I need first to speak to my team mate about this

proud breach
#

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

wintry shoal
#

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?

white mistBOT
proud breach
#

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

wintry shoal
proud breach
#

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?

wintry shoal
#

give me 2 minutes

proud breach
#

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

wintry shoal
#

Ok. I will watch the video and talk to backend/engineer manager.

proud breach
#

but overall the flow is

  1. Find the PaymentMethod on the platform pm_123
  2. Clone it on the connected account and get pm_ABC instead
  3. Use that pm_ABC with the CVC
wintry shoal
#

thanks