Interfaces and Integrations
Torque supports configurable third-party integrations. Each deployment can use approved providers that match its operating, compliance, security, and infrastructure requirements.
Configurable integration categories
| Category | Torque experience | Provider boundary |
|---|---|---|
| Identity and access | Start and continue account, session, sign-in, sign-up, password, recovery, and multi-factor authentication flows. | The configured identity provider owns identity policy, credentials, sessions, recovery, and authoritative authentication results. |
| Fund and investment operations | Read fund data, create or recover investment work, submit actions, and display returned status. | The configured operating services own fund availability, capacity, persistence, and authoritative status transitions. |
| Eligibility and compliance evidence | Start or continue identity, business, accreditation, suitability, and evidence-collection flows. | The configured compliance providers own decisioning, evidence retention, review outcomes, and completion results. |
| Agreements and electronic signatures | Present agreement, signature, and document-completion handoffs. | The configured agreement provider owns signature validity, completion evidence, and retained execution records. |
| Payments, wallets, and settlement | Present funding, bank-account connection, wallet setup, transaction, custody, and signing handoffs. | The configured financial and custody providers own money movement, asset custody, network execution, transaction results, and final balances. |
| Document storage and delivery | Display authorized public or private document collections and supplied download links. | The configured document provider owns access checks, secure link issuance, storage, and retention. |
| Distributions and communications | Display distribution records and support inbox, email, and device-notification behavior. | The configured payout and communication providers own calculation inputs, delivery results, payout execution, and retained records. |
| Forms and analytics | Submit contact or subscription requests and record permitted usage data where configured. | The configured services own delivery, consent enforcement, retention, and privacy controls. |
Interface Requirements
Every configured integration contract must define authentication, authorization, request and response schemas, validation errors, idempotency, retry behavior, events or webhooks, reconciliation ownership, and deprecation policy. Client behavior alone does not prove provider-side completion.
Failure and Recovery
Torque preserves enough context for a user to recover from an interrupted integration flow. Recovery can include:
- Reloading unfinished investment work.
- Retrying an authorized wallet or signing handoff.
- Returning to an incomplete eligibility action.
- Showing a safe recovery page when an integration or route cannot load.
A retry is safe or idempotent only when the configured service contract provides that guarantee.