FAQ
Q: Is there any event generated when a transfer is updated? That is, is there an equivalent to the Customer/Account Modification events in EES?
A: No, event 840 is close, but it only triggers when ACH transactions created.
Q: If an ACH transfer results in a return or Notifications of Change (NOC) response from the Fed or ACH processing system is there any notification/event sent to notify subscribers of the NOC?
A: Event 910 will trigger on a NOC if they are submitted by 3rd parties through the ACHFileAdd operation.
Q: Why does event 20030 have a mask with just the last four digits instead of the first six and last four or the token?
A: When translated, JHA is only given the last four so it is a direct translation.
Q: Can EESEventInfoArray contain events from multiple institutions?
A: Yes
Q: Can an EventDataInfoArray contain events for more than one entity/user for a particular institution?
A: Yes
Q: Could we see an event response example?
A: Before looking at an example response, it’s important to know the following:
- The content type response should be: Content-Type: text/xml; charset=utf-8
- The Security.TimeStamp.Created and Security.TimeStamp.Expires elements should follow UTC time and be set five minutes apart with Created time being the moment you receive the request
- The fields within the JESHdr should echo the fields sent within the JESHdr section of the EESEventAdd request
<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>2021-03-24T15:54:50.058Z</u:Created>
<u:Expires>2021-03-24T15:59:50.058Z</u:Expires>
</u:Timestamp>
</o:Security>
</s:Header>
<s:Body>
<EESEventAddResponse xmlns="http://jackhenry.com/jxchange/JES/2008">
<JESMsgRsHdr>
<JESHdr>
<AuditUsrId></AuditUsrId>
<AuditWsId></AuditWsId>
<ConsumerProd></ConsumerProd>
<ConsumerRqDtTime>2020-10-26T18:13:51.0000000</ConsumerRqDtTime>
<jXLogTrackingId>122222222</jXLogTrackingId>
<OrigConsumerInfo/>
<ValidConsmName>{Insert}</ValidConsmName>
<ValidConsmProd>{Insert}</ValidConsmProd>
</JESHdr>
</JESMsgRsHdr>
<RsStat>Success</RsStat>
</EESEventAddResponse>
</s:Body>
</s:Envelope>
Q: What would an event request look like on a push subscription?
A: Note this is using BasicHttpsBinding with TransportWithMessageSecurity. I.E. WS-UserNameTokenxml:
<Addressing>
<Action>http://jackhenry.com/ws/EESEventAdd</Action>
<To>https://YourCompanyEESListener.test/EESService/basicHttps</To>
</Addressing>
<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="7cdd69a0-768d-4ac4-908c-950906406339" xmlns="http://schemas.microsoft.com/2004/09/ServiceModel/Diagnostics">00000000-0000-0000-0000-000000000000</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>2024-03-01T22:58:54.344Z</u:Created>
<u:Expires>2024-03-01T23:03:54.344Z</u:Expires>
</u:Timestamp>
<o:UsernameToken u:Id="uuid-0ab1c984-02c7-4647-abcb-1b255511b327-118">
<o:Username>
<!-- Removed-->
</o:Username>
<o:Password>
<!-- Removed-->
</o:Password>
</o:UsernameToken>
</o:Security>
</s:Header>
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<EESEventAdd xmlns="http://jackhenry.com/jxchange/JES/2008">
<JESMsgRqHdr>
<JESHdr>
<AuditWsId>EESFarmName</AuditWsId>
<ConsumerProd>Enterprise Event</ConsumerProd>
<ConsumerRqDtTime>2024-03-01T16:58:54.3293923-06:00</ConsumerRqDtTime>
<jXLogTrackingId>7eb7e483-5c76-4c8f-9a26-610a258abff4</jXLogTrackingId>
</JESHdr>
</JESMsgRqHdr>
<SubscrpId>YourSubscriptionID</SubscrpId>
<EESEventInfoArray>
<EESEventInfo>
<EventNum>660</EventNum>
<EventProd>Silverlake</EventProd>
<EventTimeDt>2024-02-28T05:02:10</EventTimeDt>
<InstId>011001276</InstId>
<ProdEnv>TEST</ProdEnv>
<SystemId>Silverlake-Instance</SystemId>
<EventUsrId>SILVERLAKE-CUSTOMER</EventUsrId>
<EventWsId>WS1234</EventWsId>
<BusCorrelId>422383</BusCorrelId>
<EventAppId>CF</EventAppId>
<EventProcId>R3RUNJHA/CFCUSTADD</EventProcId>
<EventThreadId>0</EventThreadId>
<EventDataInfoArray>
<EventDataInfo>
<Name>ItemName</Name>
<Val>Customer ID</Val>
</EventDataInfo>
<EventDataInfo>
<Name>UserId</Name>
<Val>SILVERLAKE-CUSTOMER</Val>
</EventDataInfo>
<EventDataInfo>
<Name>Value</Name>
</EventDataInfo>
<EventDataInfo>
<Name>Action</Name>
<Val>Create</Val>
</EventDataInfo>
<EventDataInfo>
<Name>CustId</Name>
<Val>HAA3947</Val>
</EventDataInfo>
</EventDataInfoArray>
<EventUniqueId>6632ac58-2602-4427-a77b-064b3adc7a79</EventUniqueId>
<EESIdHistInfoArray>
<EESIdHistInfo>
<EESHistId>011001276-PROD-jxdmz.jackhenry.com</EESHistId>
</EESIdHistInfo>
</EESIdHistInfoArray>
<Custom/>
</EESEventInfo>
</EESEventInfoArray>
</EESEventAdd>
</s:Body>
</s:Envelope>
Q: We’ve received messages from the EES system and see this attribute listed in the Security header: s:mustUnderstand=“1”. What does that attribute represent?
A: Setting the mustUnderstand attribute to “1” in Windows Communication Foundation (WCF) forces the message receiver to process the data contained in the header element. In this instance, that would be the timestamp and username/password used to authenticate the connection. That attribute will appear in all messages sent from EES.
Q: What SOAP action so we need to use for our EES listener? Can we pick one and have you update it on your end?
A: The SOAP action from EES will always need to be set to http://jackhenry.com/ws/EESEventAdd. That is the only value that EES supports.
Q: Do you support self-signed certificates for EES listener endpoints?
A: No, we only support certs that are signed by a publicly trusted Certification Authority.