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.

List transactions

Action: GET Endpoint: /transactions List all transactions. By default, this endpoint returns transactions conducted within the last 30 days. To return transactions older than 30 days, you must include the start_date and end_date query parameters in your request. By default, GET /transactions returns transactions having either PENDING or COMPLETION states. This endpoint supports field filtering and pagination.

URL query parameters

Response body

Sample response body

JSON

List transactions for a funding account

Action: GET Endpoint: /transactions/fundingsource/{funding_source_token} List transactions for a specific funding source. By default, this endpoint returns transactions conducted within the last 30 days. To return transactions older than 30 days, you must include the start_date and end_date query parameters in your request. By default, GET /transactions/fundingsource/{funding_source_token} returns transactions having either PENDING or COMPLETION states. This endpoint supports field filtering and pagination.

URL path parameters

URL query parameters

Response body

Retrieve transaction

Action: GET Endpoint: /transactions/{token} Retrieve a specific transaction. Include the token path parameter to identify the transaction.
Note Transactions are not available in real time via this endpoint, and typically appear after 30 seconds. On occasion, a transaction may require up to four hours to appear.

URL path parameters

URL query parameters

Response body

See Transaction object.

Sample response body

JSON
Action: GET Endpoint: /transactions/{token}/related List all transactions related to the specified transaction. By default, this endpoint returns transactions conducted within the last 30 days. To return transactions older than 30 days, you must include the start_date and end_date query parameters in your request. By default, this endpoint returns transactions of any state. To return transactions in specific states, you must include the state query parameter in your request. This endpoint supports field filtering and pagination.

URL path parameters

URL query parameters

Response body

Sample response body

JSON