Who we work withCredit unions
Engineering for credit unions and their technology partners
We build the services credit unions offer their members, and the platforms of the fintechs and programmes behind them: single sign-on from digital banking, member programmes and mobile SDKs, on infrastructure built to pass a credit union’s vendor review.
01
Who we work with
- Credit unions adding digital services for their members
- Fintechs and member programmes that credit unions offer to their members
- Credit union service organisations building shared platforms
02
What your systems have to meet
The NCUA rules and guidance credit unions apply to themselves and to the technology vendors they rely on. We build systems that support these obligations; meeting them remains your organisation’s responsibility.
- NCUA Part 748 · Appendix A
- Safeguarding member information, the Gramm-Leach-Bliley Act requirements as they apply to credit unions.
- NCUA Part 748 · Appendix B
- Responding to unauthorised access to member information, including notifying members.
- NCUA cyber incident notification
- Reporting a reportable cyber incident to the NCUA within 72 hours, which depends on vendors telling the credit union promptly.
- NCUA Part 749
- Records preservation and vital records.
- NCUA Letter to Credit Unions 07-CU-13
- Evaluating third-party relationships: the due diligence and oversight credit unions apply to vendors.
- FFIEC IT Examination Handbook · ACET
- The information-security practices and cybersecurity maturity examiners assess.
03
Typical projects
- Single sign-on from digital banking
Members arrive from online banking already signed in, over SAML or OIDC, with their account created on first visit and identity kept with each credit union.
- Member programmes and rewards
Balances, redemptions and subscriptions where every change to a member’s balance can be traced to a booking or an admin action.
- Mobile SDKs for credit union apps
Android and iOS SDKs that bring a programme into each credit union’s own mobile app.
- Partner integrations
Travel, loyalty and payment partners connected with real-time callbacks, webhooks and reconciliation, with card details left with the payment processor.
- Platforms built for vendor review
AWS environments defined in code: private networks, encryption, no SSH, least-privilege deploys and backups, with the evidence a credit union’s review asks for.
- Operations and admin tools
Refunds, manual adjustments, member syncs and billing reconciliation in purpose-built tools, each action recorded.
04
How we work with your compliance team
We are engineers, not a law firm, compliance consultancy or auditor. We don’t give legal or compliance advice or certify your firm; we work with the people who do.
- Alongside your compliance team
- We engineer the controls, records and evidence. Your CCO and advisers interpret the rules and own the compliance programme.
- Evidence from the system
- Records, review history and deployment logs come from the systems themselves, so requests are answered with data, not reconstructions.
- Ready for your vendor review
- Our practices, security documentation and questionnaire answers are prepared for your due diligence before we start.
Next step
Tell us about the system and the rules it has to meet.
An engineer will reply with how we'd approach it, or who would be a better fit.