How Teller fits in CloudIP
- Provides live bank and credit-card feeds to the Accounting module.
- Verifies bank ownership for ACH-debit payment methods.
- Powers balance checks for cash-flow forecasting.
Why this integration exists
Teller connects directly to US bank APIs and is the default for the Accounting bank-feeds capability.
Configuration notes
- Re-auth flows handled in-app when banks rotate tokens.
- No credentials stored in CloudIP — all bank auth lives in the Teller enrollment token.
- Teller authenticates with a client TLS certificate, so the feed runs from the CloudIP application servers rather than the edge.
How the Teller integration runs in production
The Teller integration is part of the standard CloudIP subscription — it is not a partner-tier add-on or a separate billing line. Authentication, rate limiting, and error handling are managed inside the platform, and any change in the Teller state of the world propagates to the relevant CloudIP module without operator intervention.
For most customers, the integration is invisible after the initial connection: records appear in the banking module they belong to, and downstream workflows — reports, audit trail, exports — see the same data the rest of the platform sees. The integration honours the tenant.dataResidency choice you make at provisioning, so Teller traffic respects the same boundary as your own records.
If you eventually outgrow the Teller integration, the data it touches stays inside CloudIP — the integration is a connector, not a system of record. That means swapping Teller for an alternative does not require a data migration; it requires reconnecting the source.
Common questions about the Teller integration
Yes. The Teller integration is part of the platform; there is no per-integration fee or premium tier required to use it. You bring your own Teller account where applicable, and CloudIP handles the connection.
Start free for 14 days
See how CloudIP and its integrations work together on real data.