Bank RPA

Bank RPA, and the line item nobody quotes you

People searching this land on company profiles. Here is the part those profiles skip: bots that drive banking-core screens have to be rebuilt every time the core changes, which is exactly why bank RPA is sold as a standing relationship and not a one-time install.

Matthew Diakonov, Written with AI

Published June 17, 20266 min read

Direct answer (verified June 17, 2026)

BankRPA is a vendor-agnostic RPA consulting firm in Grand Rapids, Michigan, founded in 2020. Its consultants are former banking and credit-union staff who build robotic process automation on core systems from Jack Henry, Fiserv, and FIS, frequently using Nintex RPA. More broadly, bank RPA means robotic process automation applied to banking-core and back-office workflows so a software bot does the repetitive keystroke work a clerk would.

Source: bankrpa.com/about-us. Mediar is not affiliated with BankRPA; this guide explains the category and a different way to build it.

What bank RPA actually runs on

The work is unglamorous and high-volume: the same screens, the same keystrokes, hundreds of times a week. These are the workloads documented in BankRPA's published Nintex deployment, on the core systems community and regional banks actually run.

Banking cores it runs on

FIS Bankway and Horizon, Fiserv DNA, Premier and Signature, Jack Henry Silverlake and Xperience, plus the content and payments systems bolted to them.

Debit card issuance

200 to 300 requests a week. Account verification, fraud-alert checks, address updates. A bot clears the overnight queue before staff log in.

Visa token deactivation

Monthly batches of roughly 700 tokens, each deactivated by hand. Automated in three to four days, cutting unnecessary billing charges.

Social Security / Medicaid reporting

Pulling monthly balance and accrued-interest figures from the core into spreadsheets. A six-account request used to take about two hours.

CD renewals

Pre-approved certificate-of-deposit renewals processed overnight instead of by a clerk during business hours.

The recurring cost hiding in the service menu

Read any bank RPA consultancy's service list carefully. Next to "automation script development" you will find "legacy script upgrades" and dedicated RPA support sitting there as their own line items. That is not padding. It is the honest shape of the technology.

Traditional RPA records the exact buttons, field positions, and window coordinates of a core-system screen. It is a script that says "click the control at this location, type into the field with this label." When FIS ships a Bankway update, when Fiserv moves a panel in DNA, when Jack Henry relabels a field in Xperience, the coordinates the script memorized no longer point at the right thing. The bot fails silently or, worse, types into the wrong field. Someone has to re-record it. That someone bills you.

So the maintenance is not a defect in any one vendor. It is built into the selector-and-coordinate approach itself. The bot never understood the screen; it memorized where things were. Move them and it is lost.

3 to 4 days

“Time BankRPA took to automate a recurring batch of roughly 700 Visa token deactivations on a banking core. The build is fast. The question every bank should ask is what happens to that bot at the next core upgrade.”

BankRPA / Nintex customer story, verified June 17 2026

Two ways to drive the same core screen

Selector-based bot vs. watch-once agent

The bot is recorded against the current layout of the core screen. It clicks coordinates and matches field labels exactly as they were on the day it was built.

Breaks when a core update moves or renames a control
Needs re-recording after each version bump
Support and 'legacy script upgrades' become recurring costs
Fails silently or types into the wrong field when the UI drifts

Why the maintenance question matters more for banks

Core systems are not stable targets. FIS, Fiserv, and Jack Henry push updates on their own cadence, and a community or regional bank does not control the schedule. Every one of those updates is a potential break for a selector-based bot, and a break in a banking workflow is not cosmetic: it is a missed CD renewal, a token left active and billing, a debit-card queue that backs up overnight.

Reading the accessibility tree changes what an update means. When the agent identifies a field by its exposed role and name rather than its pixel position, a relabeled or relocated control usually still resolves. The same approach is why this works on green-screen and legacy Windows cores at all: there is no API to call, so the only reliable way in is the interface the operating system already exposes for assistive technology.

Mediar has moved bank onboarding from eight weeks to two on this model, and the Terminator SDK behind it is open source on GitHub for teams that want to extend their own automations. It is SOC 2 Type II certified, with on-prem or cloud deployment.

See your worst core-system workflow run without a script

Bring one Jack Henry, Fiserv, or FIS workflow that keeps breaking. We will show you what a watch-once agent does with it on a call.

Bank RPA: common questions

What is BankRPA?

BankRPA is a vendor-agnostic RPA consulting firm based in Grand Rapids, Michigan, founded in 2020. Its consultants are former banking and credit-union staff who implement robotic process automation on core systems from Jack Henry, Fiserv, and FIS, frequently using Nintex RPA. Services include automation script development, legacy script upgrades, RPA training, and implementation consulting.

What does 'bank RPA' mean in general?

Bank RPA is robotic process automation applied to banking-core and back-office workflows: debit-card issuance, CD renewals, token deactivation, regulatory reporting, deposit and lending operations. A software bot drives the same core-system screens a clerk would, following a recorded script, so repetitive keystroke work runs unattended.

Which core banking systems can RPA automate?

Documented deployments cover FIS Bankway and Horizon, Fiserv DNA, Premier and Signature, and Jack Henry Silverlake and Xperience, along with the enterprise content management and payments systems attached to them. These are green-screen and Windows-desktop applications without modern APIs, which is why bots drive the UI directly.

Why does bank RPA need 'legacy script upgrades'?

Traditional RPA records the exact buttons, fields, and window coordinates of a core-system screen. When the core vendor ships a version update and those labels or layouts shift, every script that touched the changed screen breaks. That is why an RPA consultancy lists legacy script upgrades and standing support as recurring line items: the bots need re-recording each time the underlying UI moves.

How is Mediar different from script-based bank RPA?

Mediar's AI agents watch a workflow once, then execute it by reading what each application exposes through Windows accessibility APIs, the same interfaces screen readers use. There are no pixel matchers or hard-coded selectors, so when a core system relabels a field or moves a panel, the agent still finds it by meaning rather than by coordinate. That removes most of the re-recording work that script-based bots require after a core upgrade.

Is Mediar affiliated with BankRPA?

No. BankRPA is a separate RPA consulting firm. This page explains the bank RPA category and contrasts the script-based approach with Mediar's accessibility-API agents. If you are evaluating either, talk to both.

What does Mediar cost for a bank?

Pricing is $0.75 per minute of runtime with no per-seat licensing. The $10,000 turn-key program fee converts to credits, so it functions as prepaid usage. Mediar is SOC 2 Type II certified, and the Terminator SDK is open source on GitHub for teams that want to extend their automations.