Developer Resources
Details
SoapAction | http://jackhenry.com/ws/EFTCardAdd |
Input Name | EFTCardAdd |
Output Name | EFTCardAddResponse |
Input Namespace | http://jackhenry.com/jxchange/TPG/2008 |
Group Name | Customer |
Container | TPG_CustomerMaster.xsd |
XML Examples
EFTCardAdd-XML-CD
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:UsernameToken xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:Username>{Insert}</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">{Insert}</wsse:Password>
<wsu:Created xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">2020-12-20T16:45:20Z
</wsu:Created>
</wsse:UsernameToken>
</wsse:Security>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<EFTCardAdd xmlns="http://jackhenry.com/jxchange/TPG/2008">
<MsgRqHdr>
<jXchangeHdr>
<JxVer/>
<AuditUsrId></AuditUsrId>
<AuditWsId></AuditWsId>
<AuthenUsrId/>
<ConsumerName/>
<ConsumerProd/>
<Ver_1/>
<jXLogTrackingId>{Insert}</jXLogTrackingId>
<Ver_2/>
<InstRtId>11111900</InstRtId>
<InstEnv>TEST</InstEnv>
<Ver_3/>
<BusCorrelId/>
<Ver_4/>
<WorkflowCorrelId/>
<Ver_5/>
<ValidConsmName>{Insert}</ValidConsmName>
<ValidConsmProd>{Insert}</ValidConsmProd>
<Ver_6/>
</jXchangeHdr>
<Ver_1/>
<Ver_2/>
<Ver_3/>
</MsgRqHdr>
<ErrOvrRdInfoArray>
<ErrOvrRd>
<ErrCode/>
<Ver_1/>
</ErrOvrRd>
</ErrOvrRdInfoArray>
<CustId>299709810</CustId>
<EFTCardType>1</EFTCardType>
<EFTCardAddInfoArray>
<EFTCardAddInfoRec>
<EmbosName>Albert</EmbosName>
<SecdEmbosName/>
<Ver_1/>
</EFTCardAddInfoRec>
<EFTCardAddInfoRec>
<EmbosName/>
<SecdEmbosName/>
<Ver_1/>
</EFTCardAddInfoRec>
</EFTCardAddInfoArray>
<EFTCardAcctIdArray>
<EFTCardAcctIdInfo>
<EFTCardAcctId>10001790</EFTCardAcctId>
<EFTCardAcctType>10</EFTCardAcctType>
<EFTCardPrimAcct>true</EFTCardPrimAcct>
<Dlt/>
<Ver_1/>
<AliasAcctName/>
<Ver_2/>
</EFTCardAcctIdInfo>
<EFTCardAcctIdInfo>
<EFTCardAcctId/>
<EFTCardAcctType/>
<EFTCardPrimAcct/>
<Dlt/>
<Ver_1/>
<AliasAcctName/>
<Ver_2/>
</EFTCardAcctIdInfo>
</EFTCardAcctIdArray>
<Custom/>
<Ver_1/>
<EFTCardProdCode JHANull="true"></EFTCardProdCode>
<Ver_2/>
</EFTCardAdd>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
EFTCardAdd-XML-Request
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Header>
<wsse:Security
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:UsernameToken
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:Username>{Insert}</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">{Insert}</wsse:Password>
<wsu:Created
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">2017-09-20T16:45:20Z
</wsu:Created>
</wsse:UsernameToken>
</wsse:Security>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<EFTCardAdd
xmlns="http://jackhenry.com/jxchange/TPG/2008">
<MsgRqHdr>
<jXchangeHdr>
<JxVer/>
<AuditUsrId></AuditUsrId>
<AuditWsId></AuditWsId>
<AuthenUsrId/>
<ConsumerName/>
<ConsumerProd/>
<Ver_1/>
<jXLogTrackingId>{Insert}</jXLogTrackingId>
<Ver_2/>
<InstRtId JHANull="" Rstr="">{Insert}</InstRtId>
<InstEnv>{Insert}</InstEnv>
<Ver_3/>
<BusCorrelId/>
<Ver_4/>
<WorkflowCorrelId/>
<Ver_5/>
<ValidConsmName>{Insert}</ValidConsmName>
<ValidConsmProd>{Insert}</ValidConsmProd>
<Ver_6/>
</jXchangeHdr>
<Ver_1/>
<Ver_2/>
<Ver_3/>
</MsgRqHdr>
<ErrOvrRdInfoArray>
<ErrOvrRd>
<ErrCode/>
<Ver_1/>
</ErrOvrRd>
<ErrOvrRd>
<ErrCode/>
<Ver_1/>
</ErrOvrRd>
</ErrOvrRdInfoArray>
<CustId JHANull="" Rstr="">A000003</CustId>
<EFTCardType JHANull="" Rstr="">Debit</EFTCardType>
<EFTCardAddInfoArray>
<EFTCardAddInfoRec>
<EmbosName JHANull="" Rstr="">Albert</EmbosName>
<SecdEmbosName JHANull="" Rstr=""/>
<Ver_1/>
</EFTCardAddInfoRec>
<EFTCardAddInfoRec>
<EmbosName JHANull="" Rstr=""/>
<SecdEmbosName JHANull="" Rstr=""/>
<Ver_1/>
</EFTCardAddInfoRec>
</EFTCardAddInfoArray>
<EFTCardAcctIdArray>
<EFTCardAcctIdInfo>
<EFTCardAcctId JHANull="" Rstr="">876514</EFTCardAcctId>
<EFTCardAcctType JHANull="" Rstr="">D</EFTCardAcctType>
<EFTCardPrimAcct JHANull="" Rstr="">true</EFTCardPrimAcct>
<Dlt/>
<Ver_1/>
<AliasAcctName JHANull="" Rstr=""/>
<Ver_2/>
</EFTCardAcctIdInfo>
<EFTCardAcctIdInfo>
<EFTCardAcctId JHANull="" Rstr=""/>
<EFTCardAcctType JHANull="" Rstr=""/>
<EFTCardPrimAcct JHANull="" Rstr=""/>
<Dlt/>
<Ver_1/>
<AliasAcctName JHANull="" Rstr=""/>
<Ver_2/>
</EFTCardAcctIdInfo>
</EFTCardAcctIdArray>
<Custom/>
<Ver_1/>
<EFTCardProdCode JHANull="" Rstr="">431123</EFTCardProdCode>
<Ver_2/>
</EFTCardAdd>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
EFTCardAdd-XML-Response
<?xml version="1.0" encoding="UTF-8"?>
<s:Envelope
xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<s:Header>
<ActivityId CorrelationId="6e1b9a92-1587-4e3f-a4b8-4b5b37842d6b"
xmlns="http://schemas.microsoft.com/2004/09/ServiceModel/Diagnostics">117af93f-ea8b-4bb2-8f92-8ae91b100d8b
</ActivityId>
<o:Security s:mustUnderstand="1"
xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<u:Timestamp u:Id="_0">
<u:Created>2017-09-20T16:45:34.057Z</u:Created>
<u:Expires>2017-09-20T16:50:34.057Z</u:Expires>
</u:Timestamp>
</o:Security>
</s:Header>
<s:Body>
<EFTCardAddResponse
xmlns="http://jackhenry.com/jxchange/TPG/2008"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<MsgRsHdr>
<jXchangeHdr>
<JxVer>R2016.2</JxVer>
<AuditUsrId>PA</AuditUsrId>
<AuditWsId>IDG</AuditWsId>
<AuthenUsrId/>
<ConsumerName/>
<ConsumerProd/>
<Ver_1/>
<jXLogTrackingId>987654321</jXLogTrackingId>
<Ver_2/>
<InstRtId>011001276</InstRtId>
<InstEnv>TEST</InstEnv>
<Ver_3/>
<BusCorrelId>101f78f2-bcbe-4fe5-afa9-9fab7b6398f7</BusCorrelId>
<Ver_4/>
<WorkflowCorrelId/>
<Ver_5/>
<ValidConsmName></ValidConsmName>
<ValidConsmProd></ValidConsmProd>
</jXchangeHdr>
<Ver_1/>
</MsgRsHdr>
<EFTCardAddRsArray>
<EFTCardAddRsRec>
<EFTCardNum MaskVal="111222******2656">1112220000002656</EFTCardNum>
<EmbosName>HANNAH CARTER</EmbosName>
<Ver_1/>
</EFTCardAddRsRec>
</EFTCardAddRsArray>
<RsStat>Success</RsStat>
<Ver_1/>
</EFTCardAddResponse>
</s:Body>
</s:Envelope>
FAQ
EFTCardAddFAQ
Q: Is EFTCardAcctId a value that can be generated by the AcctIdGen?
A: You are able to call the EFTCardAdd function without
an account ID. If after the card is generated you want to add an account
ID to the card you would use the EFTCardAcctIdAdd function. If you have an
account ID at the time of the EFTCardAdd and want to link it at the time
of card creation, then you would include the account ID with the
<EFTCardAcctID>
element.
If you are wanting to generate a new account along with a new EFT Card, then you would utilize the AcctIDGen, then use that generated ID to perform AcctAdd, afterwards use that account ID and enter it into the EFTCardAdd function.
Q: When attempting to add a EFT Card to a new customer and account we receive an error that states:
<ErrCode>9036</ErrCode>
<ErrCat>Fault</ErrCat>
<ErrDesc>Address has changed in the last 30 days, cannot issue card</ErrDesc>
<ErrLoc>ATCARDADD</ErrLoc>
Is there a way to get around this so we can create a person, account, and EFTCard all at the same time?
A: It is a part of the Fact Act law that we have to notify if the address has been changed in the last 30 days if a card is being ordered or reordered. Since the error is categorized as a Fault,
<FaultMsgRec>
<ErrCode>9036</ErrCode>
<ErrCat>Fault</ErrCat>
<ErrDesc>Address has changed in the last 30 days, cannot issue card</ErrDesc>
<ErrLoc>ATCARDADD</ErrLoc>
</FaultMsgRec>
it can be overridden by passing the error code into the ErrOvrRdInfoArray of the request:
<ErrOvrRdInfoArray>
<ErrOvrRd>
<ErrCode>9036</ErrCode>
</ErrOvrRd>
</ErrOvrRdInfoArray>
Q: Core Director I have a question about account types, to print a debit Consumer card do you know what account type we should configure on our side?
A: For Core Director the EFTCardAdd service only works with the following account types:
- 10 Demand Deposit
- 20 Savings
- 40 Loan
Q: When attempting to perform an EFTCardAdd operation, I am getting error 9007:No default ISOs are setup for new card requests for the given card type.
A: Retrieve a list of all valid ISO using the ParmValSrch service with ParmName = EFTCardProdCode.
Q: Can you tell us where on the core the
EFTCardPrimAcct
field is mapped?
A: EFTCardPrimAcct
is not mapped to any
certain field on the core side. It is only a True/False field asking the
question as to if this should be made the primary account or not. If you
say 'TRUE' on one of the accounts being passed in it will make that
account the primary account or make it the DDA 1 account on the card on
core. For instance if you add 3 different DDAs:
- 123456 > FALSE
- 456789 > TRUE
- 321654 > FALSE
Account 456789 will be the primary account or on the card on the core side it will be made the 1 position account.
Q: How to handle the
<EFTCardProdCode>
for a new card?
A: Long story short is that when trying to create a new card when one doesn’t exist there are 2 options with the EFTCardProdCode. Pass in the product code you what to use to create that card under. If you do not pass in a product code then each FI will have a default product code set up to use and it will always default to use that one to create the new card.
Q: When a card is mailed what status does it arrive to the customer?
A: It will arrive in the Warm Status which allows
deposits only. You would need to use the
<EFTCardMod>
operation to set the card to Act (active)
status to make the card fully usable.
Q: Is there a service within the EFTCard service where we can setup an pre-numbered ATM Card with a full 16 digits?
A: Unfortunately, the answer is no. EFTCardAdd is all we have to offer and the host does generate that card number. There is nothing that will accept pre-numbered cards outside of just reordering an existing card.