#scootee

1 messages · Page 1 of 1 (latest)

hybrid fulcrumBOT
spare zealot
#

Hello! Not sure what you mean by search. Can you tell me more about what you're trying to do?

stark badger
#

for example, I'm using the stripe-php library to do the following, find payment intents of $status

$stripe->paymentIntents->search([
                'query' => "status:\"$status\"",
            ]);
#

is there a way to query for payment intents that have 3D secure protection:

spare zealot
stark badger
#

I see

#

follow up question, this payment intent we created in test mode had 3D secure attempt recorded: pi_3NOlvjDSR3PVsRbH21pLvH0k

#

do you know why it isn't the case in any production payments? example: pi_3NOnw8DSR3PVsRbH16e0v2ZI

spare zealot
#

Looks like nothing on the production Payment Intent requested or required 3D Secure, or the card issuer doesn't support 3D Secure, so 3D Secure didn't happen.

stark badger
#

we're creating the payment intent with the following option:

  "payment_method_options": {
    "card": {
      "request_three_d_secure": "any"
    }

from the docs:
When you set request_three_d_secure to any, Stripe requires your customer to perform authentication to complete the payment successfully if 3DS authentication is available for a card. If it’s not available for the given card, the payment proceeds normally.

spare zealot
#

Yep, request_three_d_secure is just that, a request. There's no way to force 3D Secure.

stark badger
#

gotcha, we're just wondering if we're doing something incorrect since we can't seem to find a customer with 3D secure attempted like we had seen in test mode

spare zealot
#

Are most of your customers in the US?

stark badger
#

yes

spare zealot
#

That's probably why. 3D Secure is mostly not a thing in the US.

#

Some card issuers support it, but many don't.

#

Looks like there are some though. pi_3NOoWZDSR3PVsRbH2wUkaEm6 for example.

#

If you want to find them the easiest way would be to look for payment_intent.requires_action Events.

stark badger
#

interesting

#

thank you for this information, we'll investigate further on our end