TransactionEntries represent individual units of money movements within a single Transaction.
Attributes
- idstring
Unique identifier for the object.
- objectstring
String representing the object’s type. Objects of the same type share the same value.
- balance_
impactobject The current impact of the TransactionEntry on the FinancialAccount’s balance.
- 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.
- effective_
attimestamp When the TransactionEntry will impact the FinancialAccount’s balance.
- financial_
accountstring The FinancialAccount associated with this object.
- flownullable string
Token of the flow associated with the TransactionEntry.
- flow_
detailsnullable objectExpandable Details of the flow associated with the TransactionEntry.
- flow_
typeenum Type of the flow associated with the TransactionEntry.
Possible enum valuescredit_
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 valuefalse
if the object exists in test mode. - transactionstringExpandable
The Transaction associated with this object.
- typeenum
The specific money movement that generated the TransactionEntry.
Possible enum valuescredit_
reversal The TransactionEntry was generated by a CreditReversal.
credit_
reversal_ posting The TransactionEntry was generated by a posted CreditReversal.
debit_
reversal The TransactionEntry was generated by a DebitReversal.
inbound_
transfer The TransactionEntry was generated by an InboundTransfer.
inbound_
transfer_ return The TransactionEntry was generated by an InboundTransferReturn.
issuing_
authorization_ hold The TransactionEntry was generated by an Issuing authorization hold.
issuing_
authorization_ release The TransactionEntry was generated by an Issuing authorization release.
other
The TransactionEntry was generated by some other money movement.
outbound_
payment The TransactionEntry was generated by an OutboundPayment.
outbound_
payment_ cancellation The TransactionEntry was generated by a cancelled OutboundPayment.
Show 10 more
{ "id": "trxne_1MtkgV2eZvKYlo2CmofEnIwJ", "object": "treasury.transaction_entry", "balance_impact": { "cash": 0, "inbound_pending": 0, "outbound_pending": -1000 }, "created": 1680756271, "currency": "usd", "effective_at": 1680756271, "financial_account": "fa_1MtkgV2eZvKYlo2CdxyvnHeQ", "flow": "obt_1MtkgV2eZvKYlo2CCxhXVFLB", "flow_type": "outbound_transfer", "livemode": false, "transaction": "trxn_1MtkgV2eZvKYlo2CRYxD7KLh", "type": "outbound_transfer"}
Retrieves a TransactionEntry object.
Parameters
No parameters.
Returns
Returns a TransactionEntry object.
{ "id": "trxne_1MtkgV2eZvKYlo2CmofEnIwJ", "object": "treasury.transaction_entry", "balance_impact": { "cash": 0, "inbound_pending": 0, "outbound_pending": -1000 }, "created": 1680756271, "currency": "usd", "effective_at": 1680756271, "financial_account": "fa_1MtkgV2eZvKYlo2CdxyvnHeQ", "flow": "obt_1MtkgV2eZvKYlo2CCxhXVFLB", "flow_type": "outbound_transfer", "livemode": false, "transaction": "trxn_1MtkgV2eZvKYlo2CRYxD7KLh", "type": "outbound_transfer"}
Retrieves a list of TransactionEntry objects.
Parameters
- financial_
accountstringRequired Returns objects associated with this FinancialAccount.
- createdobject
Only return TransactionEntries that were created during the given date interval.
- order_
byenum The results are in reverse chronological order by
created
oreffective_
. The default isat created
.Possible enum valuescreated
Timestamp describing when the TransactionEntry was created.
effective_
at Timestamp describing when the TransactionEntry was effective.
- transactionstring
Only return TransactionEntries associated with this Transaction.
More parameters
- ending_
beforestring - limitinteger
- starting_
afterstring
Returns
A dictionary with a data
property that contains an array of up to limit
TransactionEntries, starting after TransactionEntry starting_
. Each entry in the array is a separate TransactionEntry object. If no more TransactionEntries are available, the resulting array is empty.
{ "object": "list", "url": "/v1/treasury/transaction_entries", "has_more": false, "data": [ { "id": "trxne_1MtkgV2eZvKYlo2CmofEnIwJ", "object": "treasury.transaction_entry", "balance_impact": { "cash": 0, "inbound_pending": 0, "outbound_pending": -1000 }, "created": 1680756271, "currency": "usd", "effective_at": 1680756271, "financial_account": "fa_1MtkgV2eZvKYlo2CdxyvnHeQ", "flow": "obt_1MtkgV2eZvKYlo2CCxhXVFLB", "flow_type": "outbound_transfer", "livemode": false, "transaction": "trxn_1MtkgV2eZvKYlo2CRYxD7KLh", "type": "outbound_transfer" } {...} {...} ],}
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_
endpoints. These methods can only be called on test mode objects.
Related guide: Moving money with Treasury using OutboundTransfer objects
- POST/
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_
endpoints. These methods can only be called on test mode objects.
Related guide: Moving money with Treasury using OutboundPayment objects
- POST/
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.
Related guide: Moving money with Treasury using InboundTransfer objects
- POST/
ReceivedCredits represent funds sent to a FinancialAccount (for example, via ACH or wire). These money movements are not initiated from the FinancialAccount.
ReceivedDebits represent funds pulled from a FinancialAccount. These are not initiated from the FinancialAccount.
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.
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.
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.
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.
An active entitlement describes access to a feature for a customer.
If you have scheduled a Sigma query, you’ll receive a sigma.
webhook each time the query runs. The webhook contains a ScheduledQueryRun
object, which you can use to retrieve the query results.
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.
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.
A Financial Connections Account represents an account that exists outside of Stripe, to which you have been granted some degree of access.
Describes an owner of an account.
A Financial Connections Session is the secure way to programmatically launch the client-side Stripe.js modal that lets your users link their accounts.
A Transaction represents a real transaction that affects a Financial Connections Account balance.
A Tax Calculation allows you to calculate the tax to collect from your customer.
Related guide: Calculate tax in your custom payment flow
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
A Tax Transaction records the tax collected from or refunded to your customer.
Related guide: Calculate tax in your custom payment flow
You can use Tax Settings
to manage configurations used by Stripe Tax calculations.
Related guide: Using the Settings API
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
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_
, 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 guide: Accessing verification results.
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
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
Orders represent your intent to purchase a particular Climate product. When you create an order, the payment is deducted from your merchant balance.
A Climate product represents a type of carbon removal unit available for reservation. You can retrieve it to see the current price and availability.
A supplier of carbon removal.
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.
Related guide: Forward card details to third-party API endpoints.
You can configure webhook endpoints via the API to be notified about events that happen in your Stripe account or connected accounts.
Most users configure webhooks from the dashboard, which provides a user interface for registering and testing your webhook endpoints.
Related guide: Setting up webhooks