Access transactions for a Financial Connections account
Access an account's transactions with your user's permission.
The Financial Connections API allows you to retrieve transactions on a Financial Connections Account. Use transaction data to build a variety of products and solutions, such as:
- Expedite the underwriting process and improve access to credit and other financial services for your users.
- Mitigate fraud and reduce risk during user onboarding by evaluating a user’s transaction history, and understanding cash inflows and outflows from their financial accounts.
- Help your users track expenses, handle bills, and manage their finances.
Before you begin
You must have a completed Financial Connections registration to access transactions in live mode. Visit your Dashboard settings to check the state of your registration or begin the registration process. Financial Connections test data is always available.
Create a customer Recommended Server-side
We recommend that you create a Customer with an email address and phone number to represent your user, that you then attach to your payment. Attaching a Customer object allows you to list previously linked accounts later. By providing the email address and phone number on the Customer object, Financial Connections can improve the authentication flow by simplifying sign-in or sign-up for your user, depending on whether they’re a returning Link user.
Command Line
Select a language
cURL
Stripe CLI
Ruby
Python
PHP
Java
Node.js
Go
.NET
No results
Request access to an account's transactions Server-side
You must collect an account before you can access its transaction data. To learn more about how to collect Financial Connections Accounts consult the integration guide most relevant to your use case: accept payments, facilitate Connect payouts, or build other-data powered products.
When collecting an account, you specify the data you need access to with the permissions parameter. The set of requested data permissions are viewable by the user in the authentication flow. Financial Connections Accounts are collectible through various integration paths, and how you specify the parameter varies slightly by API.
Enable US bank account as a payment method in your Dashboard before creating the intent.
Command Line
Select a language
cURL
Stripe CLI
Ruby
Python
PHP
Java
Node.js
Go
.NET
No results
When using dynamic payment methods for certain payments APIs, you can also configure requested permissions in the Dashboard. Learn how to access additional account data on Financial Connections accounts.
Subscribe to transaction data Server-side
When you subscribe to an account’s transaction data, Stripe automatically retrieves new transactions in the background every day and notifies you when they’re available. Subscribing to daily updates is the easiest way to keep the account’s transaction data up to date.
To get the Financial Connections Account ID you want to subscribe to transactions for, consult the documentation for our payments integrations or check the guide for Financial Connections Sessions.
Subscribe to transaction data by calling the subscribe API:
Command Line
Select a language
cURL
Stripe CLI
Ruby
Python
PHP
Java
Node.js
Go
.NET
No results
Note
Subscriptions aren’t allowed on inactive accounts.
In addition to activating a subscription to future transaction data, this API call automatically initiates a transaction refresh:
{
"id": "fca_1LDYuMGxLVUXRs6HW0lrat9T",
"object": "financial_connections.account",
"display_name": "Savings",
"institution_name": "Test Bank",
"status": "active",
"permissions": ["transactions"],
"subscriptions": ["transactions"],
"transaction_refresh": {
"id": "fctxnref_1aaaxqEitUZY8Svm4QdcWZKt",
"last_attempted_at": 1706742786,
"next_refresh_available_at": null,
"status": "pending"
}
// ...
}
As long as you remain subscribed to transaction data, Stripe initiates a new refresh every day.
Wait for the refresh to complete
All Financial Connections data refreshes are asynchronous. After you initiate a transaction refresh, you must wait for it to complete, then retrieve the resulting transactions.
The transaction_refresh field on a Financial Connections account represents the transaction refresh state. This field remains null until you request the transactions permission and initiate a refresh. After you start a transaction refresh, the state changes to pending, and after completion, it moves to either succeeded or failed. We send the financial_connections.account.refreshed_transactions event when the transaction refresh completes. To determine the success of the refresh, check the transaction_refresh.status field while handling the webhook.
Retrieve transactions Server-side
After Stripe successfully refreshes transactions on the account, you can retrieve them using the transactions list API:
Command Line
Select a language
cURL
Stripe CLI
Ruby
Python
PHP
Java
Node.js
Go
.NET
No results
Stripe returns a paginated list of up to the last 180 days of transaction history on an account, depending on the account’s financial institution.
The status of a transaction is one of pending, posted, or void. Information included in the description field varies, but can include metadata such as the business name.
Retrieving transactions since last refresh
You might wish to retrieve only new transaction data since your last data pull. For example, some users save previously retrieved transaction data to their database, and subsequently merge new or updated data as it becomes available.
To retrieve only new or updated transaction data since your last refresh, pass the transaction_refresh identifier provided by your last observed financial_connections.account.refreshed_transactions webhook event object to the list API:
Command Line
Select a language
cURL
Stripe CLI
Ruby
Python
PHP
Java
Node.js
Go
.NET
No results
The following is an example webhook integration that only retrieves and records new or updated transaction data:
Python
import stripe
from flask import Flask
app = Flask(__name__)
@app.route('/stripe_webhooks', methods=['POST'])
def webhook():
event = None
try:
event = stripe.Event.construct_from(json.loads(request.data), stripe.api_key)
except ValueError as e:
# Invalid payload
raise e
if event.type == "financial_connections.account.refreshed_transactions":
account = event.data.object
sync_transactions(account["id"], account["transaction_refresh"]["id"])
return jsonify(success=True)
def sync_transactions(account_id, current_refresh):
# Fetches the last transaction_refresh observed for this account from internal database
last_observed_transaction_refresh = get_previous_transaction_refresh(key=account_id)
# Get transactions since the last seen transaction_refresh
response = client.v1.financial_connections.transactions.list(params={
'account': account_id,
'transaction_refresh': {'after': last_observed_transaction_refresh},
})
# We know every transaction is either new or updated because of the `transaction_refresh` filter in the list endpoint
for transaction in response.data:
record_transaction(transaction) # Saves the transaction to the DB
# Updates the last observed transaction_refresh for this account to the current refresh
set_previous_transaction_refresh(key=account_id, value=current_refresh)