Skip to content
StitchOps

Blog

Core banking and identity: connecting the core without an integration project

Core banking platforms rarely connect to identity tools, and official integration programs are slow and costly. How banks bring core access under identity governance anyway.

, Cofounder and CEO ·

Ask a community bank which system matters most for access control and the answer is the core. Ask which system its identity provider cannot reach, and the answer is usually the same.

Why the core is the hardest system to connect

  • It predates identity providers. Core platforms were designed around their own user administration, often in a desktop client or a terminal session.
  • Access is in codes. Teller limits, override rights and module permissions are stored as role and permission codes. An identity tool cannot read them, and a reviewer cannot understand them without translation.
  • Integration goes through the vendor. Official integration programs typically mean vendor approval, fees, a statement of work and months of project time. Some banks are told new integrations are not available at all.
  • Subsystems multiply the work. A core is rarely one system. Deposits, lending, wires, imaging and online banking each have their own users.

One bank told us its core provider offered no supported way to connect access data to its identity tools, so every subsystem was reviewed by hand. Another was quoted custom development for its core that cost more than the governance platform itself.

A different approach: use the screens your staff already use

Your administrators already create users, change roles and disable accounts in the core every week. They do it through the core's own screens. StitchOps does the same thing, through the same screens, with an account your bank creates and controls.

  • No vendor integration project. Nothing new is installed in the core.
  • Deterministic. The same inputs produce the same outputs every time, and every step is logged with evidence.
  • Inside your network. The worker runs as an unattended session on a dedicated worker VM in your environment, connecting outbound only.
  • Credentials stay vaulted. In your vault or the StitchOps per tenant vault, never shown to anyone.

What banks automate first

  1. Access reviews. A read only account collects users and role codes from each core subsystem. Codes are mapped once into plain language, and reviews run in your governance tool. See user access reviews at banks.
  2. Terminations. When HR records a termination, the user is disabled in every core subsystem on the last day, with a record of each step.
  3. Hires and moves. New tellers and lenders get the roles their position needs, and moves change roles instead of adding to them.
  4. Password resets. Verified resets without a help desk call.

Check your core contract for any terms that govern automated administration before you start. Most banks find the conversation is simpler than an integration project, because nothing new connects to the core.

Next step

Tell us which core and subsystems you run and how your administrators manage users today. We will show you what can be automated, what the read only account needs, and where to start. See StitchOps for financial services and pricing.

Frequently asked questions

Why is core banking hard to connect to an identity provider?
Core platforms were built before identity providers, express access as role and permission codes, and usually offer integration only through vendor programs that need approval, fees and project time.
Do we need the core vendor's permission to automate user management?
StitchOps works through the same administrative screens your staff already use, with an account your bank creates, so no new vendor integration is required. Check your core contract for any terms on automated access.
What can be automated in the core?
Collecting who has access for reviews, creating and disabling users on hire and termination, role changes on a move, and password resets, anywhere a person can log in and act.
Does anything change in the core system?
For access reviews, nothing: StitchOps uses a read only account. For provisioning, it makes the same changes an administrator would, and logs each one.

Start with one workflow that never had an API.

Fifteen minutes on your top three manual processes. We tell you which one to run first.