ds-dev | Stripe Developers | Page 1

jade mangoBOT Sep 23, 2022, 7:37 AM

#

abstract kite Sep 23, 2022, 7:38 AM

#

Can you share the request ID (req_xxx) you try to create a charge? Here’s how you can find it: https://support.stripe.com/questions/finding-the-id-for-an-api-request

Finding the ID for an API Request : Stripe: Help & Support

Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.

rancid mango Sep 23, 2022, 7:42 AM

#

Request_id is req_U92QQG0kX6uqKU

#

I try to setup subscription

abstract kite Sep 23, 2022, 7:52 AM

#

I see that you created two subscriptions with 27.97 USD:

#

They both of charges of 27.97 USD

rancid mango Sep 23, 2022, 7:54 AM

#

authorization requests getting 1 second delay

#

#

#

these subscriptions as you shown early created with 2 minutes interval - this is simply another attempt

#

when I make request https://dashboard.stripe.com/logs/req_U92QQG0kX6uqKU

this make 2 card authorization attempts

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

#

when I make same request https://dashboard.stripe.com/logs/req_P6PF7p7eT6HtTr

I get only one authorization request(that ok)

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

#

two absolutely identical requests on the same user with the same card generate a different number of authorization requests

abstract kite Sep 23, 2022, 8:07 AM

#

I'll be stepping away. My colleague @wispy mortar will be taking over

wispy mortar Sep 23, 2022, 8:18 AM

#

Hi! I'm taking over this thread. Give me a few minutes to catchup.

queen finch Sep 23, 2022, 8:27 AM

#

at a guess, it's probably just that we are retrying the authorisation on the merchant's side, which is something we do to try to optimised declines by retrying the authorisation on the network with slightly different parameters (https://stripe.com/payments/authorization)

#

it's not uncommon for payment processors to do that as far as I know

rancid mango Sep 23, 2022, 8:31 AM

#

but this behavior is not constant

sometimes happens often, today not once - what does it depend on?

#

can we managed this behavior?

queen finch Sep 23, 2022, 8:36 AM

#

rancid mango but this behavior is not constant sometimes happens often, today not once - wha...

it's all internal to the payment processor(which happens to be Stripe in this case, but you're using Issuing so your cards are likely going to be actually charged by multiple merchants and payment processors and they may or may not do their authorisation attempts with retries, I suppose).

queen finch Sep 23, 2022, 8:36 AM

#

rancid mango can we managed this behavior?

no

#

what actual problem is this causing you exactly?

rancid mango Sep 23, 2022, 8:38 AM

#

maybe scare the users with attempts to double charge

#

or increase decline rate of our descriptor in payment systems

#

that is not good

queen finch Sep 23, 2022, 8:40 AM

#

I don't think those are likely outcomes, sorry

#

anyway I checked and for req_U92QQG0kX6uqKU, yes, our "adaptive acceptance" system was used there so we retried the declined charge internally, so my guess there was correct. As I said, as the issuer this is just behaviour you might see, it's not uncommon for a merchant/payment processor to get a decline and immediately retry it, or to retry it with different "ISO8583" parameters, or even for the end-customer to get the decline and then try again.

#ds-dev