SFMS Bank Application Interface Specifications Document ... - IDRBT

More documents

Recommendations

Info

SFMS Bank Application Interface specifications Version 3.0 21. M Filler 9 Alpha Numeric 22. M UTR (Unique 16 Alpha Transaction Numeric Reference) sequence number. SFMS API rejects the message if there is no sequence number. Ex: If sequence number is 5 then user should send as ‘000000005’ Filler for future use and default value is XXXXXXXXX. Unique Transaction Reference Generated for RTGS. Host applications should default it to XXXXXXXXXXXXXXXX 23. M Priority Flag 2 Number This Priority flag is used for routing the messages in RTGS messages. For Host applications the default value is 99 24. M Block A End Identifier 25. M Block4 Begin Identifier 26. M Block 4 Alpha Numeric 27. M Block End Identifier for Block 4 28. O Block5A Begin Identifier 29. O Block 5A Alpha Numeric 30. O Block5A End Identifier 1 Char Block End identifier. This should be } 3 Alpha This block4 begin identifier Numeric should be {4: Text block of the message. Length of the message cannot exceed 10 KB. 2 Char Block End identifier should be - } 6 Char It the Bank Application can generate the UMAC then this should be {UMAC: If the Bank Application does not have the capability to prepare the signature, this field can be left blank. Authorizer Signature. This is an optional field, which can be filled by Bank applications with signature prepared in PKCS7 standard on Block4 Information. If the Bank Application does not have the capability to prepare the signature, this field can be left blank. If this field is blank the messages will be forced to be in “PENDING AUTHORIZATION” state in SFMS Offline/Branch Server. 1 Char If the Bank Application can generate the UMAC then this should be } If the Bank Application does not have the capability to prepare the signature, this field can be left blank. Confidential Uncontrolled when Printed Page 9 of 24
SFMS Bank Application Interface specifications Version 3.0 Note: For straight through processing of messages Block 5A is mandatory. An example for the incoming message structure to the SFMS branch server from Bank application is shown below {A: Block A begin Identifier B09 Bank Application Identifier F01 Message Identifier O Input/output Identifier ( either I or O) 100 Message type XXX Sub Message type ( For IFN 298C01, this field should be C01, for IFN100 Message, this field should be XXX) SBIN0001001 Sender IFSC Code SBIN0001002 End receiver IFSC Code 1 Delivery notification flag 1 Open Notification flag 2 Non-delivery Warning flag 005 Obsolescence Period abcdefgh12345678 Message User Reference (MUR) 2 Possible Duplicate flag XXX Service Identifier 20030909 Originating date 1020 Originating time 2 Testing and training flag 000012345 Sequence Number XXXXXXXXXX Filler XXXXXXXXXXXXXXXX Unique Transaction Reference. 99 Priority Flag } Block A end Identifier {4: Block 4 Begin Identifier :20:TT/320 Block 4 text message format :32A:20030909INR100, -} Block 4 End Identifier {UMAC: Block 5A Begin Identifier User Signature for Authorisation } Block 5A End Identifier 3.2 Acknowledgement Message Index Mandato ry / Field Name Field Length Data Type Description Confidential Uncontrolled when Printed Page 10 of 24
Page 1 and 2: Document Number: Copy Number: INSTI
Page 3 and 4: SFMS Bank Application Interface spe
Page 11: SFMS Bank Application Interface spe
Page 27: SFMS Bank Application Interface spe

SFMS Bank Application Interface Specifications Document ... - IDRBT

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?