The Merchant Central has integrations for boarding and reporting on your First Data Omaha portfolio, as well as calculating residuals. See the information below for how to set up each part. 

Boarding

1. Get AccessOne from First Data.
2. Download and complete this form (click here)  and submit it with your request. 
3. Send an email to accessonesupport@firstdata. com  (cc your First Data CSA) with the form attached and request AccessOne API boarding access. 
4. As soon as First Data enables your ISO for API access, you will go to your AccessOne site and navigate to the Board Access Function section.  From there you will locate Boarding API Access in the Omaha section and provide the support team the AccessOne Username along with the Boarding API Password. 
5. Request your grids (MM reports) from your CSA and Request Bank FIID for each sys/prin for Buypass boarding (Grid files must be in .doc, .docx, or .txt format).
   
   1. MM-016: Merchant Authorization Income Rates
   2. MM-138: User Defined Expense Grid
   3. MM-139: User Defined Income Grid
   4. MM-168: Tiered Discount Grids
   5. MM-726: MFC Merchant Grids
   6. MM-733: Pricing Grid Listing Report

Once this is all set up, head over to our Boarding First Data Omaha Retail Accounts With TurboApp article to get started!

Underwriting Status

• Apps submitted using AccessOne boarding API in TurboApp will have their statuses updated in the site.
• Apps submitted elsewhere will not show in the CRM.

Residuals

File used: ISO(number)_(sysprin)_S1ResidualStatementDetailReport-yyyymm file for each Sys/Prin.

1. Send Merchant Central support an Excel spreadsheet with a list of First Data North merchant IDs and approval dates, with any agents' Merchant Central usernames and their residual splits (%) included.
2. We will use this spreadsheet to import your merchants to the site and assign users to them for access and residuals purposes.

Daily Portfolio Reporting With Transactions and Other Daily Info

1. Request FDFG reporting for merchant info, deposits & transactions, memos, retrievals, and chargebacks. Provide the received credentials to Merchant Central support.
2. Provide Merchant Central support with a Business Track login for retrieving monthly merchant statements.

Other Info About Reporting

An AccessOne user login can be used for Pending Transactions and scraping account info (without waiting for FDFG update the next morning). Add the username and password to the AccessOne-type datasource.

If FDFG is not available, then AccessOne Reporting API can be used for similar info and statements. See this page for how to retrieve the credentials: Enable the AccessOne Reporting API Most commonly, a Sub-ISO would use this because they don't have and cannot get FDFG reporting. The main ISO creates a user for the Sub-ISO and then gets credentials (API username and password) for that login. That would get much of the same info as FDFG.

If the ISO is using FDFG, there are not actual credentials. Instead, the primary AccessOne user name (but not the password) is the info Support needs because that is in the filenames and that connects the files to the ISO's site. That and the start date are what should be sent to the developer by Merchant Central support. First Data may also provide this directly to Merchant Central.

More Info: Fiserv First Data FDFG Integration Setup Guide