Integration Exchange. Provider choice, governed as configuration.
Banking, custody, payments, identity, tax, and data providers connect through one governed exchange. Each financial institution, custodian, and administrator receives its own provider selections, vault-backed credential profiles, environment settings, effective dates, and enable and disable controls. Administrator choices remain inside the governing custodian’s permissions.
Integration families
Provider names are published only when the integration and relationship are authorized.
Banking partners
FBO and deposit relationships behind omnibus custodial cash.
Custody providers
The provider side of the custody command fabric.
Payments
ACH, wire, instant, and card rails behind money movement.
Identity & onboarding
KYC, KYB, and document verification in opening flows.
Tax providers
Filing and delivery paths for tax reporting.
Market & reference data
Pricing and reference data for positions and valuations.
What the exchange guarantees
The properties every integration shares.
Normalized events
Partner events arrive as A8 Core™ events your systems already consume.
Credential isolation
Partner credentials held in the integration layer, never in application code.
Replay & recovery
Feeds can be replayed and gaps healed with records of both.
Observability
Every integration’s health, lag, and errors visible in operations.
Configuration follows the institution
Every account has one governing custodian, and the configuration hierarchy follows from that.
Financial institutions
Institution-owned core, sponsor-bank, network, and payment configurations, isolated by environment and credential profile.
Custodians
The governing custodian controls the providers and capabilities that execute deposits, custody instructions, transfers, settlement, tax filing, and books-and-records activity — including its own filing credentials, held per environment as vault references in its configuration.
Third-party administrators
A custodian may authorize several TPAs, and a TPA may serve several custodians. Each relationship is configured separately, and a TPA cannot exceed the custodian’s settings.
A8 Core™ common services
System-wide market, reference, identifier, research, and common data-source credentials are maintained by authorized A8 Core™ personnel.
Administrative workflow is not money movement
The distinction an examiner tests, drawn on the architecture rather than asserted in a policy.
What a TPA may do
Collect documentation, validate contribution limits, classify a transaction, prepare an instruction, and perform delegated administrative approval.
What only the custodian, its FI, or an authorized clearing provider does
Remote deposit capture, physical deposits, ACH, wires, instant payments, settlement, and regulated asset movement.
One asset, multiple trusted sources
A8 Core™ maintains one system-wide asset definition, and every account holding and investment links to it.
Each source observation is preserved as an immutable, source-attributed record. Canonical fields are resolved from those observations by effective-dated authority, freshness, validation, entitlement, and licensing rules — so a valuation can always be traced to the source that produced it and the moment it was true.
Integrations and subprocessors are five different statements
Publishing them as one list is how a vendor-risk reviewer is misled, so they are kept apart.
Available or authorized
The integration exists and the relationship permits naming it.
Development targets
Specified and planned. Not available today.
Legacy or sunset interfaces
Supported only for transition, prior periods, corrections, and evidence.
Potential subprocessors
Under consideration or contracted but not enabled. No customer data flows.
Active subprocessors
Contracted, enabled, and processing covered customer data. Only these appear on Exhibit C.
Build on the account operating system.
See how this module fits your institution’s account, custody, and operations model.