#priyanka_26911

1 messages · Page 1 of 1 (latest)

quaint flareBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

coarse locust
#

👋 happy to help

#

is you account located in India?

quasi vortex
#

yes

coarse locust
#

please take a moment to read this doc

quasi vortex
#

but now I am trying in my local with sandbox mode

coarse locust
#

please go through the doc I sent you, since there are RBI related regulations that you need to take into account when doing recurring payments in India

quasi vortex
#

okay checking it

#

BUt we will be trying with us issued cards

coarse locust
#

even though

quasi vortex
coarse locust
#

@quasi vortex if you don't create e-mandates as the doc suggests you will always have to do 3DS even in off-session PaymentIntents

#

which btw I didn't ask but I assumed you were using the off-session: true parameter when creating the subsequent PaymentIntents right?

quaint flareBOT
quasi vortex
#

yes I am using off_session

coarse locust
#

for more clarity there are 2 off_session related parameters

#

1- setup_future_usage: "off_session" to setup the PM for future usage

#

2- off-session: true for the subsequent PaymetnIntents

quasi vortex
#

yes I has used setup_future_usage for payment intent API

#

got this response in next_action

"next_action": {
    "alipay_handle_redirect": null,
    "boleto_display_details": null,
    "card_await_notification": null,
    "cashapp_handle_redirect_or_display_qr_code": null,
    "display_bank_transfer_instructions": null,
    "konbini_display_details": null,
    "oxxo_display_details": null,
    "paynow_display_qr_code": null,
    "pix_display_qr_code": null,
    "promptpay_display_qr_code": null,
    "redirect_to_url": null,
    "type": "use_stripe_sdk",
    "use_stripe_sdk": {
        "source": "src_1ObgpKAXdNbPpzLyaxFNCmPj",
        "stripe_js": "https://hooks.stripe.com/redirect/authenticate/src_1ObgpKAXdNbPpzLyaxFNCmPj?client_secret=src_client_secret_eD0XYbXexMy0ebkdbTq9z8rG&source_redirect_slug=test_YWNjdF8xTnM3TERBWGROYlBwekx5LF9QUVh2QnZMa2ZYSThzQzZiaUV4T24zeXZxQXZ6YzVD0100GWE6uBrK",
        "type": "three_d_secure_redirect"
    },
    "verify_with_microdeposits": null,
    "wechat_pay_display_qr_code": null,
    "wechat_pay_redirect_to_android_app": null,
    "wechat_pay_redirect_to_ios_app": null
},
"object": "payment_intent",
"on_behalf_of": null,
"payment_method": "pm_1ObgoeAXdNbPpzLyRJG2sLvc",
"payment_method_configuration_details": {
    "id": "pmc_1NsOzzAXdNbPpzLylajjDC7F",
    "parent": null
},
📎 message.txt
dense mason
#

sounds normal, what's wrong with that?

quasi vortex
#

status I have recived as requires_Action and what is this property use_stripe_sdk

dense mason
#

it doesn't matter, it's something that is used by stripe.js when you confirm the PaymentIntent

#

if you want to test the second PaymentIntent not requiring 3DS you need to specifcally use the "3155" card

image.png
quasi vortex
#

yes with this card..its working fne and after using off_session property added to payment intent

dense mason
#

great

quasi vortex
#

then without set up intent..i can directly use payment intent with off_session set to true right ?

dense mason
#

no

quasi vortex
#

because I see set up intent id is not used anywhere

dense mason
#

you would set up the card first with the SetupIntent, and then later you can do off-session payments without 3DS

dense mason
quasi vortex
#

without doing set up intent ..i can just use this to create payment method and then use that payment method id in payment intent with off_session = true

is this correct ?

PaymentMethod paymentMethod = PaymentMethod.create(params);

dense mason
#

no