Read bank data
Access accounts, balances and transactions programmatically.
TrueLayer Connector
Embed access to customers’ bank accounts to read accounts, balances and transactions, verify account ownership and initiate pay-by-bank flows inside your SaaS product with Cyclr.
Initiate payments
Create pay-by-bank payments and manage payouts and mandates.
Secure auth
Use OAuth flows and signed requests for payments.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
What you can integrate and automate with TrueLayer
Teams can read account details, balances, and transaction history, run account verification, and initiate bank payments and payouts for end users. Use Cyclr to build in-app connection flows, schedule transaction syncs, and surface payment status and webhook events inside your multi-tenant product. See the TrueLayer API documentation for product-specific endpoints and scopes.
PRODUCT USE CASES
Top use cases for TrueLayer integrations
Build customer-facing automations for payments, account verification, reconciliation and transaction-driven workflows. Publish these as white-label embedded integrations in your app via Cyclr’s marketplace and governance controls.
Automated payment reconciliation
Sync transactions and balances for customer accounts to reconcile received payments and update invoices. Uses Transactions and Balances endpoints.
Bank account verification during signup
Verify account ownership and holder identity to reduce fraud using TrueLayer’s Verification and Data connection flows.
Initiate refunds and payouts
Create pay-by-bank payments, manage mandates and send payouts using the Payments and Payouts APIs with signing keys and idempotency.
ORCHESTRATION
How TrueLayer works with Cyclr
Cyclr sits between your SaaS product and TrueLayer to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
TrueLayer
TrueLayer processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore TrueLayer methods you can orchestrate through Cyclr.
Accounts3
Retrieve an account
ActionReturns data associated with the specified account
Retrieve account transactions
ActionReturns transaction data for the specified account
List all accounts
ActionReturns all customer accounts and associated data
Cards4
Retrieve a card
ActionReturns a customer card and associated data
Retrieve card balance
ActionReturns card balance information for the specified account
Retrieve card transactions
ActionReturns card transaction data for the specified account
List all cards
ActionReturns all customer cards and associated data
Customer1
Retrieve identity information
ActionReturns Customer identity information held by the Provider. This can include name, address, emails and phone numbers
TECHNICAL DETAILS
TrueLayer integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing TrueLayer integrations in Cyclr.
API and authentication
- API host
https://api.truelayer.com- Authentication
- OAuth 2.0; Client credentials
- Credentials
client_id; client_secret; redirect_uri; signing keys (Payments); webhook URI
- Method categories
Accounts; Balances; Transactions; Payments; Payouts; Verification; Merchant endpoints
Pagination and rate limits
Pagination
Many list endpoints use cursor-based pagination (next_cursor). Transactions support date-range filters; large exports can run asynchronously with webhook notification.
Rate limits
TrueLayer enforces per-endpoint rate limits and returns 429 on excess; implement backoff and idempotency for Payments.
IMPLEMENTATION
Authentication at a glance
TrueLayer uses OAuth 2.0: authorization-code for user consent and client_credentials for server-to-server calls. Payments require uploaded signing keys and client credentials. Confirm enabled flows in Cyclr Console.
- Authentication method
- OAuth 2.0; Client credentials
- Credential required
client_id; client_secret; redirect_uri; signing keys (Payments); webhook URI
Before you begin:
View setup guideRequires a TrueLayer Console app, client credentials and uploaded signing keys for Payments.
COMMON QUESTIONS
Frequently asked questions
It reads bank accounts, balances and transactions, verifies account ownership and initiates pay-by-bank payments and payouts. Use Data endpoints for account data and Payments/Payouts for bank-initiated money flows.
Answer: TrueLayer uses OAuth 2.0. Use the authorization-code flow to obtain user consent for Data access and client_credentials for server-to-server operations; Payments require uploaded signing keys and client credentials.
Yes. Create and manage per-tenant connections (user consent flows and server credentials) and use Cyclr to store tenant credentials and run multi-tenant workflows securely.
Yes. Cyclr can wrap TrueLayer methods (read transactions, create payments, verify accounts) as governed MCP tools so product teams expose approved actions to end users.
KEEP EXPLORING
Related resources and connectors
Documentation
What is iPaaS?
Read more →ProductHow to develop an API – Best Practices to Follow from Cyclr Developers
Read more →ProductMCP PaaS
Read more →Related connectorAuthorize.net
Related Billing/Payment connector for customer-facing integration workflows.
Related connectorBookeo
Related Billing/Payment connector for customer-facing integration workflows.
Related connectorCardpointe
Related Billing/Payment connector for customer-facing integration workflows.