#kratos6753

1 messages · Page 1 of 1 (latest)

warm shellBOT
trail lynx
#

Hi there!

#

What exactly is different? And why is that an issue?

near radish
#

stripe payment_intents create --amount=20000 --currency=usd -d "payment_method_types[]"=card --customer=cus_NKXxynp7GEG9P6 --capture-method=manual --off-session=true --confirm=true --payment-method=pm_1MbefuA7BWdKIiAUHqoaGbrg --return-url=https://example.com/success --statement-descriptor="xxxx" -d "transfer_data[destination]"="acct_16nyiVHY17QvtQWI"

#

stripe cli version - 1.8.11

#

here payment intent created is pi_3MbgV1A7BWdKIiAU1peWA3bF, which is uncaptured one, which is what is expected from the payment method used

#

But with python api - args = { 'amount': amount, 'currency': 'usd', 'confirm': True, 'description': description, 'customer': stripe_customer_id, 'capture_method': 'manual', 'statement_descriptor': statement_descriptor, 'payment_method_types': ["card"], 'application_fee_amount': 0, 'transfer_data': {'destination': stripe_account_id}, 'payment_method': payment_method } stripe.PaymentIntent.create(**args)

#

the payment intent created in this way, requires further action. But why is that? because the card used should not ask for 3ds in bothways, right

#

do you want request ids for both these requests?

trail lynx
#

Can you share the PaymentIntent ID (pi_xxx) for both?

near radish
#

for cli case - pi_3MbgV1A7BWdKIiAU1peWA3bF

#

for app case - pi_3Mbeg4A7BWdKIiAU01kLhh8P

trail lynx
#

Thanks! Give me a few minutes to look into this.

near radish
#

sure

trail lynx
#

pi_3Mbeg4A7BWdKIiAU01kLhh8P doesn't have off_session: "true"

near radish
#

yes, but using setup intents I have already authenticated, right?

#

also off_session: true is by default I believe

trail lynx
#

Yes, but you need to set off_session: "true" when you create the PaymentIntent.

#

also off_session: true is by default I believe
no I don't think so.

near radish
#

ok sure, will try that and let you know. Thanks soma.