Developer Resources
For this API to function in an Financial Institution’s (FI) environment(s), the FI must be a subscriber to the Jack Henry Card Processing Service (CPS). If CPS is not configured in the FI’s environment, this API will return an error message stating there is not a message configured or access is denied.
Please discuss with your partner FI before using in their environment(s).
Details
| SoapAction | http://jackhenry.com/ws/EFTCardAcctIdAdd |
| Input Name | EFTCardAcctIdAdd |
| Output Name | EFTCardAcctIdAddResponse |
| Input Namespace | http://jackhenry.com/jxchange/TPG/2008 |
| Group Name | Customer |
| Container | TPG_CustomerMaster.xsd |
XML Examples
EFTCardAcctIdAdd Request
<?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>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<EFTCardAcctIdAdd
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>
<EFTCardNum JHANull="" MaskVal="" Rstr="" SrchType="">1112220000002847</EFTCardNum>
<EFTCardSufxNum JHANull="" Rstr="">0</EFTCardSufxNum>
<EFTCardAcctIdArray>
<EFTCardAcctIdInfo>
<EFTCardAcctId JHANull="" Rstr="">143453</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/>
</EFTCardAcctIdAdd>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
EFTCardAcctIdAdd FAQ
Should I use EFTCardAcctIdAdd to add an account to an EFTCard?
Use EFTCardAcctIdAdd when you only need to add a non‑funding DDA account to an existing EFTCard. It is the simplest and most direct method for that scenario.
If you need to add a new DDA account that will become the primary funding account, you must use EFTCardMod instead. This is required because the existing funding account must first be updated to Funding = “N” before the new account can be added with Funding = “Y”.
Attempting to add a new funding account using EFTCardAcctIdAdd when a primary funding account already exists will result in an error and the request will be rejected.
- Have a how-to question? Seeing a weird error? Get help on StackOverflow.
- Register for the Developer Office Hours where we answer technical Q&A from the audience.