Context
There are multiple integration methods for Glide to automatically create a debit card in the core. For cards printed or created in branch, staff will continue their existing process of ordering a debit card. This guide will focus on the integration method for debit cards ordered through Glide's member flow (online). The integration method will depend on your existing debit card ordering process.
Jack Henry Symitar
Tracking Record (Preferred Method)
Glide would add a tracking record on the account or share level. Adding a tracking record would then have to signal to your core or card issuer to print and ship the card to the member.
Debit Card PowerOn
Our standard PowerOn relies on the credit union to author the PowerOn logic where Glide calls the credit union PowerOn based on the following features and parameters:
PowerOn name is configurable e.g. SYC.CREATE.CARD.BY.ACCTNUM
Limited to one card type per institution
Print one card per Glide call
Supports Debit or Credit (not ATM)
Can be called for the primary and/or joint (pass TIN in each case)
Optionally, create an access record defining what membership products the card can access.
Inputs:
Card holder full name and optionally tax ID number
Account number
Returns card locator
Inputs:
@RGUSERCHR3 Card Holder Full Name (First M Last)
@RGUSERCHR4 Account Number (member number)
@RGUSERNUM1 Card Type (10=ATM, 15=Debit)
@RGUSERNUM2 Card Locator
@RGUSERNUM3 Card Holder TIN#
Outputs:
@RGUSERNUM1 Error Code
@RGUSERNUM2 Card Locator
@RGUSERCHR1 Error Message
Fiserv XP2
Glide will create a card record in the core, given a certain card type. The defaults in the core will be used. Glide will specify the Individual ID of a holder who is requesting the card.