Refunds are transactions with type of refund. Refunds can also be reversed and can be identified as a transaction with type of refund with a negative amount.

When we create a transaction representing a refund, credit, or refund reversal, we try to link it to the original authorization. In some cases, like when a card has been credited rather than refunded, this isn’t possible. In these cases, the authorization field of the transaction is set to null, and the transaction won’t be linked to the authorization.

{
  "id": "ipi_1GTG10EEsyYlpYZ9VJn2xV3B",
  "object": "issuing.transaction",
  "amount": 100,
  "authorization": "iauth_1GBZQyEEsyYlpYZ9255L8GQC",
  "balance_transaction": null,
  "card": "ic_1GBZQJEEsyYlpYZ99v6rq38S",
  "cardholder": null,
  "created": 1585783834,
  "currency": "usd",

Merchants can capture an amount less than the amount that has been authorized. As a result, a transaction may show an amount less than on the linked authorization.

The full amount of the authorization is not always captured. As a result, a transaction may show an amount less than on its linked authorization. In this case, the amount of funds held by Stripe for an authorization is the difference of the authorization amount and all linked capture transaction amounts.

Businesses in some merchant categories (including vehicle rentals, bars and restaurants, and ground transportation) won’t know the final transaction amount at the time of authorization. These businesses can authorize a card for an amount and then capture funds greater than that amount.

For example, a restaurant often authorizes a charge for the bill amount and then captures an amount that includes the tip. In this case, the authorized amount is a relatively close estimate of the amount to be captured. However, in a case such as ground transportation, the authorized amount is typically a minimal amount, whereas the captured amount reflects the actual journey taken by the cardholder.

Some merchant categories (including airlines, cruise lines, or railway merchants) may authorize a transaction and then capture funds multiple times. An example of this is when you purchase three items but they ship separately when available. This results in the creation of multiple issuing_authorization.updated webhook events and multiple transactions.

Merchants may initiate a capture despite receiving a declined authorization, or even without an authorization. In either case, transaction objects are created, and the captured amount is debited from your balance and sent to the merchant. If no authorization was requested, 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 is up to you (or your cardholder) to recognize when this is the case and dispute illegitimate transactions.

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.

{
  "id": "ipi_1GTG10EEsyYlpYZ9VJn2xV3B",
  "object": "issuing.transaction",
  "amount": -100,
  "authorization": null,
  "balance_transaction": null,
  "card": "ic_1GBZQJEEsyYlpYZ99v6rq38S",
  "cardholder": null,
  "created": 1585783834,
  "currency": "usd",