Debit Card Creation Implementation

Last updated: December 9, 2025

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.

Card Record Creation

We are able to create a card record directly in the core for primary and roles.

Card Record

Symitar Core Field

Populates with

ChkId

Accounts.external_core_id

Number

Determined by FI, typically 'NEXT'

Type

Determined by FI

Card Access Record

Symitar Core Field

Populates with

AccessType

Determined by FI, based on specific account

AccountNumber

Users.external_core_id (account number in core)

EnableDeposit

Determined by FI

EnableFm

Determined by FI

EnableInquiry

Determined by FI

EnableWithdrawal

Determined by FI

Id

Accounts.external_core_id

IdType

Determined by FI

We are also able to create a Card Name Record with the same information sent to the name record.

Corelation Keystone

We are able to create a card record directly in the core for both primary and roles.

CARD Table

Keystone Core Field

Populates with

PRIMARY_ACCOUNT_SERIAL

ACCOUNT SERIAL

TYPE_SERIAL

Determined by FI

CARD_PLASTIC Table

Keystone Core Field

Populates with

PARENT_SERIAL

CARD SERIAL

DESIGN_SERIAL

Determined by FI

PERSON_SERIAL

PERSON SERIAL (SERIAL from person requesting card)

PERSON_ADDRESS_LINK_SERIAL

ADDRESS_LINK_SERIAL (From the mailing address of the PERSON requesting)

CARD_ACCESS Table

Keystone Core Field

Populates with

PARENT_SERIAL

CARD SERIAL

SHARE_SERIAL

SHARE SERIAL (Serial of share that the card needs access to. Defaults to all checking/savings that aren't money market)

CATEGORY

SV, CK (Savings/Checking)

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.