What Stuut needs from your bank
You can start with either one. Most customers with a lockbox send both.
How the connection works
Stuut receives bank data in one of three ways. Your bank and your Stuut team will confirm which one fits.- Bank API. Stuut reads your account activity directly from the bank. You approve access through your bank’s portal. No bank login is shared with Stuut.
- Secure file transfer (SFTP). Your bank sends files to Stuut on a schedule. Your bank and Stuut set this up together.
- Bank account link or manual upload. For smaller banks, you can link the account in Stuut or upload a statement at any time from the Bank Statements page.
Choose your bank
Bank of America
CashPro bank transactions and B2Bi lockbox files.
Citi
Bank accounts and transactions through the CitiConnect API.
JPMorgan Chase
Cash reporting through J.P. Morgan Access, plus lockbox files.
PNC
Lockbox files and check images through PNC’s secure file exchange (EFX).
Wells Fargo
Bank transactions through the Wells Fargo Gateway API.
Kyriba
Bank statements from all your banks through the Kyriba API.
Trovata
Bank accounts and transactions from all your banks through the Trovata API.
Don’t see your bank here? Stuut also connects to Western Alliance Bank, links smaller banks through Plaid, and reads standard bank files from most other banks. Contact your Stuut team or support@stuut.co for help with any bank.
Typical timeline
Most of the setup work happens at your bank, so timing depends on your bank’s process. The steps are usually:- Request. You ask your bank’s treasury contact to send data to Stuut. Each guide includes a sample email.
- Paperwork. Your bank may ask you to sign a third-party data authorization.
- Connection. Your bank and Stuut set up the connection directly.
- Testing. Your bank sends test data. Stuut loads it so you can review it before go-live.
- Go-live. Your bank switches to production data, and Stuut processes it automatically.