1-Way ofx and Microsoft Money Microsoft Corporation June 3, 2005 What is 1-Way ofx?

OFX 1.0.1 to 1.0.2

• 
  Revisions to the specification text, organized by chapter
  
• 
  General revisions to the specification text
  
• 
  Changes to the Document Type Definition (DTD) files
  

1. Specification Changes by Chapter

   1. Chapter 1, “Overview”

      Section	Subject	Change Type	Change
      1.2	OFX headers, VERSION	Update	Updated VERSION:101 to VERSION:102 to indicate version 1.0.2 of the DTDs.

   2. Chapter 2, “Structure”

      1. Sections 2 to 2.4.5

Section	Subject	Change Type	Change
2.	Data blocks	Correction	Open Financial Exchange data consists of some headers plus only one Open Financial Exchange data block.
2.1	HTTP headers	Addition	If a communication time-out error occurs while an OFX server and back-end server are communicating to fill a request, then the server MUST return code 500.
2.2, 2.2.3	OFX headers, VERSION	Update	Updated VERSION:101 to VERSION:102 to indicate version 1.0.2 of the DTDs.
2.2.4	Security	Deletion	Reference to Type 2 security has been deleted.
2.4.2	Case sensitivity	Addition	Upper case letters must be used for element names and enumerated values.
2.4.3	Top level	Clarification	A single file must contain only one OFX block.
2.4.5.3	Message Set Version Numbers	Addition	Added section about message set version numbers. This section distinguishes message set version numbers from the version numbers of the OFX headers and the DTD files.
2.4.6	Message sets and version control	Addition	List of status code values for the element of : 0 Success (INFO) 2000 General error (ERROR) 2022 Invalid TAN (ERROR)

1. Sections 2.5.1.1 to 2.5.2.3

   Section	Subject	Change Type	Change
   2.5.1.1		Clarification	The effective size of is A-32. However, if Type 1 security is used, then the actual length is A-171.
   2.5.1.1		Clarification	The client will determine out-of-band whether a FI aggregate should be used and if so, the appropriate values for it. If the FI aggregate is to be used, then the client should send it in every request, and the server should return it in every response.
   2.5.1.2		Clarification	A client should use and only when the service provider that originated is the same provider that is specified by in the profile message set. A client can determine if the service provider is the same by comparing the value of in the appropriate message set with the value for in the profile message set.
   2.5.2.1		Clarification	A change request changes the customer’s password for the specific realm associated with the messages contained in the OFX block.
   2.5.2.1		Clarification	The effective size of is A-32. However, if Type 1 security is used, then the actual field length is A-171.
   2.5.2.3		Addition	Information on the challenge request and challenge response, the first steps in Type 1 security, has been added.
   2.5.2.3		Addition	Status code 15501, Could not provide random data (ERROR), has been added to the list of Status code values for the element of .
   2.5.3		Deletion	Deleted and from .

1. Chapter 3, “Common Aggregates, Elements, & Data Types”

   Section	Subject	Change Type	Change
   3.2.8.2	Date and datetime	Addition	Time zones are specified by an offset and optionally, a time zone name. The offset defines the time zone.

2. Chapter 4, “Open Financial Exchange Security”

5. Chapter 7, “FI Profile”

6. Chapter 8, “Activation & Account Information”

7. Chapter 9, “Customer to FI Communication”

8. Chapter 11, “Banking”

   Section	Subject	Change Type	Change
   11.4.2.3.1		Correction	is of type FITID.
   11.5.4.2		Correction	is of type FITID.
   11.6.1.1	Stop check	Change	type changed from A-255 to A-32.
   11.6.1.1.2	Stop check	Change	type changed from A-255 to A-32.
   11.6.1.1.2.1	Stop check	Change	type changed from A-255 to A-32.
   11.12.5.1	Statement closing download	Change	has been changed to optional.

9. Chapter 12, “Payments”

10. Chapter 13, “Investments”

1. Appendix A

   Subject	Change Type	Change
   Status code, 2021	Addition	The server does not support the requested version.
   Status code, 2022	Addition	The server was unable to validate the TAN sent in the request.
   Status code, 15504	Addition	Could not provide random data

1. General Specification Changes

3. DTD Changes