Looking for news about other EFT projects?
Overview
Digital Card Issuance (DCI) is the latest card technology that provides virtual access to a newly issued credit or debit card, allowing the member to have immediate access to funds. Members can request a new card online at any time, day or night. No more waiting for the new card to arrive in the mail before it can be used to make purchases.
Provisioning to Digital Wallet, or “push provisioning,” refers to the ability for credit unions to “push” the newly issued card # to a mobile wallet provider, such as Apple Pay, Samsung Pay, and Google Pay, so it is available for immediate use by the member.
Building a platform that supports both Digital Card Issuance and Push Provisioning will enhance the full card experience for members. The two processes together allow the member to request a new card via online banking, then start to use their new card right away via the supported mobile wallet.
Supported Features
- Card Replacement for lost/stolen/damaged card (block the old card # and issue a new one)
- Provision to Digital Wallet (if digitally issued via this new process, only)
Digital Card Issuance must be coordinated between the card vendor and core online banking provider. We’re starting with CO-OP, but will be building the structure as generically as possible to work with other vendors as well. We will be working vendor-by-vendor with each vendor as a separate project.
Attacking the Project
In order to manage the development and deployment processes, we will be breaking up the development project into multiple, inter-dependent projects, tackling them in roughly this order. The first two projects cover the CU*BASE components, EFT components, and basic mobile app components, respectively, and are interdependent:
After that will come future projects to allow members to place card orders online, automated push provisioning via our mobile app and the ability to digitally issue cards as part of accepting a 1Click credit card offer.
As we get further along in the design process, more details will be posted on this Kitchen page, so stay tuned!
NOTE: We completed a lengthy study into PCI (Payment Card Industry) certification requirements, especially related to these DCI/provisioning projects. With the controls we already have in place and by using third-party vendor tools, we have determined a path forward that will allow us to proceed without the need for official certification at this time.
Push Provisioning
After many months of searching, studying, and frequent disappointments, we have finally identified a solution to allow for provisioning digitally-issued cards to digital wallets! The solution we’ve found is a vendor-agnostic tool which will allow for us to create a more uniform structure and help simplify implementation on our side. While the overall solution will work for any vendor, we will still need to work with this company and each vendor initially to ensure the process is working as we designed. We are still working through agreements and pricing but will begin working on specs very soon.
Projects and Status
As of February 2025:
| Proj# | Description | Status/Notes |
| 58388 | Create Mechanism for DCI Card Requests via CU*BASE (configs and infrastructure) | In production with 23.05 (Completed) |
| 58485 | Real-time card adds/maintenance for CO-OP | Completed |
| 59971 | Real-time card adds/maintenance for PSCU | Waiting for programmer |
| 60411 | Real-time card adds/maintenance for JHA | Waiting for programmer |
| 60660 | Real-time card adds/maintenance for Fiserv | In development |
| 60840 | OLB Standalone Web Module to allow members to cancel CO-OP cards and be issued a new card | Implemented; working with select CUs for beta testing now |
| 61262 | Real-time card adds/maintenance for Shazam | Waiting for programmer |
| 61264 | Real-time card adds/maintenance for MAP | In development |
| 62873 | Ability to Digitally Activate the Card for CO-OP | Waiting for Programmer |
| 61576 | OLB Standalone Web Module to allow members to cancel MAP cards and be issued a new card | Waiting for Programmer |
| 61575 | OLB Standalone Web Module to allow members to cancel FISERV cards and be issued a new card | Waiting for Programmer |
| 62368 | OLB Standalone Web Module to allow members to cancel JHA cards and be issued a new card | Waiting for Programmer |
| 61574 | OLB Standalone Web Module to allow members to cancel Shazam cards and be issued a new card | Waiting for Programmer |
| 63797 | Real-time card adds/maintenance for FIS Payments1 Platform | Waiting for Programmer |
| 63798 | OLB Standalone Web Module to allow members to cancel FIS cards and be issued a new card | Waiting for Programmer |
News for Co-op Clients
Since our first foray into push real-time card creation and push provisioning will be with Co-Op, we have been working with Co-Op on the requirements CUs will need to meet in order to activate this new functionality.
More details coming soon in the Store!
Your chefs for this recipe: Heather French
Do we also need to be signed up with our card processor to use this feature? We use COOP. They have digitization available. Do we need to complete a project with them to be able to use this with CU*A?
Thanks for the question! It’s a little early to say one way or the other, as we’re still writing the design specs. I believe our first interface for this will be with CO-OP, and it’s also possible that some vendors might not support the process at all. Expect to hear a lot more about it later in the year as we get further along.
Is there a new COOP task force or group working with CU*Answers? I heard this was a thing and curious if we can participate if it is available
Yes, Hollie! I happened to visit this page today following a Co-op/CU*A Task Force meeting. I’ll see that you get added to the list!
A thought here. One of the most annoying parts about card replacement for any reason is updating all the recurring transactions or subscriptions (Netflix, amazon etc). I know the idea is for the member to eventually be able to self-serve and issue themselves a new card via the mobile app directly into their digital wallet. Any way to present to the user a list of recurring transactions during this process that will need updated once the new “card” is issued? Could start simple here with just a list (I believe recurring transactions are coded) so the members are reminded to go and update them with the vendors. This would be a nice feature to add into Gold as well so that contact center users could remind members about these transactions before they issue the replacement card in Gold. Dreaming here but an even better solution would be to update the information for the member…wouldn’t that be cool?
It’s my understanding that the VAU/ABU (Visa® Account Updater and Mastercard® Automatic Billing Updater) service was designed by Visa and Mastercard to assist with adjusting recurring payments to the new card number. When your credit union orders a card today in CU*BASE you can select if the card is being opted in or out of that service, and that determines what Visa/Mastercard does.
As to our plans for allowing members to cancel and order a new card themselves online, we haven’t really talked yet about how to handle that process, but will add this to our discussions to see if we can either offer the option to the member, or let your CU decide whether to automatically opt them in, or some variation. Theoretically we could probably present a list of recurring payments, too, but I think this service would probably be a better solution. Either way, thanks for the idea!