card_raw

Pipelined Data Sets > Symitar > card_raw

Column name	Description	Mode	Type
institutionid	This field stores the JH Platform institution identifier	REQUIRED	STRING
eventtime	Internal use only	NULLABLE	INTEGER
sourcetype	Internal use only; SSDB field	NULLABLE	STRING
operation	Internal use only; SSDB field	NULLABLE	STRING
extractdate	Internal use only	NULLABLE	DATE
processdatetime	Internal use only; SSDB field	NULLABLE	TIMESTAMP
carduuid	This field stores a JH Platform unique identifier for a card	NULLABLE	STRING
accountuuid	This field stores a JH Platform unique identifier for an account	NULLABLE	STRING
accountnumber	This field stores the Symitar account number (membership account number)	NULLABLE	STRING
cardkey	Internal use only; SSDB field	NULLABLE	INTEGER
accountkey	Internal use only; SSDB field	NULLABLE	INTEGER
sortrank	Internal use only; SSDB field	NULLABLE	INTEGER
deleteid	This field stores a soft delete flag where 0=not deleted, 1=deleted	NULLABLE	INTEGER
symdate	Internal use only; SSDB field	NULLABLE	INTEGER
systemcreatedatetime	Internal use only; SSDB field	NULLABLE	INTEGER
odscreatedatetime	Internal use only; SSDB field	NULLABLE	INTEGER
sym	Internal use only; SSDB field	NULLABLE	INTEGER
odsdeleteflag	Internal use only; SSDB field	NULLABLE	INTEGER
odskey	Internal use only; SSDB field	NULLABLE	INTEGER
number	This field stores the card number based on the type of card and your defined procedures	NULLABLE	STRING
suffix	This field stores the two-digit suffix to the card number, if any	NULLABLE	STRING
type	This field stores a user-defined code to identify the type of card	NULLABLE	INTEGER
nametype	This field stores a code that Symitar uses to determine the name and address for mailing and embossing instructions	NULLABLE	INTEGER
status	This field stores a code that identifies the current status of the card	NULLABLE	INTEGER
issuecode	This field stores a user-defined code to identify any other information about the card or about issuing the card	NULLABLE	INTEGER
reissuecode	This field stores a code that determines how to reissue a card	NULLABLE	INTEGER
issuedate	This field stores the date the card was first issued or, in some instances, when the Card record was created	NULLABLE	DATE
effectivedate	This field stores the date the card was last issued or reissued	NULLABLE	DATE
expirationdate	This field stores the actual date the card expires	NULLABLE	DATE
limitamount	This field stores the maximum amount that can be withdrawn from an offline ATM within the period specified in the Limit Days field	NULLABLE	NUMERIC
limitdays	This field stores the number of days required between withdrawals of the value in the Limit Amount field at an offline ATM	NULLABLE	INTEGER
usagelimit	This field stores the maximum amount that can be withdrawn from an online ATM each day	NULLABLE	NUMERIC
usageamount	This field stores the total amount of all withdrawals based on the value in the Usage Date field from an online ATM	NULLABLE	NUMERIC
usagedate	This field stores the last date when the card was used in an online environment, except for when an online cash deposit is made	NULLABLE	DATE
blockcode	This field stores a processor-defined block code, if any	NULLABLE	STRING
reclasscode	This field stores a processor-defined reclass code, if any	NULLABLE	STRING
pinactual	This field can store the actual PIN (personal identification number) used by the processor for this card	NULLABLE	INTEGER
pinoffset	This field can store a PIN (personal identification number) offset for this card	NULLABLE	INTEGER
pinretries	This field can store the number of times someone attempted to enter an invalid PIN (personal identification number) for this card	NULLABLE	INTEGER
poslimit	This field stores the maximum amount that can be withdrawn for online, point-of-sale transactions each day	NULLABLE	NUMERIC
posamount	This field stores the total amount of all point-of-sale withdrawals, based on the value in the Usage Date field	NULLABLE	NUMERIC
misclimit	This field stores the maximum amount that can be withdrawn from an online environment in miscellaneous transactions each day	NULLABLE	NUMERIC
miscamount	This field stores the daily amount of all miscellaneous withdrawals, based on the value in the Usage Date field	NULLABLE	NUMERIC
reissuemonths	This field stores a code that indicates the number of months for which Symitar should reissue the card	NULLABLE	INTEGER
savid	This field stores the ID of any Share record in the same account that can be accessed through the online environment with this card	NULLABLE	STRING
chkid	This field stores the ID of any share draft record in the same account that can be accessed through the online environment with this card	NULLABLE	STRING
locid	This field stores the ID of any line of credit Loan record in the same account that can be accessed through the online environment with this card	NULLABLE	STRING
miscid_1	These three fields can each store the ID of any Share record or Loan record in the same account that can be accessed through the online environment with this card	NULLABLE	STRING
miscid_2	These three fields can each store the ID of any Share record or Loan record in the same account that can be accessed through the online environment with this card	NULLABLE	STRING
miscid_3	These three fields can each store the ID of any Share record or Loan record in the same account that can be accessed through the online environment with this card	NULLABLE	STRING
deplimit	This field stores the aggregate deposit amount per day that is not subject to holds for ATM envelope or check deposits that are not treated as Regulation CC deposits	NULLABLE	NUMERIC
depamount	This field stores the total amount of all online ATM envelope or check deposits that are not treated as Regulation CC deposits, based on the value in the Usage Date field	NULLABLE	NUMERIC
activedate	This field stores the date the card is considered active	NULLABLE	DATE
prevexpirationdate	This field can store the previous expiration date from the Expiration Date field of a card when you reissue that card	NULLABLE	DATE
prevnumber	This field can store the previous value from the Card Number field of a card when you reissue that card	NULLABLE	STRING
prevsuffix	This field can store the previous value from the Card Suffix field of a card when you reissue that card	NULLABLE	STRING
prevpinactual	This field can store the previous value from the PIN Actual field for a card when you reissue that card	NULLABLE	INTEGER
prevpinoffset	This field can store the previous value from the PIN Offset field for a card when you reissue that card	NULLABLE	INTEGER
warningcode_1	These fields can each store a code that identifies a different user-defined warning to apply to this card	NULLABLE	INTEGER
warningcode_2	These fields can each store a code that identifies a different user-defined warning to apply to this card	NULLABLE	INTEGER
warningcode_3	These fields can each store a code that identifies a different user-defined warning to apply to this card	NULLABLE	INTEGER
warningcode_4	These fields can each store a code that identifies a different user-defined warning to apply to this card	NULLABLE	INTEGER
warningcode_5	These fields can each store a code that identifies a different user-defined warning to apply to this card	NULLABLE	INTEGER
warningcode_6	These fields can each store a code that identifies a different user-defined warning to apply to this card	NULLABLE	INTEGER
warningcode_7	These fields can each store a code that identifies a different user-defined warning to apply to this card	NULLABLE	INTEGER
warningcode_8	These fields can each store a code that identifies a different user-defined warning to apply to this card	NULLABLE	INTEGER
warningcode_9	These fields can each store a code that identifies a different user-defined warning to apply to this card	NULLABLE	INTEGER
warningcode_10	These fields can each store a code that identifies a different user-defined warning to apply to this card	NULLABLE	INTEGER
warningcode_11	These fields can each store a code that identifies a different user-defined warning to apply to this card	NULLABLE	INTEGER
warningcode_12	These fields can each store a code that identifies a different user-defined warning to apply to this card	NULLABLE	INTEGER
warningcode_13	These fields can each store a code that identifies a different user-defined warning to apply to this card	NULLABLE	INTEGER
warningcode_14	These fields can each store a code that identifies a different user-defined warning to apply to this card	NULLABLE	INTEGER
warningcode_15	These fields can each store a code that identifies a different user-defined warning to apply to this card	NULLABLE	INTEGER
warningcode_16	These fields can each store a code that identifies a different user-defined warning to apply to this card	NULLABLE	INTEGER
warningcode_17	These fields can each store a code that identifies a different user-defined warning to apply to this card	NULLABLE	INTEGER
warningcode_18	These fields can each store a code that identifies a different user-defined warning to apply to this card	NULLABLE	INTEGER
warningcode_19	These fields can each store a code that identifies a different user-defined warning to apply to this card	NULLABLE	INTEGER
warningcode_20	These fields can each store a code that identifies a different user-defined warning to apply to this card	NULLABLE	INTEGER
warningexpiration_1	These fields can each store a date after which the corresponding warning should no longer apply to the card	NULLABLE	DATE
warningexpiration_2	These fields can each store a date after which the corresponding warning should no longer apply to the card	NULLABLE	DATE
warningexpiration_3	These fields can each store a date after which the corresponding warning should no longer apply to the card	NULLABLE	DATE
warningexpiration_4	These fields can each store a date after which the corresponding warning should no longer apply to the card	NULLABLE	DATE
warningexpiration_5	These fields can each store a date after which the corresponding warning should no longer apply to the card	NULLABLE	DATE
warningexpiration_6	These fields can each store a date after which the corresponding warning should no longer apply to the card	NULLABLE	DATE
warningexpiration_7	These fields can each store a date after which the corresponding warning should no longer apply to the card	NULLABLE	DATE
warningexpiration_8	These fields can each store a date after which the corresponding warning should no longer apply to the card	NULLABLE	DATE
warningexpiration_9	These fields can each store a date after which the corresponding warning should no longer apply to the card	NULLABLE	DATE
warningexpiration_10	These fields can each store a date after which the corresponding warning should no longer apply to the card	NULLABLE	DATE
warningexpiration_11	These fields can each store a date after which the corresponding warning should no longer apply to the card	NULLABLE	DATE
warningexpiration_12	These fields can each store a date after which the corresponding warning should no longer apply to the card	NULLABLE	DATE
warningexpiration_13	These fields can each store a date after which the corresponding warning should no longer apply to the card	NULLABLE	DATE
warningexpiration_14	These fields can each store a date after which the corresponding warning should no longer apply to the card	NULLABLE	DATE
warningexpiration_15	These fields can each store a date after which the corresponding warning should no longer apply to the card	NULLABLE	DATE
warningexpiration_16	These fields can each store a date after which the corresponding warning should no longer apply to the card	NULLABLE	DATE
warningexpiration_17	These fields can each store a date after which the corresponding warning should no longer apply to the card	NULLABLE	DATE
warningexpiration_18	These fields can each store a date after which the corresponding warning should no longer apply to the card	NULLABLE	DATE
warningexpiration_19	These fields can each store a date after which the corresponding warning should no longer apply to the card	NULLABLE	DATE
warningexpiration_20	These fields can each store a date after which the corresponding warning should no longer apply to the card	NULLABLE	DATE
service_1	These fields can each store a code that identifies a different user-defined service offered with the card	NULLABLE	INTEGER
service_2	These fields can each store a code that identifies a different user-defined service offered with the card	NULLABLE	INTEGER
service_3	These fields can each store a code that identifies a different user-defined service offered with the card	NULLABLE	INTEGER
service_4	These fields can each store a code that identifies a different user-defined service offered with the card	NULLABLE	INTEGER
service_5	These fields can each store a code that identifies a different user-defined service offered with the card	NULLABLE	INTEGER
service_6	These fields can each store a code that identifies a different user-defined service offered with the card	NULLABLE	INTEGER
service_7	These fields can each store a code that identifies a different user-defined service offered with the card	NULLABLE	INTEGER
service_8	These fields can each store a code that identifies a different user-defined service offered with the card	NULLABLE	INTEGER
authlimit	This field stores the maximum amount that can be authorized for online credit or debit card merchant (signature-based) transactions each day	NULLABLE	NUMERIC
authamount	This field stores the daily amount of authorizations performed for an online credit or debit card merchant (signature-based) transactions, based on the value in the Usage Date field	NULLABLE	NUMERIC
authcountlimit	This field stores the maximum number of authorizations allowed for an online credit or debit card merchant (signature-based) transactions per day	NULLABLE	INTEGER
authcount	This field stores the number of daily authorizations performed for an online credit or debit card merchant (signature-based) transactions, based on the value in the Usage Date field	NULLABLE	INTEGER
atmcountlimit	This field stores the maximum number of online ATM transactions you allow each day	NULLABLE	INTEGER
atmcount	This field stores the number of daily ATM transactions, based on the value in the Usage Date field	NULLABLE	INTEGER
poscountlimit	This field stores the maximum number of point-of-sale transactions per day that your financial institution allows	NULLABLE	INTEGER
poscount	This field stores the number of daily (Close Day Processing to Close Day Processing) point-of-sale transactions, based on the value in the Usage Date field	NULLABLE	INTEGER
misccountlimit	This field stores the maximum number of miscellaneous transactions per day that your financial institution allows	NULLABLE	INTEGER
misccount	This field stores the number of daily miscellaneous transactions, based on the value in the Usage Date field	NULLABLE	INTEGER
creddeblimit	This field stores the monetary completion transaction limit per day for an online debit or credit card	NULLABLE	NUMERIC
creddebamount	This field stores the daily amount of monetary completion transactions for an online debit or credit card	NULLABLE	NUMERIC
creddebcountlimit	This field stores the maximum number of monetary completion transactions your financial institution allows per day for an online debit or credit card	NULLABLE	INTEGER
creddebcount	This field stores the number of daily transactions for an online debit or credit card, based on the value in the Usage Date field	NULLABLE	INTEGER
feecount_1	Each of these four fields can store the current number of a fees for a different type of fee	NULLABLE	INTEGER
feecount_2	Each of these four fields can store the current number of a fees for a different type of fee	NULLABLE	INTEGER
feecount_3	Each of these four fields can store the current number of a fees for a different type of fee	NULLABLE	INTEGER
feecount_4	Each of these four fields can store the current number of a fees for a different type of fee	NULLABLE	INTEGER
creditcardid	This field stores the ID of any credit card Loan record in the same account that can be accessed through the online environment with this card	NULLABLE	STRING
singleusagemax	This field stores the maximum amount allowed for a single cash withdrawal	NULLABLE	NUMERIC
wdcheckmax	This field stores the maximum amount allowed for a single withdrawal by check per day	NULLABLE	NUMERIC
wdchecklimit	This field stores the limit for withdrawals by check per day	NULLABLE	NUMERIC
wdcheckamount	This field stores the total amount of withdrawals by check (greater than $0.00), based on the value in the Usage Date field	NULLABLE	NUMERIC
wdcheckcountlimit	This field stores the maximum number of withdrawals by check allowed per day	NULLABLE	INTEGER
wdcheckcount	This field stores the number of withdrawals by check performed, based on the value in the Usage Date field	NULLABLE	INTEGER
xfermax	This field stores the maximum amount for a single transfer that your financial institution allows	NULLABLE	NUMERIC
xferlimit	This field stores the maximum amount that can be transferred each day	NULLABLE	NUMERIC
xferamount	This field stores the total transfer amount (greater than $0.00), based on the value in the Usage Date field	NULLABLE	NUMERIC
xfercountlimit	This field stores the maximum number of transfers allowed per day	NULLABLE	INTEGER
xfercount	This field stores the number of transfers performed, based on the value in the Usage Date field	NULLABLE	INTEGER
billpaymax	This field stores the Maximum amount (greater than $0.00) for a single bill payment	NULLABLE	NUMERIC
billpaylimit	This field stores the daily bill payment limit	NULLABLE	NUMERIC
billpayamount	This field stores the total bill payment amount (greater than $0.00), based on the value in the Usage Date field	NULLABLE	NUMERIC
billpaycountlimit	This field stores the maximum number of bill payments allowed per day	NULLABLE	INTEGER
billpaycount	This field stores the number of bill payments performed, based on the value in the Usage Date field	NULLABLE	INTEGER
depmax	This field stores the maximum amount allowed in a single deposit	NULLABLE	NUMERIC
depcountlimit	This field stores the maximum number of deposits allowed per day	NULLABLE	INTEGER
depcount	This field stores the number of deposits performed, based on the value in the Usage Date field	NULLABLE	INTEGER
prevactivationdate	This field stores the previous activation date for a card with a matching value from the Prev Expiration Date field	NULLABLE	DATE
extraemboss	This field stores a second emboss line on a card order	NULLABLE	STRING
closedate	This field stores the date the Card record was closed	NULLABLE	DATE
statusreason	This field stores a code that indicates why a card was set to (2) Capture status	NULLABLE	INTEGER
pinorderdate	This field stores the date the last time a personal identification number (PIN) was ordered	NULLABLE	DATE
locator	This field stores a unique number within each member account that can be used as a unique identification of this record	NULLABLE	INTEGER
description	This field stores a card description that displays in card inquiries and on card FM screens when all fields display	NULLABLE	STRING
lastaddrchgdate	This field stores the date of the last file maintenance only when the value in the Name Type field changes	NULLABLE	DATE
recordchangedate	Symitar stores the system date in this field when you create, change, or save the Card record. Sometimes Symitar updates this field because the record was saved, even though there may not be any actual changes in the record	NULLABLE	DATE
createdbyuser	Symitar stores the user ID and is populated when this Card record is created in this field	NULLABLE	INTEGER
createdatbranch	This field stores the branch ID of the branch where the Card record is created	NULLABLE	INTEGER
instantissue	This field stores a code that indicates whether the card was an instant issue or not	NULLABLE	INTEGER
imagerefnumber	This field stores the value of a photo reference number for members who create an imaged card background	NULLABLE	STRING
imagerefdate	This field stores the date that an imaged card background was created online	NULLABLE	DATE
imagerefissuecount	This field stores the number of times that a card with an imaged background has been issued before the card expiration	NULLABLE	INTEGER
emvchipprofile	This field stores the EMV chip profile (network processing options) associated with the card. If this field is non-blank, the card is using the EMV chip	NULLABLE	STRING
pinencrypted	This field stores the encrypted value for a PIN (personal identification number). This value depends on the encryption method you use, which can come from the ATM network or a third party	NULLABLE	STRING
fileupdatemanagerexception	This field stores a code that indicates whether the ATM File Update Manager software encounters an exception associated with the card data that it sent or received from the network and gives a general idea (status) about the reason. This indication applies to both high priority messages and messages sent in regular processing	NULLABLE	INTEGER
countlimit_1	These fields store the number of daily transactions allowed for each limit	NULLABLE	INTEGER
countlimit_2	These fields store the number of daily transactions allowed for each limit	NULLABLE	INTEGER
countlimit_3	These fields store the number of daily transactions allowed for each limit	NULLABLE	INTEGER
countlimit_4	These fields store the number of daily transactions allowed for each limit	NULLABLE	INTEGER
countlimit_5	These fields store the number of daily transactions allowed for each limit	NULLABLE	INTEGER
countlimit_6	These fields store the number of daily transactions allowed for each limit	NULLABLE	INTEGER
limitcount_1	These fields store the current number of transactions for each limit	NULLABLE	INTEGER
limitcount_2	These fields store the current number of transactions for each limit	NULLABLE	INTEGER
limitcount_3	These fields store the current number of transactions for each limit	NULLABLE	INTEGER
limitcount_4	These fields store the current number of transactions for each limit	NULLABLE	INTEGER
limitcount_5	These fields store the current number of transactions for each limit	NULLABLE	INTEGER
limitcount_6	These fields store the current number of transactions for each limit	NULLABLE	INTEGER
limit_1	These fields store a daily limit amount, which is the total transaction amount allowed for the day, for each limit	NULLABLE	NUMERIC
limit_2	These fields store a daily limit amount, which is the total transaction amount allowed for the day, for each limit	NULLABLE	NUMERIC
limit_3	These fields store a daily limit amount, which is the total transaction amount allowed for the day, for each limit	NULLABLE	NUMERIC
limit_4	These fields store a daily limit amount, which is the total transaction amount allowed for the day, for each limit	NULLABLE	NUMERIC
limit_5	These fields store a daily limit amount, which is the total transaction amount allowed for the day, for each limit	NULLABLE	NUMERIC
limit_6	These fields store a daily limit amount, which is the total transaction amount allowed for the day, for each limit	NULLABLE	NUMERIC
limitusageamount_1	These fields store the current total transaction amount approved for each limit	NULLABLE	NUMERIC
limitusageamount_2	These fields store the current total transaction amount approved for each limit	NULLABLE	NUMERIC
limitusageamount_3	These fields store the current total transaction amount approved for each limit	NULLABLE	NUMERIC
limitusageamount_4	These fields store the current total transaction amount approved for each limit	NULLABLE	NUMERIC
limitusageamount_5	These fields store the current total transaction amount approved for each limit	NULLABLE	NUMERIC
limitusageamount_6	These fields store the current total transaction amount approved for each limit	NULLABLE	NUMERIC
peritemlimit_1	These fields store the maximum amount allowed for a single transaction for each limit	NULLABLE	NUMERIC
peritemlimit_2	These fields store the maximum amount allowed for a single transaction for each limit	NULLABLE	NUMERIC
peritemlimit_3	These fields store the maximum amount allowed for a single transaction for each limit	NULLABLE	NUMERIC
peritemlimit_4	These fields store the maximum amount allowed for a single transaction for each limit	NULLABLE	NUMERIC
peritemlimit_5	These fields store the maximum amount allowed for a single transaction for each limit	NULLABLE	NUMERIC
peritemlimit_6	These fields store the maximum amount allowed for a single transaction for each limit	NULLABLE	NUMERIC
digitalissuestatus	This field stores a code that indicates whether the card was digitally issued or whether the request for digital issuance was successful	NULLABLE	INTEGER
digitalissueexcept	This field stores the reason for an exception associated with a digital issuance request. Symitar outputs unique text for the exceptions that appear in this field based on invalid or missing information in a corresponding user-defined Account Tracking record or the value in the Response Code message field that it receives from the online network	NULLABLE	STRING
templimitstartdate	This field stores the date at which a temporary limit begins for ATM, POS, or authorization transactions. The date in this field is used in conjunction with the date in the Temporary Limit End Date field to specify a date range for which the temporary limits are in effect	NULLABLE	DATE
templimitenddate	This field stores the date at which a temporary limit expires for ATM, POS, or authorization transactions. The date in this field is used in conjunction with the date in the Temporary Limit Start Date field to specify a date range for which the temporary limits are in effect	NULLABLE	DATE
atmtemplimit	This field stores the maximum amount that can be withdrawn from an online ATM each day during the date range specified in the Temporary Limit Start Date and Temporary Limit End Date fields	NULLABLE	NUMERIC
postemplimit	This field stores the maximum amount that can be withdrawn for online point-of-sale transactions each day during the date range specified in the Temporary Limit Star Date and Temporary Limit End Date fields	NULLABLE	NUMERIC
authtemplimit	This field stores the maximum amount that can be authorized for online credit or debit card merchant (signature-based) transactions each day during the date range specified in the Temporary Limit Start Date and Temporary Limit End Date fields	NULLABLE	NUMERIC
onlinecardissue	This field allows the system to specify whether a card was issued using an online file update message. If the card was ordered online, this field would also display the status of the online card order	NULLABLE	INTEGER
onlinerushissue	This field determines whether a rush order was requested for the card to be delivered to the cardholder	NULLABLE	INTEGER
plasticcount		NULLABLE	INTEGER

Have a Question?

Have a how-to question? Seeing a weird error? Get help on our collaborative Discourse page.
Register for the Developer Office Hours where we answer technical Q&A, in real time, from the audience.

Please ignore this field

Did this page help you?

Last updated Tue Sep 15 2026