Skip to main content
The /transactions resource represents the electronic messages that carry information used for payment processing. A transaction usually originates when a cardholder attempts to make a payment, either online or at a physical point of sale. You can receive information about transactions as they occur by configuring webhooks. Learn about configuring webhooks in the About Webhooks guide. See the transaction events for which you can set up webhooks in the Event Types API reference page. You can also retrieve transactions associated with specific cards, merchants, and account holders using the endpoints described here. For an overview of transactions and the transaction object, including the complete list of transaction response codes, see About Transactions.
Tip Use the /transactions endpoint to retrieve smaller datasets (up to one page). For best performance when requesting larger datasets, use the DiVA API.

Transaction object

Transactions are represented by the transaction object. The Marqeta platform creates a separate transaction object for each transaction message received from the card network. The attributes of a given transaction object depend on the transaction type. This section documents all fields that might be included in a transaction object.

Available operations