× Discuss about OFS, Temenos Connectors, Various OFS modes, OFS with Versions, OFS performance, Logging, EB.PHANTOM, OFS.SOURCE etc…

Swift Interface

  • krishnakumarkr
  • Topic Author
  • Visitor
  • Visitor
12 years 7 months ago #11070 by krishnakumarkr
Swift Interface was created by krishnakumarkr
Hi all,

I have 2 questions.
- is T24 a true correspondent banking system? I mean when incoming swift messages DO NOT end with the receiving bank, but are to be re-routed to another entity automatically.
- is there a functionality to re-route the incoming messages automatically, based on the fields populated in T24?

no matter how I format the swift messages, the message held up in the FT hold queue.

Thanks
KK

Please Log in or Create an account to join the conversation.

More
12 years 7 months ago #11097 by durai611
Replied by durai611 on topic Re: Swift Interface
Dear KK,

I don't have that much knowledge in autorouting of SWIFT messages.

But I think, this might be helpful for you to get some idea of autorouting in T24. Kindly check the following fields in AGENCY record,

AUTOROUTING
AUTORTE.CCY
AUTORTE.APPL
AUTORTE.BANK
AUTORTE.REGN
AUTORTE.ACCT

Meanwhile if I get some information will keep on update here :-)

Cheers

Please Log in or Create an account to join the conversation.

More
12 years 7 months ago - 12 years 7 months ago #11100 by saahmad
Replied by saahmad on topic Re: Swift Interface
We are using SWIFT's gateway software that actually routes the message through the SWIFT network. At our bank T24 only is used to parse(generate and read) the SWIFT messages according to the SWIFT patch version installed. the generated messages are put in a folder where the gateway software picks and routes accrording.

I am 90% percent sure that T24 does not have any native solution for routing swift msgs. however there may be carriers that could be implemented to achieve this routing functionality
Last edit: 12 years 7 months ago by saahmad.

Please Log in or Create an account to join the conversation.

Time to create page: 0.079 seconds