Developer Resources
Details
SoapAction | http://jackhenry.com/ws/EFTCardSrch |
Input Name | EFTCardSrch |
Output Name | EFTCardSrchResponse |
Input Namespace | http://jackhenry.com/jxchange/TPG/2008 |
Group Name | Customer |
Container | TPG_CustomerMaster.xsd |
Operation Summary
OperationSummary-EFTCardSrch
Operation Summary
The EFTCardSrch operation provides the ability to search for EFT cards. The request must contain at least one of the following search filters:
EFTCardSrch Element | Description |
ComName | The common name. This is the full name like John Doe. |
CustId | The identifier attached to a customer. |
AccountId | A complex element containing the incoming account identification information. The simple elements within this complex are: AcctId (Account Id) AcctType (Account Type) |
EFTCardNum | The debit card number. |
TaxId | The tax identification number. |
The EFTCardSrch response will contain an EFTCardSrchArray of results that match the search criteria in the request. Each record in the array will have an EFTCardNum element with the EFT card number. If no match is found, an array will not be returned and the response will contain a warning with an ErrCode value of 49 and ErrDesc of No Records Match Selection Criteria .
The EFT card status, EFTCardStat, and status description, EFTCardStatDesc, elements are returned for each card listed in the response.
The complete PassPort Card Status list is as follows:
Card Status | Description | Card Status | Description |
A | Active | O | Order new card |
C | Closed | P | PIN Mailer |
D | Deleted Card | R | Re-order card |
E | Expired | S | Securomatic deposits only |
H | Hot Card | W | Warm card - Deposits only |
I | In process card order | X | PIN retries exceeded |
L | Limits | Z | Do not reorder |
M | Manually Activate |
The EFTCardInq operation can then be called to retrieve additional information for an invididual card. The request must include the EFTCardNum element representing the card number of the EFT card to inquire upon.
Special Considerations
The EFTCardNum, TaxId, and ComName elements each contain a SrchType attribute that support the canonical values Exact, StartsWith, EndsWith, and Contains. This optional attributes conveys to the provider how each filter should be applied to the search expression.
XML Examples
EFTCardSrchXMLRs
<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>
<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>2020-08-26T17:46:39.987Z</u:Created>
<u:Expires>2020-08-26T17:51:39.987Z</u:Expires>
</u:Timestamp>
</o:Security>
</s:Header>
<s:Body>
<EFTCardSrchResponse
xmlns="http://jackhenry.com/jxchange/TPG/2008"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SrchMsgRsHdr>
<jXchangeHdr>
<JxVer>R2017.4</JxVer>
<AuditUsrId></AuditUsrId>
<AuditWsId></AuditWsId>
<AuthenUsrId></AuthenUsrId>
<ConsumerName></ConsumerName>
<ConsumerProd></ConsumerProd>
<Ver_1></Ver_1>
<jXLogTrackingId>122222222</jXLogTrackingId>
<Ver_2></Ver_2>
<InstRtId>011001276</InstRtId>
<InstEnv>TEST</InstEnv>
<Ver_3></Ver_3>
<BusCorrelId>df6256a2-4c69-4cbc-a1c9-08319ea5c02f</BusCorrelId>
<Ver_4></Ver_4>
<WorkflowCorrelId></WorkflowCorrelId>
<Ver_5></Ver_5>
<ValidConsmName></ValidConsmName>
<ValidConsmProd></ValidConsmProd>
</jXchangeHdr>
<SentRec>2</SentRec>
<MoreRec>false</MoreRec>
<Cursor>0</Cursor>
<TotRec>2</TotRec>
<Ver_1></Ver_1>
</SrchMsgRsHdr>
<CustId></CustId>
<AccountId>
<AcctId>99959</AcctId>
<AcctType>D</AcctType>
<Ver_1></Ver_1>
</AccountId>
<EFTCardNum></EFTCardNum>
<TaxId></TaxId>
<ComName></ComName>
<EFTCardSrchArray>
<EFTCardSrchRec>
<EFTCardNum MaskVal="431123******7860">4311230036277860</EFTCardNum>
<CustId>SAA0001</CustId>
<TaxId MaskVal="455-47-8758">455478758</TaxId>
<EmbosName>TESTING</EmbosName>
<EFTCardStat>A</EFTCardStat>
<EFTCardStatDesc>Active</EFTCardStatDesc>
<LastActDt>2011-08-15</LastActDt>
<Ver_1></Ver_1>
<EFTCardStatType>Act</EFTCardStatType>
<Ver_2></Ver_2>
</EFTCardSrchRec>
<EFTCardSrchRec>
<EFTCardNum MaskVal="431123******6067">4311230365136067</EFTCardNum>
<CustId>B000052</CustId>
<TaxId MaskVal="552-23-3655">552233655</TaxId>
<EmbosName>GAYLENE BROWN</EmbosName>
<EFTCardStat>A</EFTCardStat>
<EFTCardStatDesc>Active</EFTCardStatDesc>
<Ver_1></Ver_1>
<EFTCardStatType>Act</EFTCardStatType>
<Ver_2></Ver_2>
</EFTCardSrchRec>
</EFTCardSrchArray>
<Ver_1></Ver_1>
</EFTCardSrchResponse>
</s:Body>
</s:Envelope>
XML
<?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">2017-09-20T19:33:23Z
</wsu:Created>
</wsse:UsernameToken>
</wsse:Security>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<EFTCardSrch
xmlns="http://jackhenry.com/jxchange/TPG/2008">
<SrchMsgRqHdr>
<jXchangeHdr>
<JxVer/>
<AuditUsrId></AuditUsrId>
<AuditWsId></AuditWsId>
<AuthenUsrId/>
<ConsumerName/>
<ConsumerProd/>
<Ver_1/>
<jXLogTrackingId>{Insert}</jXLogTrackingId>
<Ver_2/>
<InstRtId>011001276</InstRtId>
<InstEnv>TEST</InstEnv>
<Ver_3/>
<BusCorrelId/>
<Ver_4/>
<WorkflowCorrelId/>
<Ver_5/>
<ValidConsmName>{Insert}</ValidConsmName>
<ValidConsmProd>{Insert}</ValidConsmProd>
<Ver_6/>
</jXchangeHdr>
<MaxRec>10</MaxRec>
<Cursor/>
</SrchMsgRqHdr>
<CustId></CustId>
<AccountId Rstr="">
<AcctId SrchType="">99959</AcctId>
<AcctType>D</AcctType>
<Ver_1/>
</AccountId>
<EFTCardNum></EFTCardNum>
<TaxId></TaxId>
<ComName SrchType=""/>
<Custom/>
<SvcPrvdInfo/>
<Ver_1/>
</EFTCardSrch>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
FAQ
EFTCardSrchFAQ
EFTCardSrch Questions
Q: There were two accounts associated to this card number - 1234/ Checking and 1247437 / Checking. However when we did EFTCardSrch on the account number - 1234, the card number returned in the response is different - 1112220000000098. The customer number linked to this account is also different than the customer number we got from EFTCardInq response. Can you please check if this is an expected behavior or test data issue.
A: If you look at the request coming in you can see a MaxRec element which is set to 1 and Cursor which is set to blank.
<ns:MaxRec>1</ns:MaxRec>
<ns:Cursor/>
- The MaxRec element means how many records do you want returned back for your selected criteria. In this case it was 1 so we only passed one card back in the response. If you look at the response from where they sent a request on the account number 1234 we sent back these elements.
<SentRec>1</SentRec>
<MoreRec>true</MoreRec>
<Cursor>2</Cursor>
<TotRec>45</TotRec>
- We sent 1 record, MoreRec is True meaning there are more records, Cursor is now on 2 meaning we have only sent 1 record back and if they request again with this data we will send the next one, and TotRec is 45 meaning there are a total of 45 records that we could send back if requested.
- Long story short if MaxRec was set to 99 or something like that then in this case we would have sent back all 45 cards that were tied to account number 1234. The other option is to request it again passing MaxRec as 1 and Cursor now at 2 which would pass the next card number and he could do that 45 times by passing the next Cursor number from each response.
Q: In the EFTCardInq response, what does EFTCardTrnType and EFTCardTrnLocType signify?
A: EFTCardTrnType and EFTCardTrnLocType are a part of monthly or statement cycle totals. This will list the number of transactions per transaction type that has occurred on that card during that cycle. ATM W/D’s, Deposits, POS purchases, etc… If there are any there will also be a count that would go with each one.
Q: The ComName field returns empty value in EFTCardSrch response. Also, ComName field is not present in the EFTCardInq response unlike in EFTCardSrch. Which field can we use for Customer's name associated to the card in EFTCardInq service?
A: ComName is only used in the Request and will not have a value in the response. If you want the name you will have to use EmbossName in the response for both EFTCardInq and EFTCardSrch.