After an authorization is approved and is captured, the status on the authorization is set to closed and a Transaction object is created. This normally happens within 24 hours; however hotels, airlines, and car rental companies are able to capture up to 31 days after authorization.
When an authorization is captured, two things happen.
The status on the authorization is set to closed, releasing the purchase amount held by that authorization. A balance transaction of type issuing_authorization_release is created to represent this.
Spending controls, real time authorization controls, and card status (whether a card is active or not) don’t apply for capture. They can be used to determine whether authorizations are approved, but captures for approved authorizations always succeed.
Handling other transactions
In addition to regular transactions, there are a few other cases that you should be ready to handle.
Merchants might initiate a capture despite receiving a declined authorization, or even without an authorization. In either case, Stripe creates transaction objects, and we deduct the captured amount from your Issuing balance and send it to the merchant. If we didn’t receive an authorization request for the capture, the transaction objects won’t have a linked authorization object.
Sometimes these transactions correspond to legitimate purchases. In other cases, these transactions are unauthorized purchases or a result of fraudulent behavior. It’s up to you (or your cardholder) to recognize when this is the case and dispute illegitimate transactions. Because some of these transactions are legitimate, you can’t block them.
An example of a legitimate transaction without an authorization is a payment on an airplane. The terminals used on airplanes are usually not connected to the internet. Purchases on flights are not able to create authorizations and instead create transactions that are sent after the plane lands.
