Download presentation
Presentation is loading. Please wait.
Published byKelly Stevens Modified over 6 years ago
1
To build a new merchant record, click on the Add icon
2
CMS Merchant Wizard window will appear
CMS Merchant Wizard window will appear. Select the appropriate profile from the drop down menu. The number in the Description is the sys/prin plus a check digit
3
Select the Vendor ID and Product for the terminal, software or gateway the merchant will be using
4
Required fields in Merchant tab:
DBA, Phone#, Address, City, State, Postal Code (the merchant descriptor that goes out to interchange will be drawn from these fields) Merchant Data – always MER000 If merchant will be set up with a retail MCC but will be processing MOTO, the Direct Marketing flag must be checked CS Phone is required for MOTO merchants and must be entered if it is different from the regular Phone# Address is required for YourPay setups
6
Select terminal application by clicking on Add Future
If applicable, select Pin Pad, Check Reader, Proximity Reader Select terminal application by clicking on Add Future
7
Select terminal application from list (in this case there is only one choice)
8
Information on the application will auto-populate
11
Enter info for all card types the merchant will accept
Enter info for all card types the merchant will accept. For MC/Visa, use Omaha MID and enter MCC
12
Once all card types have been entered, click on arrows to add each card type for this terminal
13
As each card type is selected, choose the Price Plan appropriate for the product the merchant is using
14
Price Plan will vary by product, but as a general rule:
Dial/IPN and YourPay = B Micros = M All other internet gateways = Y This will cover virtually every situation There are also online edits in CMS that will prevent you from entering the wrong Price Plan
15
When all entry is complete, click Save icon
Displays primary and secondary auth/settle numbers the terminal will be programmed to use. In this tab you can add prefixes if needed, such as a 9 to get an outside line. When all entry is complete, click Save icon
16
Main CMS Screen To pull up an existing merchant, you can fill in one or more of the fields above. For example, you can enter the Omaha MID (or the Amex Discover, etc merchant number) in Processor Merch #, or enter the Nashville MID, TID or DBA, etc.
17
Example: Enter Omaha MID and hit Enter
19
Icons in CMS Pend Record – Allows user to temporarily save account builds or changes if an error message is received when trying to perform a normal save. Merchant/Terminal History – Changes to the account are displayed in reverse chronological order. See example below. Displays before and after values for the field changed, along with the CMS user ID, name of the user who made the change, and time/date of the change.
20
Set date range and click on Search
Viewing Batch Information – allows you to view batch and transaction level detail. Batch totals for previous 30 days can be viewed online, and transaction detail from the past 14 days. Set date range and click on Search
21
The six most recent batches will display, including open batches as in this example. To see additional batches click on More Batches. Dates and times displayed are for when the first transaction was added to the batch. To see the details of a batch, double click on the batch
22
The first six transactions in the batch are displayed
The first six transactions in the batch are displayed. To display more transactions click on More Transactions. The Closed Date and time, along with totals for sales and counts, are also displayed. To see further detail, such as AVS response, E-Commerce Indicator, Purchase Card Data, etc., click on the drop menu next to Available Aux Data. The menu will show the categories of detail available for the selected transaction. In this example, there is data available for AVS and Card Code Validation. To view the detail, select an item and click on View Aux Data. AVS example on following page.
23
In this case, the address did not match or was not provided, but the ZIP Code was a match, resulting in an AVS response of Z.
24
Incident Reporting – log of calls to the Nashville POS Help Desk
25
Voice auth information – displays voice auth numbers for all card types
26
Auth-Only Information – Displays auth-only transactions
Auth-Only Information – Displays auth-only transactions. Functions very much like the batch information window. Select a date range and click on Search.
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.