The surfaces your customers see under your brand, and the XYB Console your operators work in. Both extended by your engineers.
Experience Layer
The branded surface: configured, not coded.
Brand
Your logo, palette and type on every end-customer surface.
Configure
Change journeys, flows and flags. No redeploy.
Compose
Take only the surfaces you need, on any core.
User actions flow down; events flow up. The Experience Layer sits above Orchestration and Runtime.
The bank's human-facing surfaces: customer journeys under the bank's brand, operator work on the XYB Console.
The event-native substrate: every state change a governed, replayable event.
Container-first, the base the platform is built on: scales with demand, deploys where regulations or strategy require.
End-customer surfaces carry your brand and XYB stays invisible. Operator surfaces are the XYB Console, XYB-branded by design.
End-customer surfaces
Operator surfaces
Your engineers extend
Configuration goes deep. Selection stays yours. What that means, in the next two sections.
Configuration-driven, top to bottom. That's what makes the end-customer surfaces the bank's, not XYB's; the XYB Console stays XYB-branded by design.
Branding
Logo, palette, type, and design-system tokens propagate across every surface. No code required.
Layout
Screen composition, journey blocks, and navigation are configured per audience and channel. Not rebuilt.
Content
Copy, rules, and feature flags are content, not code. Adjust the surfaces without redeploying the platform.
The Experience Layer is where XYB's Solutions surface. Adaptive Digital Banking renders its branded consumer apps here; the Commercial Treasury Solution renders its treasury dashboard here.
A branded, configurable surface above the event-native substrate.