100 likes | 224 Vues
Learn about the benefits of using XML for financial messaging, including standardized data, reduced maintenance costs, and improved business opportunities. This document covers syntax, semantics, and industry adoption, offering insights on XML's role in bank operations, customer interactions, and product semantics. Discover how XML is used in e-check processing, customer and product semantics, and proposed projects for leveraging XML in the financial industry.
E N D
XML for Financial Messaging David White Wells Fargo djwhite@wellsfargo.com Milton M. Anderson FSTC miltonma@gte.net November 4, 1998 Page1
Why XML? • Language for describing syntax of text messages/documents • Independent of presentation • Independent of semantics • Is supported by major standards bodies • Is being widely adopted by the industry Page2
Bank ExtraNets Retail Customers Mortgage Company The Bank Commercial Customers Brokerage House Mutual Funds Wholesalers Page3
Echeck - SGML <amount>9.95 <currency>USD OFX 1.5 - SGML <TRNAMT>9.95 IFX 1.0 - XML <TRNCURAMT> <CURCODE>USD</CURCODE> <AMT>9.95</AMT> </TRNCURAMT> OTP 0.9 - XML <PayAmount Amount=“9.95” CurrCodeType=“ISO4217” CurrCode=“USD”/> BIPS - XML <amount encryption= key-id= encoding= ccy=“USD” >9.95</amount> What Happens Naturally? Page4
Customer Semantics • Personal information • Name • Address • Contact information • Relationship details • Householding • Other • Transactions • Credit information Page5
Product Semantics • Banking • Brokerage • Insurance • Mortgage • Mutual funds • Retirement plans Page6
Proposed Project • Establish participation and a working group • Establish contact with relevant standards bodies • Establish namespace and modeling approach • Define core customer message elements • Define a process for ongoing maintenance of semantics Page7
Proposed Project • Choose a product space for definition • Define message elements for the product • Define the message set • Produce a pilot implementation • Evaluate pilot and proceed, as appropriate Page8
Project Participation • Banks interested in supplier or commercial customer interfaces • Suppliers of mortgages, insurance, and other products • Software vendors/integrators • XML community Page9
Conclusion • XML can result in better interfaces with suppliers and large customers • Standardization of data and transaction semantics can reduce maintenance costs and enhance business opportunities • An FSTC project on Financial XML can facilitate standardization and demonstrate benefits in pilot implementations Page10