johnwick_api

[hot kestrel]

👋 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/1409848143352303767

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

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.

• johnwick_api, 2 hours ago, 16 messages

[proper crow]

Hello for some reason the previous thread got locked and I could not reply there. Happy to explain my use scenario again if interested.

[crystal hull]

We close threads after ~30 minutes of inactivity. How can I help?

[proper crow]

Oh okay sure. So basically I'm working with Stripe payment intents. And I want to understand the use case where when the off_session=false and no request_three_d_secure=challenge is set, the payment intent sometimes goes into requires_action status

Basically this is my payload:

{
  "amount": "10000",
  "capture_method": "manual",
  "confirm": "true",
  "currency": "SGD",
  "customer": "cus_************",
  "description": "Payment ",
  "metadata": {
    "reference_id": "ST-************",
    "user_id": "************",
    "you_id": "Y-************"
  },
  "off_session": "false",
  "payment_method": "pm_1O**********",
  "payment_method_options": {
    "card": {
      "recipient_details": {
        "account_details": {
          "unique_identifier": {
            "identifier": "*5006"
          }
        },
        "first_name": "************",
        "last_name": "************"
      }
    }
  },
  "payment_method_types": {
    "0": "card"
  }
}```

but 3DS is triggered.

[crystal hull]

Well you can't completely disable 3DS if that is what you're asking. The default would be to still facilitate an auth challenge from the bank if they request it/test card requires it which is what the requires_action state signifies

The request_three_d_secure param is only if you want to force 3DS/auth

[proper crow]

Okay is there a way that I can replicate this scenario using any hardcoded or mock response? I want to replicate this scenario in my testing environment.

[crystal hull]

Which scenario exactly?

[proper crow]

I send off_session=false and nothing in request_three_d_secure but I want the PI status to be requires_action

this is the scenario I want to test

[crystal hull]

Then use a test card that requires 3DS: https://docs.stripe.com/testing#regulatory-cards

4000002760003184 should do it

[proper crow]

Can I know what the country is for this card?

is it a US based card?

[crystal hull]

Or add payment_method: 'pm_card_authenticationRequired' to your request payload

I think they're all US cards unless stated otherwise, no country specific 3DS cards

[proper crow]

Okay got it.

pm_card_authenticationRequired this will always trigger a 3DS?

[crystal hull]

Yes:

This card requires authentication on all transactions, regardless of how the card is set up.

[proper crow]

Sure will try and get back. It might take some time for me to test this flow. Would this thread be locked again after 30 mins?

[crystal hull]

Yes afraid so

[proper crow]

Will try to send a test message once in a while to keep it open just in case. Please don't mind the spam. Or mute it unless I tag you for any help pls 🙏🏻

[crystal hull]

Sure

[proper crow]

Also from the stripe dashboard, is there a way we can know the reason why it failed?

Does it mean the he entered a wrong OTP? or any other reason

[crystal hull]

We don't surface that detail in the API or Dashboard I'm afraid

[proper crow]

so there's no way I can find out 🙁

[crystal hull]

No

[proper crow]

Sure. Because I want to filter out how many are system errors and how many are customer errors. Got it

[crystal hull]

Well an auth failure would generally always be a customer error