Transactions

Returns a list of Issuing Transaction objects. The objects are sorted in descending order by creation date, with the most recently created object appearing first.

Table Specific Information

Select

Server-Side Query Support

The driver uses the Stripe API to filter the results by the following columns and operators while the rest of the filter is executed client-side within the driver.

Id supports the following operator: =.
Card supports the following operator: =.
Cardholder supports the following operator: =.
Type supports the following operator: =.
Created supports the following operator: =.

You can select from Transactions with the following queries:

    SELECT * FROM Transactions WHERE Id = 'ipi_1ODMLL2eZvKYlo2CoarGZSSp'
    SELECT * FROM Transactions WHERE Card = 'card_1GhPzLJXTn'
    SELECT * FROM Transactions WHERE Cardholder = 'cardholder_12345'
    SELECT * FROM Transactions WHERE Type = 'purchase'
    SELECT * FROM Transactions WHERE Created >= '2024-01-01'

Columns


Name	Type	References	Description
Id [KEY]	String		Unique identifier for the object.
Amount	Integer		The transaction amount, which will be reflected in your balance.
AmountDetailsAtmFee	Integer		The fee charged by the ATM for the cash withdrawal.
AmountDetailsCashbackAmount	Integer		The amount of cash requested by the cardholder.
Authorization	String		The Authorization object that led to this transaction.
BalanceTransaction	String		Balance transaction that describes the impact on your account balance.
Card	String		The card used to make this transaction.
Cardholder	String		The cardholder to whom this transaction belongs.
Currency	String		Three-letter ISO currency code, in lowercase. Must be a supported currency.
MetadataAggregate	String		The set of key/value pairs that you can attach to a an object.
Type	String		The nature of the transaction.
Created	Datetime		Time at which the object was created. Measured in seconds since the Unix epoch.
Dispute	String		If youve disputed the transaction, the ID of the dispute.
Livemode	Boolean		Has the value true if the object exists in live mode or the value false if the object exists in test mode.
MerchantAmount	Integer		The amount that the merchant will receive, denominated in merchant_currency and in the smallest currency unit
MerchantCurrency	String		The currency with which the merchant is taking payment.
MerchantDataCategory	String		A categorization of the seller’s type of business.
MerchantDataCategoryCode	String		The merchant category code for the sellers business
MerchantDataCity	String		City where the seller is located
MerchantDataCountry	String		Country where the seller is located
MerchantDataName	String		Name of the seller
MerchantDataNetworkId	String		Identifier assigned to the seller by the card network.
MerchantDataPostalCode	String		Postal code where the seller is located
MerchantDataState	String		State where the seller is located
MerchantDataTerminalId	String		An ID assigned by the seller to the location of the sale.
MerchantDataURL	String		URL provided by the merchant on a 3DS request
NetworkDataAuthorizationCode	String		A code created by Stripe which is shared with the merchant to validate the authorization.
NetworkDataProcessingDate	String		The date the transaction was processed by the card network.
NetworkDataTransactionId	String		Unique identifier for the authorization assigned by the card network used to match subsequent messages, disputes, and transactions.
PurchaseDetailsFlight	String		Information about the flight that was purchased with this transaction.
PurchaseDetailsFuel	String		Information about fuel that was purchased with this transaction.
PurchaseDetailsLodging	String		Information about lodging that was purchased with this transaction.
PurchaseDetailsReceipt	String		The line items in the purchase.
PurchaseDetailsReference	String		A merchant-specific order number.
Token	String		Token object used for this transaction.
Wallet	String		The digital wallet used for this transaction.

Pseudo-Columns

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.