Temenos Transact (formerly T24) is the flagship real-time core banking platform from Temenos, running deposits, lending, payments, treasury, wealth, and Islamic banking for 950+ banks across retail, corporate, and inclusive segments. An unofficial API lets you programmatically pull accounts, balances, transactions, customers, loans, deposits, and payment orders—and push updates like fund transfers, standing orders, new arrangements, and forex deals back into Transact across on-prem, cloud, and SaaS deployments.

Temenos Transact (formerly T24) is the flagship real-time core banking platform from Temenos, delivering the most extensive set of banking functionality across Retail, Corporate, Treasury, Wealth, and Payments. Banks use Transact to administer accounts and deposits, originate and service loans, process fund transfers and standing orders, run treasury and foreign-exchange deals, and support inclusive and Islamic banking—deployed on-premises, on cloud, or as Temenos SaaS.
Core business domains and API categories include:
Common data entities:
Banks run mission-critical, real-time workloads on Transact, but turning a heavily configured core banking system into reliable API-driven automation is non-trivial:
Supergood reverse-engineers authenticated sessions, the IRIS REST framework, and OFS-backed interactions to deliver a resilient API layer for your Transact deployment—across Holdings, Order, Party, and Treasury domains and any release version.
Use Temenos Transact with AI agents: Temenos Transact MCP Server →
Book a 30-minute session to confirm your modules, release version, deployment model, and authentication setup.
We deliver a production-ready Transact adapter tailored to your bank's configuration, parameter tables, and entitlements.
Go live with continuous monitoring and automatic adjustments as Temenos releases and your configuration evolve.
Authentication
/authenticateAuthenticate to a Temenos Transact deployment using API key, OAuth, or MFA and obtain a session token for downstream calls.
Holdings
/accountsList accounts and arrangements with balances, status, and currency filters across retail, corporate, and inclusive segments.
Holdings
/transactionsRetrieve transaction details and accounting entries for an account with date-range and type filters.
Party
/customersPull customer and financial-institution party records, KYC details, beneficiaries, and delivery preferences.
Order
/create_transferInitiate an inward, outward, or bulk fund transfer or standing order against an account, including SEPA and cross-border payments.
Holdings
/create_arrangementCreate a new deposit or loan arrangement (short-term, long-term, call, Islamic, personal, mortgage, or line of credit) against the bank's product definition.
Treasury
/forex_dealsList treasury and foreign-exchange deals including spot, forward, swap, and limit orders with rate and counterparty filters.
- Pull accounts, balances, and arrangements across retail, corporate, and inclusive segments into a single warehouse - Stream transaction and accounting-entry events to downstream BI, reconciliation, and AML tools - Reconcile customer and party records across deployments for a unified banking 360
- Initiate inward, outward, and bulk fund transfers programmatically without portal clicks - Schedule and amend standing order instructions and SEPA/cross-border credit transfers - Track payment status, returns, and exceptions back into your operations workflows
- Create deposit and loan arrangements against bank-specific product definitions and interest conditions - Pull repayment schedules, balances, and accruals for downstream servicing and reporting - Push status changes and disbursements into Holdings while preserving audit trails
- Book and retrieve spot, forward, swap, and limit forex deals through the Order domain - Surface treasury positions, limits, and facilities to risk and reporting systems - Reconcile deal lifecycle events across the bank's treasury and core books
Authentication
API key, OAuth, and MFA handled in a managed session with an encrypted credential vault
Connectivity
Authenticated sessions plus the IRIS REST framework and OFS message format surfaced per the bank's release and deployment
Response format
Normalized JSON across Holdings, Order, Party, Product, and Treasury objects
Rate limits
Adaptive throttling tuned to your Transact tenant to avoid bank-side and host limits
Session management
Automatic session refresh, token rotation, and MFA replay handling
Data freshness
Near real-time reads for accounts, transactions, and payments with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for transactions, payment status, arrangement creation, and forex deal lifecycle
Latency
Sub-second reads on cached entities; multi-second writes when posting transfers and arrangements through OFS
Throughput
Horizontally scaled workers sized to high-volume retail, corporate, and treasury banking activity
Reliability
Retry, backoff, and idempotency keys for transfers, arrangements, and forex transactions
Adaptation
Continuous monitoring of Temenos releases, IRIS framework changes, and bank-specific configuration drift
Yes. Temenos Transact is the current name for the platform formerly known as T24. Supergood works against the same core banking surfaces regardless of the release branding or version you run.
No. Supergood works with your existing Transact deployment and entitlements. Where IRIS REST APIs are available we use them; otherwise we operate against the same authenticated surfaces and OFS-backed operations your bank already relies on.
Yes. Supergood adapts to all three models. For SaaS and cloud tenants we work against your bank's surfaces; for on-prem we operate against the same authenticated endpoints with network configuration tuned to your environment.
Each deployment is profiled against its configured product definitions, business rules, and parameter tables. Supergood preserves bank-specific fields, lifecycle states, and entitlements rather than forcing a generic schema.
Yes. Holdings, Order, Party, and Treasury domains are exposed through one normalized API surface, so accounts, transfers, loans, deposits, and forex deals sit alongside each other without separate integrations.