Create a Stripe Treasury FinancialAccount for a connected account via POST /v1/treasury/financial_accounts with the desired features (e.g., financial_addresses.aba, inbound_transfers.ach)
Retrieve the FinancialAccount's financial_addresses to obtain the ABA routing and account numbers that external parties can use to send funds
When funds arrive (via ACH credit, wire, or book transfer), Stripe creates a ReceivedCredit object and fires the treasury.received_credit.created webhook
List ReceivedCredits for a FinancialAccount via GET /v1/treasury/received_credits?financial_account=:fa_id; filter by status ('succeeded' or 'failed') as needed
Inspect each ReceivedCredit for amount, currency, network (ach, wire, stripe), and initiating_payment_method_details for sender information
In test mode, simulate an inbound ACH credit via POST /v1/test_helpers/treasury/received_credits using the test_mode_create helper
Known gotchas
Treasury FinancialAccounts are only available to connected accounts on platforms that have been approved for Treasury; apply for access before building
ReceivedCredits cannot be initiated by your platform; they represent funds sent by third parties and are created by Stripe automatically upon receipt
A ReceivedCredit with status 'failed' means the funds were returned to the sender; inspect the failure_code field to understand why
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp