Developer Resources
Details
SoapAction | http://jackhenry.com/ws/IntlWireTrnAdd |
Input Name | IntlWireTrnAdd |
Output Name | IntlWireTrnAddResponse |
Input Namespace | http://jackhenry.com/jxchange/TPG/2008 |
Group Name | Transaction |
Container | TPG_TransactionMaster.xsd |
XML Examples
IntlWireTrnAddXML
<?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>
<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>2018-05-17T16:32:27Z</wsu:Created>
</wsse:UsernameToken>
</wsse:Security>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<IntlWireTrnAdd
xmlns="http://jackhenry.com/jxchange/TPG/2008">
<MsgRqHdr>
<jXchangeHdr
xmlns="http://jackhenry.com/jxchange/TPG/2008">
<AuditUsrId></AuditUsrId>
<AuditWsId></AuditWsId>
<ConsumerName></ConsumerName>
<ConsumerProd></ConsumerProd>
<Ver_1/>
<jXLogTrackingId>{Insert}</jXLogTrackingId>
<Ver_2/>
<InstRtId>011001276</InstRtId>
<InstEnv>TEST</InstEnv>
<Ver_3/>
<BusCorrelId></BusCorrelId>
<Ver_4/>
<Ver_5/>
<ValidConsmName>{Insert}</ValidConsmName>
<ValidConsmProd>{Insert}</ValidConsmProd>
</jXchangeHdr>
</MsgRqHdr>
<WireCorrelId>53501</WireCorrelId>
<WireAcctId>867675</WireAcctId>
<WireAcctType>D</WireAcctType>
<WireIntlCustInfoRec>
<CustType/>
<CustId>867675</CustId>
<WireCustInfo>
<PersonName>
<ComName>Bob Tester</ComName>
<FirstName>Bob</FirstName>
<LastName>Tester</LastName>
</PersonName>
<Addr>
<StreetAddr1>123 Payer Street</StreetAddr1>
<StreetAddr2>Apt 100</StreetAddr2>
<City>Austin</City>
<StateCode>TX</StateCode>
<PostalCode>78681</PostalCode>
</Addr>
</WireCustInfo>
<TaxId/>
</WireIntlCustInfoRec>
<WireIntlTrnInfoRec>
<WireSrc>Intnet</WireSrc>
<WireAmt>10.00</WireAmt>
<CurrType>USD</CurrType>
<Cntry>MX</Cntry>
<WireIntlBenfInfoRec>
<WireBenfId>12345678</WireBenfId>
<WireBenfName>Joe Recipient</WireBenfName>
<WireBenfAddr>
<StreetAddr1>123 Receipient Street</StreetAddr1>
<StreetAddr2>Suite 300</StreetAddr2>
<Cntry>MX</Cntry>
<Ver_1/>
<StreetAddr3>Suite 300</StreetAddr3>
</WireBenfAddr>
<WireBenfFinInstAddr>
<StreetAddr1>123 Recipient FI Street</StreetAddr1>
<StreetAddr2>Suite 100</StreetAddr2>
<Cntry>MX</Cntry>
<Ver_1/>
<StreetAddr3>Suite 100</StreetAddr3>
</WireBenfFinInstAddr>
<PayeeFinInstRtId>BDEMMXMF</PayeeFinInstRtId>
<WireIntmdBankId>BDEMMXMF</WireIntmdBankId>
<IntmdFinInstStreetAddr1>123 Intermediary FI Street</IntmdFinInstStreetAddr1>
<IntmdFinInstStreetAddr2>Suite 200</IntmdFinInstStreetAddr2>
<IntmdFinInstCity>Mexico City, Mexico</IntmdFinInstCity>
<IntmdFinInstCntryType>MX</IntmdFinInstCntryType>
</WireIntlBenfInfoRec>
<WireOrignToBenfInfoRec>
<WireOrignToBenfRmkArray>
<RmkInfo>
<Rmk>This is some info between Orig and Benf</Rmk>
<Ver_1/>
</RmkInfo>
</WireOrignToBenfRmkArray>
</WireOrignToBenfInfoRec>
</WireIntlTrnInfoRec>
<WireUsrId/>
<AvlBalCalcCode>2</AvlBalCalcCode>
</IntlWireTrnAdd>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
FAQ
IntlWireTrnAddFAQhtml
IntlWireTrnAdd Questions
Q: What are the fields that SilverLake fills in, without the user entering any values for the IntlWireTrnAdd?
A: They are:
XML Path | Reference Field |
---|---|
blank | bkcntrefid = all 0 |
FundMthdType | wxtproduct = Q |
WireIntlQuoteRec.CurrPmtType | wxtentdcfl = If wxtqamtfgn = wxtqamtusd then L else F |
WireIntlQuoteRec.FeeCurrType | wxtamxfcid = USD |
WireIntlCustInfoRec.CustType | wxtrmtdcls = N |
WireIntlCustInfoRec.WireCustInfo.Addr.CntryType | wxtorgcncd = US |
WireIntlTrnInfoRec.WireSrc | wxtpltform=N |
Q: When using release 2020 we are getting a slew of validation errors. What are the rules when we have the following?
<WireCorrelId>6977</WireCorrelId>
<FundMthdType>OutgoingWire</FundMthdType>
A: When FundMthdType is sent in the request as ‘OutgoingWire’:
- If WireCorrelId is not null and not zero, then return error code 101060
- If WireContrRefId is not null and not blank, then return error code 101060
When WireQuoteId is null or zero:
- If WireIntlQuoteRec.WireTrnTimeDt is not null and not blank, then return error code 101060
- If WireIntlTrnInfoRec.CurrType = ‘USD’ and WireIntlQuoteRec.FornCurrAmt not null and not zero, then return error 101061
- If WireIntlQuoteRec.CurrExchRate is not null and not zero, then return error 101061
- If WireIntlQuoteRec.SttlCostAmt is not null and not zero, then return error 101061
- If WireIntlQuoteRec.SttlNetCostAmt is not null and not zero, then return error 101061
Once US dollar wire functionality was added to IntlWireTrnAdd in R2020, there is a new FundMthdType of ‘OutgoingWire’. Outgoing wires and Intraday contracts are handled very differently on the AMEX side and the required elements are different between the two types. When creating an OutgoingWire, the contract elements are not required WireCorrelId and WireContrRefId, and cannot be sent to AMEX with values in them, or core will receive an error from AMEX.
When you sent in the request with a
Note: This core column for the WireCorrelId element is a 22 position alphanumeric field.
Q: Are there any requirements to use the IntlWireTrnAdd service?
A: Yes, IntlWireTrnAdd can only be used for DLI (DirectLine International) and American Express customers.