Your institution · Not launched
Ongoing health for one integration that powers every Relay experience. Core integrations are available through Relay’s provider-neutral API layer — your integration partner connects your systems during onboarding.
Connection
Data mapping health
Sidecar core contract
Sidecar ships against a core-agnostic adapter. Map your API to these objects and the Sidecar experience works unchanged.
A partner implements the adapter interface, or supplies a field map from its own payloads to these fields. No Sidecar screen or business rule changes. The demo runs on a reference mock core, not a vendor production core. Permission objects describe what your institution granted; enforcement stays server-side in your systems.
Relay module health
Recent items needing attention
- AuthenticationAdd the name of your integration credential and run Test connection.
- ConnectivityAdd your server endpoint, then test the connection.
- Session handlingAdd your institution or tenant identifier.
- AccountsRun discovery so we can see the account categories available.
- ProductsConfirm how your products map to Relay categories.
- Sprout readySavings products and account relationships are required.
- Sidecar readyTransaction activity must be discovered and permitted.
Health checks shown here are simulated for the prototype using fictional sample data. In a licensed deployment they run server-side against your own environment.