Table of Contents - APTAStandards.com

Table of Contents - APTAStandards.com Table of Contents - APTAStandards.com

aptastandards.com
from aptastandards.com More from this publisher
29.06.2013 Views

Exhibit 4.3-5 Example Transaction Batch 6847102847615489 S F Muni 1265 Sequence=”23643” TimeStamp=”04/23/04 16:23:06” Type=”Credit” 10.00 Sequence=”1021” PurseAfter=”10.75” 6847102847615489 S F Muni 2102 Sequence=”4343” TimeStamp=”04/23/04 16:27:42” 1.50 Sequence=”1022” PurseAfter=”9.25” < BatchControl> Count=”1” Total=”10.00” Count=”1” Total=”1.50” < NetAmount>8.50CR 4.3.4.2 Card Management Data OFX does not specify card management data. 4.3.4.3 System and Device Data OFX does not specify system and device data. 4.3.4.4 Event Data OFX does not specify event data. 4.3.4.5 Peer to Peer Clearing & Settlement OFX does not specify peer-to-peer clearing and settlement data. 4.3.4.5 Additional Messages Offered Not applicable to OFX. 4.3.5 Data Elements Data elements fall into two main categories in OFX, “Elements” and “Aggregates”. An element is data bounded by a leading start tag and a trailing end tag. An OFX element must contain data and may not contain other elements. This is different than the more generic definition of an element in XML. An aggregate is a collection of elements and/or other aggregates. The enrollment request aggregate can be utilized to transmit Page 36

cardholder related data as in the case of Registration and Personalization messages as proposed by WP4. The structure of the ENROLLRQ aggregate is described in Exhibit 4.3-6. Exhibit 4.3-6 ENROLLQ Description Tag Description Enrollment request Aggregate First Name Middle Name Last Name Address Line 1 Address Line 2 Address Line 3 City State or Province Postal Code 3-letter Country Code Daytime Phone Evening Phone E-mail Actual User ID if known ID Used for tax purposes Mother’s maiden name or other Date of birth Service activation request aggregates are utilized to start, modify, or terminate a service for an account by sending service activation requests. These requests can be utilized to represent CID/card parameter and application update messages in UTFS. The description of the activation request aggregate in OFX is illustrated in Exhibit 4.3-7. Exhibit 4.3-7 Activation Request Aggregate (ACCTRQ) Tag Description Account Service Request Aggregate Service Addition Aggregate Service Change Aggregate Service deletion Aggregate Service to be added/changed/deleted Page 37

cardholder related data as in the case <strong>of</strong> Registration and Personalization messages as<br />

proposed by WP4. The structure <strong>of</strong> the ENROLLRQ aggregate is described in Exhibit<br />

4.3-6.<br />

Exhibit 4.3-6 ENROLLQ Description<br />

Tag Description<br />

<br />

Enrollment request Aggregate<br />

First Name<br />

Middle Name<br />

Last Name<br />

<br />

Address Line 1<br />

<br />

Address Line 2<br />

<br />

Address Line 3<br />

<br />

City<br />

<br />

State or Province<br />

Postal Code<br />

3-letter Country Code<br />

Daytime Phone<br />

Evening Phone<br />

<br />

E-mail<br />

<br />

Actual User ID if known<br />

<br />

ID Used for tax purposes<br />

<br />

Mother’s maiden name or other<br />

<br />

<br />

Date <strong>of</strong> birth<br />

Service activation request aggregates are utilized to start, modify, or terminate a service<br />

for<br />

an account by sending service activation requests. These requests can be utilized to<br />

represent CID/card parameter and application update messages in UTFS. The<br />

description <strong>of</strong> the activation request aggregate in OFX is illustrated in<br />

Exhibit 4.3-7.<br />

Exhibit 4.3-7 Activation Request Aggregate (ACCTRQ)<br />

Tag Description<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

Account Service Request Aggregate<br />

Service Addition Aggregate<br />

Service Change Aggregate<br />

Service deletion Aggregate<br />

Service to be added/changed/deleted<br />

Page 37

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!