Smart Data File Delivery Guidesmartdatasupport.mastercard.com/MPFD_Manual.pdf · the file %YY%...

MasterCard Smart DataFile Delivery Guide

December 2009

Notices

Proprietary Rights The information contained in this document is proprietary andconfidential to MasterCard International Incorporated, one or more of itsaffiliated entities (collectively "MasterCard"), or both.This material may not be duplicated, published, or disclosed, inwhole or in part, without the prior written permission of MasterCard.MasterCard provides the information in this document (or in anytranslated document) to its customers for internal use only, "AS IS," andmakes no representations or warranties of any kind with respect to suchinformation, including, but not limited to, its accuracy or reliability.

Trademarks Trademark notices and symbols used in this document reflect theregistration status of MasterCard trademarks in the United States. Pleaseconsult with the Customer Operations Services team or the MasterCardLaw Department for registration status of particular product, program, orservice names outside the United States.All third-party product and service names are trademarks or registeredtrademarks of their respective owners.

InformationAvailable Online

MasterCard provides details about the standards used for thisdocument—including times expressed, language use, excerpted text,and contact information—on the Member Publications Support pageavailable on MasterCard OnLine®. Go to Member Publications Supportfor centralized information.

Translation A translation of any MasterCard manual, bulletin, release, or otherMasterCard document into a language other than English is intendedsolely as a convenience to MasterCard customers. In no event shallMasterCard be liable for any damages resulting from a customer’s relianceon any translated document. The English version of any MasterCarddocument will take precedence over any translated version in any legalproceeding.

Publication Code MPFD

©2003–2009 MasterCardDecember 2009 • MasterCard Smart Data File Delivery Guide

Table of Contents

Chapter 1 Overview ........................................................................................ 1-iAbout File Delivery.................................................................................................................. 1-1

Data Privacy............................................................................................................................. 1-1

Enrolling in File Delivery......................................................................................................... 1-2

File Delivery Billing ................................................................................................................. 1-2

File Delivery Reference Information ........................................................................................ 1-3

Chapter 2 Technical Information .................................................................... 2-iFile Delivery Server.................................................................................................................. 2-1

Public Key Encryption ............................................................................................................. 2-1

File Naming Conventions......................................................................................................... 2-1

File Formats ............................................................................................................................. 2-3

Data Types............................................................................................................................... 2-4

Date Types............................................................................................................................... 2-4

Effective Date .................................................................................................................... 2-5

Posting Date ...................................................................................................................... 2-5

Billing Date........................................................................................................................ 2-6

File Frequency ......................................................................................................................... 2-7

Chapter 3 Forms .............................................................................................. 3-iAbout the File Delivery Setup Request Form........................................................................... 3-1

Submitting a File Delivery Setup Request for a Hosted Provider............................................. 3-1

Submitting a File Delivery Setup Request for a Non-Hosted Provider ..................................... 3-3

Chapter 4 Data Field Type Masking ............................................................... 4-iAbout Data Field Masking ....................................................................................................... 4-1

Field Type Masking Reference................................................................................................. 4-1

4000 Corporate Information............................................................................................... 4-2

4300 Account Information ................................................................................................. 4-2

4310 Fleet Account Header................................................................................................ 4-3

4320 Account Status........................................................................................................... 4-3

4410 Hierarchy Address ..................................................................................................... 4-3

4420 Portfolio .................................................................................................................... 4-4

4430 Authorization Limits .................................................................................................. 4-4

4440 Custom Hierarchy...................................................................................................... 4-4

©2003–2009 MasterCardMasterCard Smart Data File Delivery Guide • December 2009 i

Table of Contents

4450 Daily Portfolio ........................................................................................................... 4-4

4460 Account Usage .......................................................................................................... 4-4

4500 Fleet Driver ............................................................................................................... 4-5

4520 Fleet Driver/Vehicle................................................................................................... 4-5

5000 Financial Transactions ............................................................................................... 4-5

5001 Card Acceptor ........................................................................................................... 4-6

5010 Corporate Card Line Item Detail ............................................................................... 4-6

5020 Corporate Card Line Item Detail ............................................................................... 4-6

5021 Passenger Transport Detail Trip Leg Data ................................................................. 4-6

5022 Passenger Rail Transport Detail................................................................................. 4-7

5025 Travel Agency ........................................................................................................... 4-7

5030 Lodging Summary Addendum................................................................................... 4-7

5040 Vehicle Rental Detail Addendum............................................................................... 4-7

5050 Generic Addendum................................................................................................... 4-8

5060 Fleet Card Addendum ............................................................................................... 4-8

5070 Medical Services Detail Addendum........................................................................... 4-8

5080 Temporary Services Detail Addendum...................................................................... 4-8

5090 Shipping/Courier Service Detail Addendum.............................................................. 4-9

5100 Global Invoice........................................................................................................... 4-9

5110 Party Detail Addendum............................................................................................. 4-9

5120 Telephony Billing Summary Addendum ................................................................. 4-10

5121 Telephony Billing Detail.......................................................................................... 4-10

5300 Tax Addendum........................................................................................................ 4-10

5310 Custom Financial Addendum .................................................................................. 4-11

5900 Financial Adjustment Record................................................................................... 4-11

©2003–2009 MasterCard

ii December 2009 • MasterCard Smart Data File Delivery Guide

Chapter 1 OverviewThis chapter includes the basics of file delivery including a description, enrollment process,general billing details, and contact information.

About File Delivery........................................................................................................................ 1-1

Data Privacy................................................................................................................................... 1-1

Enrolling in File Delivery ............................................................................................................... 1-2

File Delivery Billing ....................................................................................................................... 1-2

File Delivery Reference Information .............................................................................................. 1-3

©2003–2009 MasterCardMasterCard Smart Data File Delivery Guide • December 2009 1-i

OverviewData Privacy

About File Delivery

MasterCard collects extensive reporting information related to commercial cardtransactions. File delivery refers to the way in which this transaction informationis made available to commercial customers outside the use of Smart Dataproducts. For example, direct data integration from the Global Data Repository(GDR) into an expense management system or an Enterprise Resource Planning(ERP) system. Corporate Purchasing and Travel and Expense (T&E) customersare examples of the type of customers that could benefit from file delivery.

The following file transfer mechanisms are available:

• File Transfer Protocol (FTP) push with public key encryption.

• Secure Copy (SCP), part of the Secure Shell (SSH) software suite.

• Secure FTP (SFTP), FTP over SSH

• FTP Secure (FTPS), FTP over Secure Socket Layer (SSL)

• Hypertext Transfer Protocol Secure (HTTPS)

• Connect:Direct

• Interpel

NOTE

File encryption is optional for all mechanisms listed except FTP. In addition, theissuer must be sending the company's data to the GDR before the data canthen be sent to the customer.

MasterCard can generate files that contain information about a company'shierarchy, or reporting structure, as well as financial information. The defaultlayout for these files is the Common Data Format (CDF) file layout; however,there are other formats available. To review a list of file formats available, referto the File Delivery Request Setup Form located on the Global CommercialProducts Information Center under Product Forms.

Data Privacy

If a customer requires the ability to automate a customer-initiated pull of data,MasterCard Information Security policy may require additional information. Inaddition, commercial or open source software may be required in order tocomply with MasterCard security requirements for the chosen delivery methodresulting in costs incurred by the customer.

NOTE

MasterCard reserves the right to require additional security measures such asdata file public key encryption regardless of the delivery mechanism or methodchosen.

©2003–2009 MasterCardMasterCard Smart Data File Delivery Guide • December 2009 1-1

OverviewFile Delivery Billing

Data that is not sent to a MasterCard-approved hosted solution providermust be sent to either the issuer or directly to the owner of the specificallyrequested data. Any attempt to send data to a third-party other than aMasterCard-approved hosted solution provider shall be considered a violationof the intended usage of this request process. If, at the discretion of MasterCardsupport personnel, such a request is submitted and suspected to be in violation,the requester will be notified as such and will be given further informationabout what options are available.

Enrolling in File Delivery

These steps outline the high-level process for receiving company data filesfrom MasterCard.

1. Ensure that the participating site can support one or more of the file transfermechanisms offered.

2. Card issuers should complete and submit the Smart Data File Delivery SetUp Request Form. The form is located in the Product Forms section of theGlobal Commercial Products Information Center.

NOTE

The steps that remain in this process are determined by the selections made onthe Smart Data File Delivery Set Up Request Form.

3. The Smart Data Help Desk reviews the information submitted on the formand engages the appropriate group at MasterCard to begin implementationof the file delivery request.

For customer-initiated pulling of data from MasterCard, additional onlineregistration or product requests may apply. Also, MasterCard InformationSecurity policy may require additional information if a customer requires theability to automate a customer-initiated pull of data. Commercial or opensource software may be required as well for information security compliance.Costs may be incurred.

File Delivery Billing

There are different types of billing fees incurred by issuers that participatein MasterCard file delivery services.

Following are the general fees that are associated with file delivery:

• A fee for each file delivery set up.

• A monthly maintenance fee for each file delivery endpoint.

• A per-record processing fee, each time it is delivered.


1-2 December 2009 • MasterCard Smart Data File Delivery Guide

OverviewFile Delivery Reference Information

These fees are billed to the issuer's Interbank Card Association (ICA) numberthrough the MasterCard Consolidated Billing System (MCBS) on the third Sundayof each month. The bill is for one month of data in arrears. Billing details areavailable through MasterCard eService available at MasterCard OnLine®. Formore information, contact [email protected].

File Delivery Reference Information

The following information is provided as a reference for implementation of filedelivery. This section includes information such as required forms, applicableguides, contact information and more.

Guides, Forms and Other Information

Following is a list of sources that provide information about file delivery.

Information Source Where to Find It

CDF File Layouts Global Commercial Products InformationCenter, under CDF/Documentation

Smart Data File Delivery Setup RequestForm

Global Commercial Products InformationCenter, under Product Forms

Contacts

Following are contacts associated with file delivery.

Whom to Contact Contact Options

Smart Data Help Desk In the U.S., phone:800-288-3381 (24/5)

Outside the U.S., phone:636-722-6636 (24/5)

Fax:636-722-7994

E-mail:[email protected]


mailto:[email protected]

mailto:[email protected]

Chapter 2 Technical InformationThis chapter describes technical information about file delivery such as servers, dataencryption, file formats, naming conventions, and more.

File Delivery Server........................................................................................................................ 2-1

Public Key Encryption ................................................................................................................... 2-1

File Naming Conventions............................................................................................................... 2-1

File Formats ................................................................................................................................... 2-3

Data Types..................................................................................................................................... 2-4

Date Types..................................................................................................................................... 2-4

Effective Date........................................................................................................................... 2-5

Posting Date ............................................................................................................................ 2-5

Billing Date.............................................................................................................................. 2-6

File Frequency ............................................................................................................................... 2-7


Technical InformationFile Naming Conventions

File Delivery Server

The end user's server must be configured to grant access to MasterCard. Itis strongly recommended that end users restrict access to their server to theMasterCard domain range: 12.22.155.224–12.22.155.254. MasterCard reservesthe right to modify this domain range.

The IP address or DNS server name must be a publicly routable Internetaddress. Please notify MasterCard at least one month in advance if the IPaddress or DNS server name is going to change.

Public Key Encryption

Since company data files contain sensitive information including financialtransactions, a robust encryption package is recommended on both ends of theInternet file transfer. MasterCard supports public key encryption for this securitypurpose. File encryption is optional for all protocols supported except FTP.

If file encryption is chosen or required, files are encrypted using a publickey provided to MasterCard by the end user. The file can only be decryptedby the end user having the private key associated to the public key that wasused to encrypt the file. MasterCard also signs the files with the MasterCardfile push private key. Doing so allows the end user to validate the source ofthe encrypted file by verifying the signature on the file. Signature validation ismade possible by importing the MasterCard file push public key onto the enduser key ring. The MasterCard file push public key is available upon request.

File Naming Conventions

Following are file naming conventions for files that will be transmitted fromMasterCard.

Standard File Names

The standard naming convention for files distributed by MasterCard isas follows: <DISTRIBUTIONID>_YYYYMMDD_hhmmssXX_<sequencenumber>.cdf.pgp

The following table describes elements in the MasterCard file namingconvention.


Technical InformationFile Naming Conventions

File Element Description

<DISTRIBUTIONID> The ID automatically assigned to adistribution when it is created in theGDR.

YYYY Year

MM Month

DD Day

hh Hour

mm Minute

ss Second

XX Data Type:

• SB—financial and hierarchy (address)data

• SF—financial data

• SH—hierarchy (address) data

<sequence number> Sequential number assigned to filesin format 000001. Allows the user toprocess the files in the correct order.

RSB9999A_20090128_163758SB_000001.cdf.pgpRSB9999A_20090129_143251SB_000002.cdf.pgp

Custom File Names

A custom file name can be chosen instead of using the standard file name.The remote file name MasterCard sends will always end with the .pgpextension—unless an alternate encryption extension has been implemented asa custom development request. Therefore, the name that you specify for yourcustom file name will be appended with .pgp. For example, myfilename.txt asa custom file name will become myfilename.txt.pgp.

NOTE

Special characters are not permitted in custom file names—only numbers,letters, and the underscore character. The percent symbol will be interpreted asa variable placeholder.



Technical InformationFile Formats

Custom file names can include both static and date/time elements if the filesbeing delivered are generated from the MasterCard GDR system. This doesnot apply to files being delivered as a result of an export or report run insmartdata.gen2 or Smart Data OnLine.

The following table describes elements in the custom file naming convention.

File Element Description

%YYYY% Four-digit year based on creation time ofthe file

%YY% Two-digit year based on creation time ofthe file

%DD% Two-digit day of month based oncreation time of the file

%MM% Two-digit month of year based oncreation time of the file

%HH% Two-digit hour timestamp (24 hourclock) based on creation time of the file

%MI% Two-digit minute time stamp based oncreation time of the file

%SS% Two-digit second time stamp based oncreation time of the file

%SEQ% Six-digit (with leading zeroes) filesequence number based on the ordinalnumber of the file generated for aparticular distribution ID

File Formats

Since company data can be shipped in multiple file formats, please consultyour card issuer or MasterCard to find out which file format will be transmittedto your company. To review a list of file formats available, refer to the FileDelivery Setup Request Form located on the Global Commercial ProductsInformation Center. If a file format you wish to receive is not listed on thisform, please contact your issuer to request a custom file format.

NOTE

If you request a custom file format that requires a new format to be created,development fees may be applicable.


Technical InformationDate Types

Data Types

When requesting data, you can specify a Data Type, which determines whatCDF record types you wish to receive in the data files. Company, OrganizationPoint, and Cardholder details are collectively referred to as "Hierarchy." In CDFterminology, these record types are those that begin with 4, for example, 4000,4100 and 4300. Financial transactions and their associated addendum recordsare referred to as Transactions with Addenda. In CDF terminology, these recordtypes are those that begin with 5, for example, 5000, 5001 and 5100.

NOTE

For custom file formats, the record types in the file may be preset per the filespecification and may supersede the Data Type chosen in the File Delivery SetupRequest form.

The following Data Type options are available.

Data Type Description

Hierarchy andTransactions with Addenda

Files will include any new or updated company, accountor organization point detail records (4000, 4100, 4300)and financial transaction and adjustment records (5000,5900). Also will include, if available, any addendumrecords associated with those financial transactions.

Transactions with Addenda Files will include financial transaction and adjustmentrecords (5000, 5900). Also will include, if available,any addendum records associated with those financialtransactions.

Transactions Only—NoAddenda

Files will include financial transaction and adjustmentrecords (5000, 5900), but none of the associatedaddendum records.

Hierarchy Refresh File Files will include the latest detail record available foreach account and organization point, as well as thecompany detail record.

TIP

If you are not certain which Data Type is applicable, select Hierarchy andTransactions with Addenda.

Date Types

There are three Date Types that are used in conjunction with file shipmentoptions such as the frequency of the shipment. The following paragraphsdescribe the Date Types available.



Technical InformationPosting Date

Effective Date

Effective Date is the default Date Type for file distributions from the GDR.The Effective Date is defined for a given record as the date and time that therecord was loaded within the GDR. Effective Date file distribution logic willresult in data records included that have an effective date and time of onesecond greater than the effective date THROUGH date time of the previousfile generated and sent.

Posting Date

Posting Date distribution logic goes to the GDR database and finds recordsloaded within the previous 90 days of the file distribution send date and thenapplies a filter to eliminate records that fall outside the beginning and endingposting date range for the current file being created.

In this example, a file is being distributed monthly with a Posting Date of day15 of each month. Three "offset days" should be added so the file generationprocess will wait three days, allowing time for data at the end of the postingdate range to arrive and load into the GDR.

The Effective Date range for initial data extraction in the GDR would be day15 of the previous month at 23:59 time (then minus 90 days) through day 19of the current month and time (then plus 90 days).

That initial file would then be filtered to eliminate data with posting datesoutside the range of day 16 of the previous month and day 15 of the currentmonth. The file for customer delivery would contain data with the posting datesbetween day 16 of the previous month and day 15 of the current month.


Technical InformationBilling Date

Billing Date

The purpose of the Billing Date as a data type is to create a file distribution tocapture all transaction, adjustment and enhanced data records with a billingdate within a given month.

Because distributions are compiled based on Effective Date (the date recordsare created in the GDR) within a monthly block, it is necessary to specify alarger date range to pull additional financial data. Depending upon the BillingCycle end date, however, each distribution may require a slightly different daterange to ensure all relevant transaction data is captured.

The Billing Date selection combined with a monthly frequency will providedistribution files on a monthly schedule that pulls financial data for overlapping90-day periods; the GDR then filters the records for a billing date based on themonth in which the distribution runs.

NOTE

The following fields must be sent by the processor in the correct format toensure that all relevant data is included in the distribution or recreate files:Transactions—BillingDate on the 5000 record and Adjustments—ProcessingDateon the 5900 record

Standard monthly distributions will pull financials with an Effective Date (theday the financial record was created in the GDR) within that monthly range.

Because a billing date for a given monthly cycle end date occurs in the future,it is possible for financials to come in over the course of two or three months,for example, financials with a July billing month could come into the GDR inMay, June or July. As a result, the distribution must look on either side of themonthly block to ensure all required financials are included.

The billing date filter will look for any record containing a billing date monththat matches the month in which the distribution runs. Therefore, it is necessaryto add an offset to the monthly cycle end date to ensure that the file is notgenerated until the month containing the billing date for that cycle.

For example, a company's billing cycle end date is day 21 of each month andthe billing date is day 15 of the next month. In this scenario, the distributionoptions should be set up as follows:

• Frequency Code—Monthly

• Month Day—21

• Data Type—Financial Transactions

• Date Type—Billing

• Offset Days—11

NOTE

The “offset days” number must be added to the distribution end date to ensurethat the file is not generated until the month following the cycle date.



Technical InformationFile Frequency

In this example, the distribution is now scheduled to run for June 21. It wouldinclude all financial data with an effective date from April 22 through July 21.The following image further illustrates this example.

The offset will cause the file to wait to run until July 2. The GDR will look atthe July run date and will filter the data in the distribution to include only thosefinancial records with a July billing date. If the offset was not included and thedistribution ran in June, the billing date filtered on would be June, not July.

File Frequency

MasterCard supports a variety of options for shipment frequency of data filesgenerated by the GDR.

NOTE

This information does not apply to files delivered via FTP or Secure Copy asexports or reports generated from smartdata.gen2 or Smart Data OnLine.

The following table describes the frequency options that are available.

Frequency Description

On Receipt MasterCard will distribute a file based on the loadingof new data records for your company into the GDR.MasterCard processes files Monday–Saturday. However,depending on the schedule of the processor file sent onbehalf of your company's card issuer, there may not be anynew records for your company loaded on a given day, sothere may be days when no new file is sent to you. Thisoption is useful if you only wish to receive a file when datais available. It eliminates the receipt of empty files.

Fixed MasterCard will distribute a file at either 1:30 PM or 4:00PM CST Monday–Saturday. This option generates a fileregardless of whether any data has arrived since the lastfile was sent. Therefore, a file could be empty or onlycontain a CDF header and trailer record and no other data.This option is useful when scheduled, automated processesat the company site require a file to be present.


Technical InformationFile Frequency

Frequency Description

Monthly MasterCard will distribute a file on a monthly basis on theday after the specified day of the month. This distributionuses the date you choose as the "through date" and the fileis sent the day after the selected date. This file includesdata loaded between the end date of the last file sentthrough the chosen monthly date. This option could resultin an empty file if there is no new data for your companyavailable since the last monthly file was sent. For example,if this field is set to day 15, the files will be sent the morningof the day 16. This file includes data from day 16 of theprevious month through day 15 of the current month.

Weekly MasterCard will distribute files on a weekly basis on the dayafter the specified day of the week. This distribution usesthe weekday you choose as the "through date" and files aresent the day after the date chosen. This file includes dataloaded between the end date of the last file sent throughthe chosen weekday. This option could result in an emptyfile if there is no new data for your company availablesince the last weekly file was sent. For example, if this fieldis set to Wednesday, the file will be sent Thursday morning.This file includes data from the previous Thursday throughWednesday of the current week.



Chapter 3 FormsThis chapter provides information about submitting a File Delivery Setup Request form andthe accompanying field definitions.

About the File Delivery Setup Request Form................................................................................. 3-1

Submitting a File Delivery Setup Request for a Hosted Provider................................................... 3-1

Submitting a File Delivery Setup Request for a Non-Hosted Provider ........................................... 3-3


FormsSubmitting a File Delivery Setup Request for a Hosted Provider

About the File Delivery Setup Request Form

The File Delivery Setup Request Form is an online form where users cansubmit to MasterCard a request for electronic file deliveries out of the GDR.The form is located on the Global Commercial Products Information Centerunder Product Forms.

Submitting a File Delivery Setup Request for a HostedProvider

These are the instructions for submitting a File Delivery Setup Request fora Hosted Solution Provider. A Hosted Solution Provider is one with whichMasterCard has a business relationship and tested, established security measuresin place.

1. Enter the following information for the issuer requesting file delivery setup.

a. Requestor Name, E-mail Address and Phone Number—informationabout the contact person at the issuer that is sponsoring this request.

b. Requestor Bank Name and Requestor Bank ICA Number—Name ofthe issuer sponsoring this request and its Interbank Card Association(ICA) number.

c. ICA to be Billed for transmissions—ICA number of the bank that willbe billed for the file transmissions.

2. Select Yes to confirm that the data is already being sent to the GDR andmove on to step 3.

NOTE

If you select No, the process will halt and the following message will appear:

Click OK to close the message. Contact the Smart Data Help Desk [email protected] for information about sending data to the GDR.

3. Select the Entity Type of the data to be distributed.

The following Entity Types are available.


FormsSubmitting a File Delivery Setup Request for a Hosted Provider

Option Description

Company Group A virtual entity created for the purpose ofgenerating a consolidated file with transactionand/or hierarchy data from multiple companies.The group's members may be from a single bankor multiple banks.

If selected, you will be prompted to enter theCompany Group Name as registered in MasterCardGDR.If the company group does not exist, a link to theCompany Group Setup form appears. The formprovides information about company groups andis used for requesting setup of a company group.

Company A specific company name. If selected, you will beprompted to enter the following:

a. Company Name as registered in MasterCardGDR

b. Company Number as registered in MasterCardGDR

c. Bank Number associated with the Companyabove

d. ICA associated to the Bank Number above

Orgpoint An organization point within the specifiedcompany. If selected, in addition to entering thecompany information noted previously, you willbe prompted to enter the following:

a. Orgpoint Name within in the company above

b. Orgpoint Number within the company above

4. Select Yes, this is a hosted solution provider approved by MasterCard. If thisanswer is No, new boxes will appear and you will be required to follow adifferent process. For more information about the non-hosted process, referto Submitting a File Delivery Setup for a Non-Hosted Provider.

5. Select the Hosted Solution Provider Name from the drop-down list. Theprovider selected determines which file formats will be available in step 6.

6. Select the File Format from the drop-down list and click Next. TheComments box appears.

NOTE

The file formats available are those MasterCard has successfully used withthe selected Hosted Solution Provider.

7. In the Comments box, enter any helpful comments, plus the desiredoutcome of this request. For example, if this file distribution is similar toone already setup, provide the details in this box. Any information of thistype can help expedite the file delivery setup process.

8. Click Submit.



FormsSubmitting a File Delivery Setup Request for a Non-Hosted Provider

An e-mail confirmation will be sent to the requestor’s e-mail address. Thee-mail contains all of the information the requestor submitted in the form.

Submitting a File Delivery Setup Request for a Non-HostedProvider

The following instructions explain how to submit a file delivery setup requestfor a non-hosted solution provider.

1. Enter the following information for the issuer requesting file delivery setup.

a. Requestor Name, E-mail Address and Phone Number—informationabout the contact person at the issuer that is sponsoring this request.

b. Requestor Bank Name and Requestor Bank ICA Number—Name ofthe issuer sponsoring this request and its Interbank Card Association(ICA) number.

c. ICA to be Billed for transmissions—ICA number of the bank that willbe billed for the file transmissions.

2. Select Yes to confirm that the data is already being sent to the GDR andmove on to step 3.

NOTE

If you select No, the process will halt and the following message will appear:

Click OK to close the message. Contact the Smart Data Help Desk [email protected] for information about sending data to the GDR.

3. Select the Entity Type of the data to be distributed.

The following Entity Types are available.

Option Description

Company Group A virtual entity created for the purpose ofgenerating a consolidated file with transactionand/or hierarchy data from multiple companies.The group's members may be from a single bankor multiple banks.

If selected, you will be prompted to enter theCompany Group Name as registered in MasterCardGDR.If the company group does not exist, a link to theCompany Group Setup form appears. The form



Option Descriptionprovides information about company groups andis used for requesting setup of a company group.

Company The specific company name. If selected, you willbe prompted to enter the following:

a. Company Name as registered in MasterCardGDR

b. Company Number as registered in MasterCardGDR

c. Bank Number associated with the Companyabove

d. ICA associated to the Bank Number above

Orgpoint An organization point within the specifiedcompany. If selected, in addition to entering thecompany information noted previously, you willbe prompted to enter the following:

a. Orgpoint Name within in the company above

b. Orgpoint Number within the company above

4. Select No, this is not a hosted solution provider approved by MasterCard.If this answer is Yes you need to follow a different process. For completehosted provider instructions, refer to Submitting a File Delivery SetupRequest for a Hosted Provider.

NOTE

Data that is not sent to a MasterCard-approved hosted solution providermust be sent only to either the card-issuing bank, OR , DIRECTLY TO THEOWNER of the specifically requested data. Any attempt to send data to athird-party other than a MasterCard-approved hosted solution provider shallbe considered a violation of the intended usage of this request process. If, atthe discretion of MasterCard support personnel, such a request is submittedand suspected to be in violation, the requester will be notified as such andwill be given further information about what options are available.

5. Select the Non-Hosted Expense Application from the drop-down list. Theapplication selected will determine the file format selections available instep 6.

6. Select the File Format from the drop-down list and click Next.

NOTE

The file formats available are those MasterCard has already successfully usedwith the selected Non-Hosted Expense Application.

7. Enter details about the file delivery. The following options are available.




Option Description

Requested File Frequency These selections determine when and at whatintervals the files will be distributed. The followingoptions are available:

• On Receipt triggered by inbounddata—distributes the file as soon as thefiles are loaded into the system from theprocessor.

• 6 files a week Monday-Saturday at 1:00AMCST, 1:30PM CST or 4:00PM CST.

• Weekly—distributes files on a weekly basis onthe day after the specified day of the week.

• Monthly—distributes files on a monthly basison the day after the specified day of the month.

• Custom Billing Cycle—Distributes files basedon the dates specified. If selected, provideSmart Data Help Desk with a spreadsheetcontaining “Through” dates (for 12 months)on which the file should be distributed. Thisis used in conjunction with Posting Date,Effective Date, or Billing Date. For moreinformation, refer to About Custom BillingCycle File Shipments.

• Day of Week Through—Indicates the“Through” day of the week that files aredistributed. For example, if this field is setto Wednesday, the file will be sent Thursdaymorning.

• Day of Month Through—Indicates the“Through” day of the month that files aredistributed. For example, if this field is set to15, the files will be sent the morning of the16th.

• Offset Days—Specifies the number of days towait for before the file is sent to help ensure allof the data is sent for the time period selected.Offset Days is used with Monthly or Weeklyfile distributions. For example, monthly witha Day of Month Through of 20 and an OffsetDays of 2 means that the file would containdata from the 21st of the previous monththrough the 20th of the current month and thefile will be sent on the third business day afterthe 20th. This is most often used with a Postingor Billing Date Type to allow for latency.

CDF Data Record Types The types of records to include in the distribution.The following options are available:



Option Description

• Active Hierarchy—All active hierarchy data.Includes all accounts and any organizationpoints with the status code value of Active.

• Address Maintenance—All new or updatedhierarchy data processed within the specifieddate range for the file being generated.

• All Hierarchy with Inactive Hierarchy—Allactive hierarchy and inactive hierarchy data.

• Financial including Addendum and AddressData—All financial data including addendumand address data.

• Financial Transactions includingAddendum—All financial data includingaddendum.

• Financial with No Addendum—All financialdata with no addendum.

• Financial with No Addenda, No AddressData—All financial data with no addenda oraddress data.

• Load Only Enhanced Data—All Enhanced Datathat has not been matched to a transaction.

Date Type for TransactionSelection

The transaction date type for the distribution.

• Effective Date—The date the transaction wasloaded into the GDR.

• Posting Date—The date the transaction wasposted to the account–provided by the issuer.

• Billing Date—The date that indicates the billingperiod for the transaction–optional, providedby the issuer.

Data Records Type forTransaction Selection

The records that will delivered in the distribution.

• All Transactions—Include all transaction typesin the file distribution.

• T&E Transactions Only—Include travel andentertainment transactions only.

• PCard Transactions Only—Include purchasingcard transactions only.

• Hotel Transactions Only—Include hoteltransactions only.

• Merchant Transactions Only—Includemerchant transactions only. This excludesadjustments.




Option Description

Receive Again TransactionsUpdated AFTER AlreadySent Out

This applies to transactions that may be appendedwith Enhanced Data after the original transactionwas sent. If Yes, you will again receive transactionswith appended data.

Receive ONLY Transactionswith Enhanced DataMatched by MasterCard

Select Yes if only matched transactions are to besent—no unmatched transactions.

Allow records withnon-numeric accountnumbers

This allows for the receiving of account numberscontaining characters other than numeric.Sometimes used with private label cards. Allowsup to 19 alphanumeric characters.

Must the line terminators beformatted for Windows OS

Select Yes if the computer receiving the files isrunning on the Microsoft Windows platform.

Optional Filter by CustomID Type—if provided intransaction by issuer

If requested, only transactions with these specificvalues (no wildcards) will be delivered. These arecontained in the private data subelement (PDS)502. For example, following is a partial list ofexpected values:

• FOLNUM—Folio Number

• TRANID—Transaction Identification

• PRCHID—Purchase Identification

• RESNUM—Reservation Number

• RNTAGR—Rental Agreement

• SUPINV—Supplier Invoice

• SUPORD—Supplier Order

• TKTNUM—Ticket Number

• TRKNUM—Tracking Number

• RECLOC—Record Locator

• CUSORD—Customer Order

• CUSTPO—Customer Purchase Order

For the most current information, refer to the IPMClearing Formats guide available on the MemberPublications page on MasterCard OnLine. This canbe used with Optional Filter by Custom ID Valueto further refine the transaction data received.

Optional Filter by CustomID Value—if provided intransaction by issuer

If requested, only transactions with these specificvalues (no wildcards) will be delivered. This canbe used with Optional Filter by Custom ID type tofurther refine the transaction data received. Thisoption is available only if the issuer is sendingthese value types.



8. As an option, you can restrict data to only receive records related to theMasterCard Product Codes that you select.

a. In the Available MasterCard Product Code Filter Values column on theleft, highlight the desired product codes. Use the right and left arrowsto move selections to and from the Filter to receive records related toONLY those in the MasterCard Product Codes chosen column.

b. Click Next.

NOTE

You will only receive records containing the product codes that youselected, or moved to the right column. Use the left arrows to moveselections back to the left column. If you choose not to put any productcodes in the right column, the file delivery will contain records for allavailable product codes.

9. As an option, you can request PCI Field Masking for outbound CDF3 XMLfile formats with version XML 6.1 or later.

Field Masking Rule

Account Number This will replace Account Number positions 7–12,character for character, with the letter X.

Account Name This will replace the field value, character forcharacter, with the letter X.

Address Data This will replace the field value, character forcharacter, with the letter X.

Employee Data This will replace the field value, character forcharacter, with the letter X.

Date of Birth This will make the field null.

Phone Data This will replace the field value, character forcharacter, with the letter X.

E-mail Address This will replace the field value, character forcharacter, with the letter X.

For information about masking, refer to About Data Field Masking.

10. Indicate whether the file transfers will be a MasterCard Initiated Push or aCustomer Initiated Pull by clicking the applicable button.

For a MasterCard Initiated Push, the following options become available.




Option Description

File Push Protocol File push options are available in the followingmechanisms or protocols.

• SFTP (Secure Shell) with secure User ID andPassword

• SCP (Secure Shell) with secure User ID andPassword

• FTP with SSL (FTP/s)

• FTP with User ID and Password (PGP fileencryption required)

• ConnectDirect

• Interpel

• XCOM

• HTTPS–No Custom Header

PGP File Encryption To request file encryption. This will default to Yesif the File Push Protocol is FTP.

• Yes—File encryption requested

• No—File encryption not requested

Custom File Name The file name to be used for the file distributionin lieu of the standard file name. For moreinformation, refer to File Naming Conventions inchapter two.

NOTE

Special characters are not permitted in customfile names—only numbers, letters, and theunderscore character. The percent symbol willbe interpreted as a variable placeholder.

MasterCard-assignedendpoint number if thecustomer already has oneassigned

The existing endpoint number for the customer.

ExistingMasterCard-assigned GDRdistribution ID that may besending files to this sameintended customer location

Any existing GDR distribution ID that may besending files to the same intended customerlocation.

Describe existing filedistributions fromMasterCard that couldbe a pattern for this newrequest

Any existing file distributions to use as a patternfor this request.

For a Customer-Initiated Pull, the following options become available.



Option Description

Data Pull Automated orUser-Initiated

Indicates whether the data pull should be anautomatic pull or a manual pull by the technicaluser.

Provide MasterCard OnLineUser ID intended forauthentication withMasterCard to pullthe requested files viaMasterCard File ExpressClient or MasterCard DataExchange service

The technical user's existing MasterCard OnLineUser ID.

MasterCard-assignedendpoint number if thecustomer already has oneassigned

The existing endpoint number for the customer.

ExistingMasterCard-assigned GDRdistribution ID that may besending files to this sameintended customer location

Any existing GDR distribution ID that may besending files to the same intended customerlocation.

Existing file distributionsfrom MasterCard to use asa pattern for this request

Any existing file distributions to use as a patternfor this request.

Technical Contact Name The user at the site that will be logging in to pullthe data.

Technical Contact E-mailAddress

The e-mail address for the technical contact.

Technical Contact PhoneNumber

The phone number for the technical contact.

11. Click Next after making the file transfer selections.

12. In the Comments box, enter any helpful comments, plus the desiredoutcome of this request and click Submit.

An e-mail confirmation will be sent to the requestor’s e-mail address. Thee-mail contains all of the information the requestor submitted in the form.



Chapter 4 Data Field Type MaskingThis chapter describes the specific masking method used for the applicable fields in eachrecord type. It includes masking for each position in the fields that can be masked perrecord number.

About Data Field Masking ............................................................................................................. 4-1

Field Type Masking Reference....................................................................................................... 4-1

4000 Corporate Information..................................................................................................... 4-2

4300 Account Information ....................................................................................................... 4-2

4310 Fleet Account Header...................................................................................................... 4-3

4320 Account Status................................................................................................................. 4-3

4410 Hierarchy Address ........................................................................................................... 4-3

4420 Portfolio .......................................................................................................................... 4-4

4430 Authorization Limits ........................................................................................................ 4-4

4440 Custom Hierarchy............................................................................................................ 4-4

4450 Daily Portfolio ................................................................................................................. 4-4

4460 Account Usage ................................................................................................................ 4-4

4500 Fleet Driver ..................................................................................................................... 4-5

4520 Fleet Driver/Vehicle......................................................................................................... 4-5

5000 Financial Transactions ..................................................................................................... 4-5

5001 Card Acceptor ................................................................................................................. 4-6

5010 Corporate Card Line Item Detail ..................................................................................... 4-6

5020 Corporate Card Line Item Detail ..................................................................................... 4-6

5021 Passenger Transport Detail Trip Leg Data ....................................................................... 4-6

5022 Passenger Rail Transport Detail....................................................................................... 4-7

5025 Travel Agency ................................................................................................................. 4-7

5030 Lodging Summary Addendum......................................................................................... 4-7

5040 Vehicle Rental Detail Addendum..................................................................................... 4-7

5050 Generic Addendum ......................................................................................................... 4-8

5060 Fleet Card Addendum ..................................................................................................... 4-8

5070 Medical Services Detail Addendum................................................................................. 4-8

5080 Temporary Services Detail Addendum ............................................................................ 4-8

5090 Shipping/Courier Service Detail Addendum.................................................................... 4-9

5100 Global Invoice................................................................................................................. 4-9

5110 Party Detail Addendum................................................................................................... 4-9

5120 Telephony Billing Summary Addendum ....................................................................... 4-10

5121 Telephony Billing Detail................................................................................................ 4-10


Data Field Type Masking

5300 Tax Addendum.............................................................................................................. 4-10

5310 Custom Financial Addendum ........................................................................................ 4-11

5900 Financial Adjustment Record......................................................................................... 4-11


4-ii December 2009 • MasterCard Smart Data File Delivery Guide


Field Type Masking Reference

About Data Field Masking

To facilitate compliance with data privacy policies, some distribution data fieldtypes can be masked in outbound CDF3 XML file formats with version XML6.1 or later.

Field types available for masking include:

• Account Name

• Account Number

• Address Data

• Employee Data

• Date of Birth (DOB)

• Phone Data

• E-mail Address

For example, if the Account Number field type is masked, all instances ofaccount numbers in the records are masked. This means positions 7–12 of the16-digit account number are masked, for example, 501234XXXXXX1234. Theway in which the data is masked is not a configurable option.

NOTE

Account Number masking is not available for smartdata.gen2 or Smart DataOnLine distributions.

Field Type Masking Reference

The following table describes the masking rules for each field type that can bemasked. Refer to this table when looking at the Masking Rules column in thetables for each record number.

Field Masking Rule

Account Number This will replace Account Number positions 7–12,character for character, with the letter X.

Account Name This will replace the field value, character for character,with the letter X.

Address Data This will replace the field value, character for character,with the letter X.

Employee Data This will replace the field value, character for character,with the letter X.

Date of Birth This will make the field null.

Phone Data This will replace the field value, character for character,with the letter X.

E-mail Address This will replace the field value, character for character,with the letter X.



4300 Account Information

4000 Corporate Information

The following table describes the masking details for applicable fields in the4000 record.

FieldNo.

Field Name StartPosition

EndPosition

Length FieldType

Masking Rule Used

15 Processing CorporateAccount

138 156 19 A Account Number

4300 Account Information


FieldNo.


EndPosition

Length FieldType

Masking Rule Used

5 Account Number 64 19 19 A Account Number

22 Alternate AccountNumber 1






28 Transfer From Account 251 269 19 A Account Number

29 Transfer To Account 270 288 19 A Account Number

35 Date of Birth 327 336 10 D Date of Birth

37 Employee ID 339 358 20 A Employee Data

38 EIN Nine Digit 359 367 9 A Account Number

40 Name Line 1 371 420 50 A Account Name

41 Name Line 2 421 470 50 A Account Name

43 Alternate Name Line 1 474 523 50 A Account Name

44 Alternate Name Line 2 524 573 50 A Account Name

47 DDA Number 650 666 17 A Account Number

48 Transit Routing Number 667 675 9 N Account Number

61 First Name 841 875 35 A Account Name

62 Last Name 876 910 35 A Account Name

63 Middle Name 911 945 35 A Account Name

64 Suffix Name 946 980 35 A Account Name




4410 Hierarchy Address

4310 Fleet Account Header


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


14 Vehicle/Driver Name 118 167 50 A Account Name

4320 Account Status


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


4410 Hierarchy Address


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


19 Address Number 182 183 2 N Address Data

20 Address Line 1 184 233 50 A Address Data




24 City 384 403 20 A Address Data

25 State/Province 404 406 3 A Address Data

26 Country Code 407 409 3 A Address Data

27 Postal Code 410 422 13 A Address Data

28 Contact Name 423 472 50 A Account Name

29 Phone Number 473 497 25 A Phone Data

30 Fax Number 498 522 25 A Phone Data

31 E-mail Address 523 582 60 A E-mail Address


Data Field Type Masking4460 Account Usage

4420 Portfolio


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


4430 Authorization Limits


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


4440 Custom Hierarchy


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


4450 Daily Portfolio


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


4460 Account Usage


FieldNo.


EndPosition

Length FieldType

Masking Rule Used





5000 Financial Transactions

4500 Fleet Driver


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


14 Driver Number 118 134 17 A Employee Data

15 Driver Name 135 184 50 A Account Name

18 Drivers License IDNumber

196 212 17 A Employee Data

19 Issue State 213 215 3 A Address Data

20 Issue Country 216 218 3 A Address Data

4520 Fleet Driver/Vehicle


FieldNo.


EndPosition

Length FieldType

Masking Rule Used

14 Vehicle/Driver Number 118 134 17 A Employee Data

18 Vehicle / Driver Numbers1 - 45


5000 Financial Transactions


FieldNo.


EndPosition

Length FieldType

Masking Rule Used










5021 Passenger Transport Detail Trip Leg Data

5001 Card Acceptor


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


5010 Corporate Card Line Item Detail


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


5020 Corporate Card Line Item Detail


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


16 Passenger Name 172 221 50 A Account Name

5021 Passenger Transport Detail Trip Leg Data


FieldNo.


EndPosition

Length FieldType

Masking Rule Used





5040 Vehicle Rental Detail Addendum

5022 Passenger Rail Transport Detail


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


6 Passenger Name 551 600 50 A Account Name

5025 Travel Agency


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


5030 Lodging Summary Addendum


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


142 Guest Name 953 1002 50 A Account Name

5040 Vehicle Rental Detail Addendum


FieldNo.


EndPosition

Length FieldType

Masking Rule Used




5080 Temporary Services Detail Addendum

5050 Generic Addendum


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


5060 Fleet Card Addendum


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


30 Driver or ID Number 265 281 17 A Employee Data

5070 Medical Services Detail Addendum


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


5080 Temporary Services Detail Addendum


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


16 Employee/TempName/ID


17 EIN or ID 212 241 30 A Account Number




5110 Party Detail Addendum

5090 Shipping/Courier Service Detail Addendum


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


5100 Global Invoice


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


5110 Party Detail Addendum


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


18 Name 1 200 249 50 A Account Name



21 Street 1 350 399 50 A Address Data






27 City 650 669 20 A Address Data

28 State/Province 670 672 3 A Address Data

29 Postal Code 673 685 13 A Address Data

30 Country Code 686 688 3 A Address Data

31 Contact Name 689 738 50 A Account Name

33 Phone Number 789 813 25 A Phone Data



5300 Tax Addendum

FieldNo.


EndPosition

Length FieldType

Masking Rule Used

34 E-mail Address 814 873 60 A E-mail Address

5120 Telephony Billing Summary Addendum


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


16 User Name 172 211 40 A Account Name

17 User Account Number 212 230 19 A Employee Data

5121 Telephony Billing Detail


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


25 Call From City 252 271 20 A Address Data

26 Call From State/Province 272 274 3 A Address Data

27 Call From Country Code 275 277 3 A Address Data

28 Call From Phone Number 278 302 25 A Phone Data

5300 Tax Addendum


FieldNo.


EndPosition

Length FieldType

Masking Rule Used





5900 Financial Adjustment Record

5310 Custom Financial Addendum


FieldNo.


EndPosition

Length FieldType

Masking Rule Used


5900 Financial Adjustment Record


FieldNo.


EndPosition

Length FieldType

Masking Rule Used




18 Alternate AccountNumber 1 Type




20 Alternate AccountNumber 2 Type





Smart Data File Delivery Guidesmartdatasupport.mastercard.com/MPFD_Manual.pdf · the file %YY%...

Documents

Transcript of Smart Data File Delivery Guidesmartdatasupport.mastercard.com/MPFD_Manual.pdf · the file %YY%...