AQZ-issuing-event

[haughty cosmos]

Hey can you share an evt_xxx ID?

[naive gate]

1 min

For example
https://dashboard.stripe.com/acct_1LHY9ZBLmgC51pn4/test/issuing/authorizations/iauth_1LQnqZBLmgC51pn4dxUcevEK

[haughty cosmos]

Can you share the Event?

[naive gate]

Our clients ask us to display the reason for declining authorization. How do we know if it is rejected on the stripe side

[haughty cosmos]

Can you share the ID of the Event you're referring to? evt_xxx?

I guess it's https://dashboard.stripe.com/test/events/evt_1LQnqaBLmgC51pn4nS0VLFoG ?

[naive gate]

For example

Can you answer my question ?
Can we find out the reason for the rejection if the authorization was rejected not by stripe?

[haughty cosmos]

I'm checking, please be patient

To be clear, we only reject the authorisation if you don't respond the to issuing_authorization.request event promptly: https://stripe.com/docs/issuing/controls/real-time-authorizations#:~:text=Your webhook must approve or decline each authorization before responding to the incoming webhook request. If Stripe does not receive your approve or decline request within 2 seconds%2C the Authorization is automatically approved or declined based on your timeout settings.

[naive gate]

https://stripe.com/docs/issuing/purchases/authorizations

Stripe checks that the balance used for Issuing has sufficient funds, that the card is active, and that your spending controls allow the authorization.

What if, for example, this check failed?

[haughty cosmos]

I don't see that on the link you shared

Are you handling those issuing_authorization.request events?

[naive gate]

We are here we have not received any webhook

[haughty cosmos]

But you are receiving them. See: https://dashboard.stripe.com/test/events/evt_1LQnqaBLmgC51pn4nS0VLFoG

[naive gate]

No such notification: 'evt_1LQnqaBLmgC51pn4nS0VLFoG'

[haughty cosmos]

That's the issuing_authorization.created event for the iauth_xxx object you shared with me

I guess you're signed into the wrong account on Dashboard

[naive gate]

Ok

I received issuing_authorization.created event. But how i know decline reason by stripe?

@haughty cosmos

[haughty cosmos]

Please stop tagging me

[naive gate]

I've tagged only once 😅

[haughty cosmos]

There won't be a decline at that point. It's up to you to action the request:

When Stripe receives an authorisation request, we send an issuing_authorization.created webhook event. If you approve the authorisation, we deduct the amount from your Issuing balance and hold it in reserve until the authorisation is either captured, voided, or expired without capture. If you decline the authorisation, the status is set to closed and we don’t place any holds.

Either way we don't store a 'decline' reason on the object: https://stripe.com/docs/api/issuing/authorizations/object

To be clear this isn't a payment attempt decline

[naive gate]

Then why stripe checks this ?

We don't seem to understand each other

I'm trying to explain again

[haughty cosmos]

Because your Issuing user is attempting to make a payment, this is the authorisation for that request. This is not the actual payment attempt across the networks

We wouldn't create an authorisation for your approval if there was insufficient balance

[naive gate]

For example

1. Account balance is 100$
2. Authorization for the amount of 105 has been created / Card is closed / Limit has been exceeded
3. We have not accepted the webhook issuing_authorization.request
4. We have accepted the webhook
   issuing_authorization.created

Question:
Is it possible to know decline reason ?

[haughty cosmos]

There's not, no

[naive gate]

pardon ?

[haughty cosmos]

You asked if its possible to know the decline reason, and I said it's not

[naive gate]

Finally got an answer, thanks

[haughty cosmos]

I answered you earlier:

[naive gate]

Okay

It would be nice if we found out why the authorization was rejected by the stripe

[haughty cosmos]

Which provider?

[naive gate]

stripe

[haughty cosmos]

As I've explained, this isn't a bank/issuer authorisation. This is an authorisation request by your Issuing user which you need to action

[naive gate]

I also explained to you about the case where we don't receive authorization request to approve/decline

[haughty cosmos]

Maybe there's some detail on the request_history hash that might be relevant: https://stripe.com/docs/api/issuing/authorizations/object#issuing_authorization_object-request_history-reason

[naive gate]

ok thanks

[haughty cosmos]

Also, this likely explains the webhook/event behaviour: https://stripe.com/docs/issuing/controls/spending-controls#:~:text=Spending controls run before real-time authorizations and can decline a purchase before the issuing_authorization.request is sent%2C resulting in a declined issuing_authorization.created event.

In the case of iauth_1LQnqZBLmgC51pn4dxUcevEK, seems the card was inactive (from the webhook event: evt_1LQnqaBLmgC51pn4nS0VLFoG)

request_history: [
      {
        amount: 1,
        amount_details: {
          atm_fee: null
        },
        approved: false,
        created: 1659080579,
        currency: "usd",
        merchant_amount: 1,
        merchant_currency: "usd",
        reason: "card_inactive"
      }
    ],

Hopefully that helps unblock you!

[naive gate]

I got an answer to all my questions, thank you for your help! Have a nice day