CU*Answers: The customers own the machine

In February 1970, a group of West Michigan credit unions organized a computer cooperative. Its five employees began processing accounts in the basement of their first client. There were 7,500 members to serve. The arrangement had an appealing lack of glamour: put the machinery downstairs, share the expense upstairs, and get on with banking.

That basement contains the essential idea of CU*Answers. A credit union needs technology expensive enough to punish a small institution for buying alone. Other credit unions need much the same thing. Bring them together and the supplier can belong to the people who depend on it. A software invoice becomes a rather more interesting document when the customer has an ownership stake in the sender.

01 / The supplier across the table

CU*Answers operates in the unromantic center of financial technology. Its credit union customers need to maintain member records, process transactions, service loans and give staff a consistent view of an account. Members need to check balances, move money and use banking services from their phones. The glamorous screen depends on a great deal of work behind it.

The company’s May 2026 snapshot puts its direct reach at 222 credit unions in 33 states, representing more than 2.7 million members and $35 billion in client assets. Those assets belong to the institutions it serves. They are not CU*Answers’ valuation. Its customers range from 70 to 78,000 members, a spread that makes the shared-infrastructure proposition unusually concrete.

A 70-member institution cannot spread software development over the same population as a much larger one. Sharing a provider gives it access to a larger development effort while keeping its own identity. CU*Answers offers hosted processing and a self-processing option, so the cooperative arrangement does not dictate a single operating setup.

02 / Ownership is the product behind the product

The familiar alternatives include Jack Henry’s Symitar and Fiserv’s DNA and Portico. All address the serious business of core processing. CU*Answers’ distinctive pitch begins with the relationship around the software: it is 100% credit union-owned.

Customers and owners are overlapping groups, rather than interchangeable words. Participating owners elect board members. Credit unions can also join conversations with subject specialists and product designers about accounting, collections, business members and future CBX work. The structure creates formal opportunities to influence a supplier. It does not promise that every request will become a feature.

The cooperative sells processing and services, collects recurring revenue and supports shared development. Owners may also receive distributions. The 2025 annual meeting minutes record $4.2 million in 2024 patronage dividends and $5.7 million in bonus patronage. Those historical figures show that ownership has had a financial expression; they are no promise about the next payment.

“Pay as you go, pay as you earn.”

CU*Answers’ published pricing philosophy

The company bought the copyright that would become CU*BASE in 1995. WESCO became CU*Answers in 2003. That change of name suited a business extending beyond data processing into practical help running a credit union. The old basement bargain acquired more rooms.

03 / A core, a phone screen, and someone who can help

The current core interface is CBX, the browser-delivered successor to CU*BASE GOLD. CU*Answers describes it as retaining GOLD’s tools and features, including built-in customer relationship management. For staff, that means the transition concerns the everyday workspace through which familiar banking work gets done.

Members encounter a different part of the system: It’s Me 247, the online banking brand introduced in 2007 and extended into mobile services. Document products, including CU*Forms and the Enhanced Online Vault, address another ordinary nuisance: getting information captured, signed and available to staff working in different places.

Consider the vault package. It brings together document storage, electronic signatures, forms, receipts and supported check-image access. The store lists a $750-$900 setup charge and $100-$500 monthly pricing, with additional charges and conditions. Its usefulness lies in a modest proposition: a member should not have to visit a particular desk merely because a document lives there.

The surrounding services matter too. Complete Care offers selectable IT management. Lender*VP supports lending and collections. AuditLink supplies audit and compliance support. Through partners such as Xtend and eDOC Innovations, the network adds operational help and document technology. A credit union can buy tools, then obtain help putting those tools to work.

04 / Read the cents, then read the commitment

The 2026 online pricing guide gives a useful starting point. For new-client contracts outside Alaska and Hawaii, the first 35,000 members carry a monthly member-processing rate of $0.56 with a seven-year commitment, $0.58 with five years, or $0.60 with three. Final pricing follows the signed agreement and is subject to cost-of-living adjustments.

There is a $2,000 monthly processing minimum. Disaster recovery and digital services have their own charges. At 10,000 members, the seven-year member-processing line calculates to $5,600 a month before those other items. A headline rate is the beginning of a budget conversation.

Cooperative ownership also leaves room for price increases. Collections services rose to $3.75 per account worked from June 2026. RTP and FedNow payment-rail fees, waived during 2025, became $0.05 per transaction plus a $100 monthly maintenance fee in January 2026. A shared supplier still has operating expenses.

For a newly formed credit union, the company advertises two initial years of free data processing. Additional services and consulting may cost extra, and the later fee strategy is revisited. The offer lowers one early expense without pretending that opening a financial institution is free.

05 / The browser met the branch

The CBX transition supplies the necessary friction in this story. On January 21, 2026, CU*Answers announced that GOLD would sunset on January 27 for credit unions without recurring CBX session timeout problems. Institutions experiencing those problems received a delayed retirement.

By March 13, its update still acknowledged “session timeout and disconnection issues.” Teams were working with a vendor to identify causes across credit union networks and individual users. Beta testing had produced promising results, and production changes were planned for March 19. Further session-resume improvements were to follow.

The public sequence supports a precise lesson. Repeated stability complaints changed the retirement plan for affected clients. It does not establish that every later issue was resolved. The transition also had workstation requirements: Station Control connects integrations, and browsers must stay current. A browser interface still depends on local setup, connectivity and testing.

For someone planning a migration, the copyable practice is to make exceptions explicit. Separate the date a system becomes available from the date its predecessor disappears. Give affected users a defined path, and judge readiness at the places where people actually work. Ownership can make those conversations meaningful; it cannot repair a session by itself.

06 / Teach before you expect fluency

Training is another part of the bargain. CU*Answers University offers free ongoing education. Custom Training Edition gives employees a place to practice with their institution’s setup without risking live member data. In June 2026, the company announced implementations for GHS Federal Credit Union, Compass Credit Union, Ripco Credit Union and a Servicer Edition client.

The idea applies beyond banking: familiarity with a screen is not the same as confidence in a transaction. Practice environments let people experiment before mistakes carry consequences. A 2023 account of the support team described a six-to-twelve-month learning curve, formal escalation and rotating mentors. The people answering questions need rehearsal too.

CU*Answers makes most sense for institutions prepared to use that shared expertise and participate in a common system. A buyer seeking complete control of every feature still has to assess the roadmap, integrations, contract and local requirements. The cooperative’s enduring suggestion is practical: share expensive machinery, give its users a voice, and budget for the work of learning to use it. The basement was merely the first address.