Transactions

Transactions represent changes to a FinancialAccount’s balance.

Endpoints

GET/v1/treasury/transactions/:id

GET/v1/treasury/transactions

The Transaction object

Attributes

idstring
Unique identifier for the object.

objectstring
String representing the object’s type. Objects of the same type share the same value.

amountinteger
Amount (in cents) transferred.

balance_impactobject
The change made to each of the FinancialAccount’s sub-balances by the Transaction.

createdtimestamp
Time at which the object was created. Measured in seconds since the Unix epoch.

currencyenum
Three-letter ISO currency code, in lowercase. Must be a supported currency.

descriptionstring
An arbitrary string attached to the object. Often useful for displaying to users.

entriesnullable objectExpandable
A list of TransactionEntries that are part of this Transaction. This cannot be expanded in any list endpoints.

financial_accountstring
The FinancialAccount associated with this object.

flownullable string
ID of the flow that created the Transaction.

flow_detailsnullable objectExpandable
Details of the flow that created the Transaction.

flow_typeenum

Type of the flow that created the Transaction.

Possible enum values

credit_reversal

The Transaction is associated with a CreditReversal.

debit_reversal

The Transaction is associated with a DebitReversal.

inbound_transfer

The Transaction is associated with an InboundTransfer.

issuing_authorization

The Transaction is associated with an Issuing authorization.

other

The Transaction is associated with some other money movement not listed above.

outbound_payment

The Transaction is associated with an OutboundPayment.

outbound_transfer

The Transaction is associated with an OutboundTransfer.

received_credit

The Transaction is associated with a ReceivedCredit.

received_debit

The Transaction is associated with a ReceivedDebit.

livemodeboolean
Has the value true if the object exists in live mode or the value false if the object exists in test mode.

statusenum

Status of the Transaction.

Possible enum values

open

The initial state for all Transactions. The Transaction results in updates to the sub-balance amounts, but the current balance is not affected until the Transaction posts.

posted

Funds have successfully entered or left the account. The current balance was affected.

void

The Transaction never impacted the balance. For example, a Transaction would enter this state if an OutboundPayment was initiated but then canceled before the funds left the account.

status_transitionsobject
Hash containing timestamps of when the object transitioned to a particular status.

The Transaction object

{
  "id": "trxn_1MtkYw2eZvKYlo2ClMGIO54z",
  "object": "treasury.transaction",
  "amount": -100,
  "balance_impact": {
    "cash": -100,
    "inbound_pending": 0,
    "outbound_pending": 100
  },
  "created": 1680755802,
  "currency": "usd",
  "description": "Jane Austen (6789) | Outbound transfer | transfer",
  "financial_account": "fa_1MtkYw2eZvKYlo2CrqmzUo3O",
  "flow": "obt_1MtkYw2eZvKYlo2CqsyBpQts",
  "flow_type": "outbound_transfer",
  "livemode": false,
  "status": "open",
  "status_transitions": {
    "posted_at": null,
    "void_at": null
  }
}

Retrieve a Transaction

Retrieves the details of an existing Transaction.

Parameters

No parameters.

Returns

Returns a Transaction object if a valid identifier was provided. Otherwise, returns an error.

GET /v1/treasury/transactions/:id

Server-side language

curl https://api.stripe.com/v1/treasury/transactions/trxn_1MtkYw2eZvKYlo2ClMGIO54z \
  -u "sk_test_4eC39Hq...arjtT1zdp7dcsk_test_4eC39HqLyjWDarjtT1zdp7dc:"

Response

{
  "id": "trxn_1MtkYw2eZvKYlo2ClMGIO54z",
  "object": "treasury.transaction",
  "amount": -100,
  "balance_impact": {
    "cash": -100,
    "inbound_pending": 0,
    "outbound_pending": 100
  },
  "created": 1680755802,
  "currency": "usd",
  "description": "Jane Austen (6789) | Outbound transfer | transfer",
  "financial_account": "fa_1MtkYw2eZvKYlo2CrqmzUo3O",
  "flow": "obt_1MtkYw2eZvKYlo2CqsyBpQts",
  "flow_type": "outbound_transfer",
  "livemode": false,
  "status": "open",
  "status_transitions": {
    "posted_at": null,
    "void_at": null
  }
}

List all Transactions

Retrieves a list of Transaction objects.

Parameters

financial_accountstringRequired
Returns objects associated with this FinancialAccount.

createdobject
Only return Transactions that were created during the given date interval.

order_byenum
The results are in reverse chronological order by created or posted_at. The default is created.
Possible enum values
created
Timestamp describing when the Transaction was created.
posted_at
Timestamp describing when the Transaction was posted.

statusenum

Only return Transactions that have the given status: open, posted, or void.

Possible enum values

open

The initial state for all Transactions. The Transaction results in updates to the sub-balance amounts, but the current balance is not affected until the Transaction posts.

posted

Funds have successfully entered or left the account. The current balance was affected.

void

The Transaction never impacted the balance. For example, a Transaction would enter this state if an OutboundPayment was initiated but then canceled before the funds left the account.

status_transitionsobject
A filter for the status_transitions.posted_at timestamp. When using this filter, status=posted and order_by=posted_at must also be specified.

More parameters

ending_beforestring

limitinteger

starting_afterstring

Returns

A dictionary with a data property that contains an array of up to limit Transactions, starting after Transaction starting_after. Each entry in the array is a separate Transaction object. If no more Transactions are available, the resulting array will be empty.

GET /v1/treasury/transactions

Server-side language

curl -G https://api.stripe.com/v1/treasury/transactions \
  -u "sk_test_4eC39Hq...arjtT1zdp7dcsk_test_4eC39HqLyjWDarjtT1zdp7dc:" \
  -d financial_account=fa_1MtkYw2eZvKYlo2CrqmzUo3O \
  -d limit=3

Response

{
  "object": "list",
  "url": "/v1/treasury/transactions",
  "has_more": false,
  "data": [
    {
      "id": "trxn_1MtkYw2eZvKYlo2ClMGIO54z",
      "object": "treasury.transaction",
      "amount": -100,
      "balance_impact": {
        "cash": -100,
        "inbound_pending": 0,
        "outbound_pending": 100
      },
      "created": 1680755802,
      "currency": "usd",
      "description": "Jane Austen (6789) | Outbound transfer | transfer",
      "financial_account": "fa_1MtkYw2eZvKYlo2CrqmzUo3O",
      "flow": "obt_1MtkYw2eZvKYlo2CqsyBpQts",
      "flow_type": "outbound_transfer",
      "livemode": false,
      "status": "open",
      "status_transitions": {
        "posted_at": null,
        "void_at": null
      }
    }
    {...}
    {...}
  ],
}

Transaction Entries

TransactionEntries represent individual units of money movements within a single Transaction.

Endpoints

GET/v1/treasury/transaction_entries/:id

GET/v1/treasury/transaction_entries

Outbound Transfers

Use OutboundTransfers to transfer funds from a FinancialAccount to a PaymentMethod belonging to the same entity. To send funds to a different party, use OutboundPayments instead. You can send funds over ACH rails or through a domestic wire transfer to a user’s own external bank account.

Simulate OutboundTransfer state changes with the /v1/test_helpers/treasury/outbound_transfers endpoints. These methods can only be called on test mode objects.

Endpoints

POST/v1/treasury/outbound_transfers

GET/v1/treasury/outbound_transfers/:id

GET/v1/treasury/outbound_transfers

POST/v1/treasury/outbound_transfers/:id/cancel

POST/v1/test_helpers/treasury/outbound_transfers/:id/fail

POST/v1/test_helpers/treasury/outbound_transfers/:id/post

POST/v1/test_helpers/treasury/outbound_transfers/:id/return

Outbound Payments

Use OutboundPayments to send funds to another party’s external bank account or FinancialAccount. To send money to an account belonging to the same user, use an OutboundTransfer.

Simulate OutboundPayment state changes with the /v1/test_helpers/treasury/outbound_payments endpoints. These methods can only be called on test mode objects.

Endpoints

POST/v1/treasury/outbound_payments

GET/v1/treasury/outbound_payments/:id

GET/v1/treasury/outbound_payments

POST/v1/treasury/outbound_payments/:id/cancel

POST/v1/test_helpers/treasury/outbound_payments/:id/fail

POST/v1/test_helpers/treasury/outbound_payments/:id/post

POST/v1/test_helpers/treasury/outbound_payments/:id/return

Inbound Transfers

Use InboundTransfers to add funds to your FinancialAccount via a PaymentMethod that is owned by you. The funds will be transferred via an ACH debit.

Endpoints

POST/v1/treasury/inbound_transfers

GET/v1/treasury/inbound_transfers/:id

GET/v1/treasury/inbound_transfers

POST/v1/treasury/inbound_transfers/:id/cancel

POST/v1/test_helpers/treasury/inbound_transfers/:id/fail

POST/v1/test_helpers/treasury/inbound_transfers/:id/return

POST/v1/test_helpers/treasury/inbound_transfers/:id/succeed

Received Credits

ReceivedCredits represent funds sent to a FinancialAccount (for example, via ACH or wire). These money movements are not initiated from the FinancialAccount.

Endpoints

GET/v1/treasury/received_credits/:id

GET/v1/treasury/received_credits

POST/v1/test_helpers/treasury/received_credits

Received Debits

ReceivedDebits represent funds pulled from a FinancialAccount. These are not initiated from the FinancialAccount.

Endpoints

GET/v1/treasury/received_debits/:id

GET/v1/treasury/received_debits

POST/v1/test_helpers/treasury/received_debits

Credit Reversals

You can reverse some ReceivedCredits depending on their network and source flow. Reversing a ReceivedCredit leads to the creation of a new object known as a CreditReversal.

Endpoints

POST/v1/treasury/credit_reversals

GET/v1/treasury/credit_reversals/:id

GET/v1/treasury/credit_reversals

Debit Reversals

You can reverse some ReceivedDebits depending on their network and source flow. Reversing a ReceivedDebit leads to the creation of a new object known as a DebitReversal.

Endpoints

POST/v1/treasury/debit_reversals

GET/v1/treasury/debit_reversals/:id

GET/v1/treasury/debit_reversals

Feature

A feature represents a monetizable ability or functionality in your system. Features can be assigned to products, and when those products are purchased, Stripe will create an entitlement to the feature for the purchasing customer.

Endpoints

POST/v1/entitlements/features

GET/v1/entitlements/features

POST/v1/entitlements/features/:id

Product Feature

A product_feature represents an attachment between a feature and a product. When a product is purchased that has a feature attached, Stripe will create an entitlement to the feature for the purchasing customer.

Endpoints

GET/v1/products/:id/features

POST/v1/products/:id/features

DELETE/v1/products/:id/features/:id

Active Entitlement

An active entitlement describes access to a feature for a customer.

Endpoints

GET/v1/entitlements/active_entitlements/:id

GET/v1/entitlements/active_entitlements

Scheduled Queries

If you have scheduled a Sigma query, you’ll receive a sigma.scheduled_query_run.created webhook each time the query runs. The webhook contains a ScheduledQueryRun object, which you can use to retrieve the query results.

Endpoints

GET/v1/sigma/scheduled_query_runs/:id

GET/v1/sigma/scheduled_query_runs

Report Runs

The Report Run object represents an instance of a report type generated with specific run parameters. Once the object is created, Stripe begins processing the report. When the report has finished running, it will give you a reference to a file where you can retrieve your results. For an overview, see API Access to Reports.

Note that certain report types can only be run based on your live-mode data (not test-mode data), and will error when queried without a live-mode API key.

Endpoints

POST/v1/reporting/report_runs

GET/v1/reporting/report_runs/:id

GET/v1/reporting/report_runs

Report Types

The Report Type resource corresponds to a particular type of report, such as the “Activity summary” or “Itemized payouts” reports. These objects are identified by an ID belonging to a set of enumerated values. See API Access to Reports documentation for those Report Type IDs, along with required and optional parameters.

Note that certain report types can only be run based on your live-mode data (not test-mode data), and will error when queried without a live-mode API key.

Endpoints

GET/v1/reporting/report_types/:id

GET/v1/reporting/report_types

Accounts

A Financial Connections Account represents an account that exists outside of Stripe, to which you have been granted some degree of access.

Endpoints

GET/v1/financial_connections/accounts/:id

GET/v1/financial_connections/accounts

POST/v1/financial_connections/accounts/:id/disconnect

POST/v1/financial_connections/accounts/:id/refresh

POST/v1/financial_connections/accounts/:id/subscribe

POST/v1/financial_connections/accounts/:id/unsubscribe

Account Owner

Describes an owner of an account.

Endpoints

GET/v1/financial_connections/accounts/:id/owners

Session

A Financial Connections Session is the secure way to programmatically launch the client-side Stripe.js modal that lets your users link their accounts.

Endpoints

POST/v1/financial_connections/sessions

GET/v1/financial_connections/sessions/:id

Transactions

A Transaction represents a real transaction that affects a Financial Connections Account balance.

Endpoints

GET/v1/financial_connections/transactions/:id

GET/v1/financial_connections/transactions

Tax Calculations

A Tax Calculation allows you to calculate the tax to collect from your customer.

Endpoints

GET/v1/tax/calculations/:id/line_items

POST/v1/tax/calculations

Tax Registrations

A Tax Registration lets us know that your business is registered to collect tax on payments within a region, enabling you to automatically collect tax.

Stripe doesn’t register on your behalf with the relevant authorities when you create a Tax Registration object. For more information on how to register to collect tax, see our guide.

Related guide: Using the Registrations API

Endpoints

POST/v1/tax/registrations

POST/v1/tax/registrations/:id

GET/v1/tax/registrations/:id

GET/v1/tax/registrations

Tax Transactions

A Tax Transaction records the tax collected from or refunded to your customer.

Endpoints

POST/v1/tax/transactions/create_reversal

POST/v1/tax/transactions/create_from_calculation

GET/v1/tax/transactions/:id/line_items

GET/v1/tax/transactions/:id

Tax Settings

You can use Tax Settings to manage configurations used by Stripe Tax calculations.

Related guide: Using the Settings API

Endpoints

POST/v1/tax/settings

GET/v1/tax/settings

Verification Session

A VerificationSession guides you through the process of collecting and verifying the identities of your users. It contains details about the type of verification, such as what verification check to perform. Only create one VerificationSession for each verification in your system.

A VerificationSession transitions through multiple statuses throughout its lifetime as it progresses through the verification flow. The VerificationSession contains the user’s verified data after verification checks are complete.

Related guide: The Verification Sessions API

Endpoints

POST/v1/identity/verification_sessions

POST/v1/identity/verification_sessions/:id

GET/v1/identity/verification_sessions/:id

GET/v1/identity/verification_sessions

POST/v1/identity/verification_sessions/:id/cancel

POST/v1/identity/verification_sessions/:id/redact

Verification Report

A VerificationReport is the result of an attempt to collect and verify data from a user. The collection of verification checks performed is determined from the type and options parameters used. You can find the result of each verification check performed in the appropriate sub-resource: document, id_number, selfie.

Each VerificationReport contains a copy of any data collected by the user as well as reference IDs which can be used to access collected images through the FileUpload API. To configure and create VerificationReports, use the VerificationSession API.

Related guides: Accessing verification results.

Endpoints

GET/v1/identity/verification_reports/:id

GET/v1/identity/verification_reports

Crypto Onramp Session

A Crypto Onramp Session represents your customer’s session as they purchase cryptocurrency through Stripe. Once payment is successful, Stripe will fulfill the delivery of cryptocurrency to your user’s wallet and contain a reference to the crypto transaction ID.

You can create an onramp session on your server and embed the widget on your frontend. Alternatively, you can redirect your users to the standalone hosted onramp.

Related guide: Integrate the onramp

Endpoints

POST/v1/crypto/onramp_sessions

GET/v1/crypto/onramp_sessions/:id

GET/v1/crypto/onramp_sessions

Crypto Onramp Quotes

Crypto Onramp Quotes are estimated quotes for onramp conversions into all the different cryptocurrencies on different networks. The Quotes API allows you to display quotes in your product UI before directing the user to the onramp widget.

Related guide: Quotes API

Endpoints

GET/v1/crypto/onramp/quotes

Climate Order

Orders represent your intent to purchase a particular Climate product. When you create an order, the payment is deducted from your merchant balance.

Endpoints

POST/v1/climate/orders

POST/v1/climate/orders/:id

GET/v1/climate/orders/:id

GET/v1/climate/orders

POST/v1/climate/orders/:id/cancel

Climate Product

A Climate product represents a type of carbon removal unit available for reservation. You can retrieve it to see the current price and availability.

Endpoints

GET/v1/climate/products/:id

GET/v1/climate/products

Climate Supplier

A supplier of carbon removal.

Endpoints

GET/v1/climate/suppliers/:id

GET/v1/climate/suppliers

Forwarding Request

Instructs Stripe to make a request on your behalf using the destination URL. The destination URL is activated by Stripe at the time of onboarding. Stripe verifies requests with your credentials provided during onboarding, and injects card details from the payment_method into the request.

Stripe redacts all sensitive fields and headers, including authentication credentials and card numbers, before storing the request and response data in the forwarding Request object, which are subject to a 30-day retention period.

You can provide a Stripe idempotency key to make sure that requests with the same key result in only one outbound request. The Stripe idempotency key provided should be unique and different from any idempotency keys provided on the underlying third-party request.

Forwarding Requests are synchronous requests that return a response or time out according to Stripe’s limits.

Endpoints

POST/v1/forwarding/requests

GET/v1/forwarding/requests/:id

GET/v1/forwarding/requests