#Ernesto Muñoz
distant crystal
shell charm
Hi 👋
This happens when a source expires.
wintry iris
👋 stepping in
Sounds like separate auth & capture to me
Where you auth'd but didn't capture after 7 days
Feel free to share an example
magic snow
Hi @shell charm
Sorry for this question, but, in this case what is the 'source'? the card?
wintry iris
Snufkin is referring to a Source object, which could be a Card but most likely in this case is some other type of payment method
If that is what caused this expiration message
magic snow
But the balance transaction with this status is from card issuing not from payment method
wintry iris
Can you provide an example balance transaction ID?
Really hard to talk in abstracts here
As this could relate to various things
magic snow
{
"id": "txn_xxx",
"object": "balance_transaction",
"amount": 5748,
"available_on": 1665472317,
"created": 1665472317,
"currency": "usd",
"description": "Released hold for authorization due to expiration",
"exchange_rate": null,
"fee": 0,
"fee_details": [
],
"net": 5748,
"reporting_category": "issuing_authorization_release",
"source": "iauth_xxx",
"status": "available",
"type": "issuing_authorization_release"
}
There is
wintry iris
Okay so we discuss these Issuing Authorizations here: https://stripe.com/docs/issuing/purchases/authorizations#authorization-updates
Basically this means that the Issuing Card was Authorized to make a purchase, but that authorization was never captured by the merchant. So the authorization was released.
magic snow
Oh ok, make sense now.
by the way, do you know what is the max time that the merchant has to capture the authorization? Or it depends on each merchant?
wintry iris
That would depend on the merchant. Usually authorizations can be held up to 7 days.
magic snow
Ok thanks for help 🙌 , really appreciated