#guillermo-kuster_code
1 messages Ā· Page 1 of 1 (latest)
š Welcome to your new thread!
ā²ļø We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
ā±ļø We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
š This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1346558915004989501
š Have more to share? Add more details, code, screenshots, videos, etc. below.
Hey there
Hi
hello! looking into this now
just double checking, are both of y'all here for the same question?
How do I get Zip Activated on my Stripe Checkout
@loud stag is @unreal cloud with you or should i redirect them to a different thread?
it's not with me
@unreal cloud you can go to the #help channel to create a new thread for your question
Thanks
@loud stag have you looked at our documentation on test cards to see if there's one for your use case in there? i'm not familiar with the exact case you're referring to so i can dig in further, just want to understand what you've looked at or tried already
https://docs.stripe.com/testing
yes. I've looked into the documentation, and unfortunately, I couldn't find any credit card that does NOT allow multicapture capability when a payment intent is created in a sandbox environment.
https://docs.stripe.com/payments/multicapture?platform=web&ui=elements#availability
hmmmm ok, that makes sense....
I've tried several credit cards numbers, including Union Pay and JCB from https://docs.stripe.com/testing?testing-method=card-numbers
it could be that this is just a quirk of test mode / sandbox behavior, looking into that now
i'm guessing you're just looking for a way to test the failure scenario right? e.g. see what happens in your integration when multicapture is not available
that's correct. During Payment intent authorization I'm sending an option "request_multicapture": "if_available", and expanding the "latest_charge" in the response so I can check if the authorization succeeded with multicapture capabilities. I need to test the scenario when a credit card is introduced but is not "multicapture" available
ok cool. let me test a couple things, and then i might need to bug some colleagues for their thoughts on this as well
fyi i need to run but my colleague will take the thread from here!
perfect. Thanks for the support guys!
@wooden urchin let me know if you need any other details about my issue
Hi, catching up now
I was able to confirm that it behaves this way in test mode. Our team is discussing about documenting this better or fixing this behavior moving forward.
Can you confirm if 5555555555554444 shows the behavior you want?
sure, let me check ..
nope it doesn't work
this is part of the payload I received:
"installments": null,
"issuer": "CIAGROUP",
"last4": "4444",
"mandate": null,
"multicapture": {
"status": "available"
},
"network": "mastercard",
"network_token": {
"used": false
},
Can you share the request id with me? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Oh, that is supposed to work: https://docs.stripe.com/payments/multicapture?platform=web&ui=elements#availability
let me find the request id ..
I'll capture your feedback on this behavior to either get it documented or need to fix this
I do not need to request id as the above document shows that Mastercard would work for multicapture
yeah that's why I tried with JCB and Union Pay before contacted you guys. I thought those two might not allow multicapture based on the docs
but they did š¤·āāļø
I see. I've shared your feedback on this confusing behavior with the team. It does not appear that it can be tested today
ok no worries. Would this channel be kept alive in case you find a usable cc for this scenario tomorrow/next week?
It won't be tomorrow or next week. I won't be able to share a specific timeline.
ok I understand. Thanks anyway