3rd Party Integration with swiftpos NetPOS and Service Monitor
Refer HERE for Reseller & Support information.
This outlines the information and the steps that are needed to familiarise oneself with the MG (Max Gaming interface.
The content is targeted at Resellers and swiftpos Venue Administrators who have a sound knowledge of and experience with swiftpos. For further information or assistance, please contact your swiftpos Reseller or swiftpos Support.
Subjects ▼
Screens ▲ ▼
NetPOS MG (Max Gaming) Settings Screen ▲ ▼
To access refer to How To Access The NetPOS Menu for more information. A NetPOS Registration for the MG (Max Gaming) interface will be required in order to access this screen. Used to configure the settings required to implement the MG (Max Gaming) interface.
Noteworthy
- Port number - The Port Numbers) for communicating to Max Gaming. This can be multiple ports, comma separated, if also configured on Max Gaming side (v6.60+). For example, 32773,32774,32775
- Timeout - The Timeout in Seconds for communicating with Max Gaming
- Request Cash Balance - request the cash balance from Max Gaming
- Link To - Link to another supported interface.
- Field Mapping - Select the mapping to use with the Link To interface.
Notes ...
If you are using the FBI Interface and you have Match Alternate ID selected in Global Preferences, then you MUST use Member No <-> Member No in the Field Mapping.
Grid Section
Noteworthy
- Pts ID - ALL the Points IDs in use by Max Gaming at the site MUST be configured here.
- Accrue - Select whether this Point Type can accrue
- Multiplier - The multiplier at which the points accrue if accrue box is ticked.
- Can Redeem - This point type can be redeemed.
- Send to Touch - Send this points account to swiftpos Touch
- Base Points - This option will use this multiplier for all members regardless of their Classification multiplier. If it is un-ticked, both multipliers will apply to the Members points accruals.
- Location Point Types - Here you can set up Location specific points multipliers. If there is no Location Point Types configured, the values from the points grid will be used.
Notes ...
Points are set in Back Office against the Category and then there is also a multiplier available in the Location setup if you want a particular location to accrue more or fewer points. Member Classifications in Back Office can also have a multiplier configured. In the Max Gaming example, they also have a multiplier for their Point Types, and they also use the Member Classification multiplier here. The Base Points option will ignore the Member Classification multiplier, and all members will receive the Multiplier set against that Points type regardless of their Classification. Touch can only show the points from the Category and also the Location Multiplier as configured in Back Office. This is because the Member may be accruing points on multiple accounts, each with a different multiplier, so there is no way to show that accurately.
Service Monitor MG (Max Gaming) Screen ▲ ▼
To access refer to How To Access The Service Monitor for more information. Used to configure the settings required for the MG (Max Gaming) interface in Service Monitor.
-
Enable Watching - Select to enable the Service Monitor to watch for activity.
-
Enable Full Debug - Select to enable. This should only be enabled when recommended.
How It Works?
(FBI) The MG (Max Gaming) Option in Services allows you to specify a folder to "watch" for files from The MG (Max Gaming) software via PC-Easy, for the purpose of synchronising SwiftPOS with the MG (Max Gaming) Members. To Use, simply specify a Folder to watch and tick Enable Watching. When a MG (Max Gaming) update is issued to PC-Easy, this feature will read in the file and add/update the Members in SwiftPOS, to be the same as MG (Max Gaming).
To switch on this feature for full integration of MG (Max Gaming) Membership, there is a charge of $1.50 per day from MG (Max Gaming).
When the CSV file and associated Semaphore file are found in the Watch Folder, the services read the MG (Max Gaming) file and imports it into the SwiftPOS database, matching by the Member Number.
If someone loses their current card, a change event will appear in the sync file, that will match the existing Member Number and update the Alternate ID field with the Card Number (Cougar v11 only), so it doesn't create duplicate records in the SwiftPOS Database.
What Data Does It Sync?
|
Field Name |
SwiftPOS Field Mapping |
|
Membership No |
Member Number |
|
New Membership No |
Member Number |
|
Title |
Salutation |
|
Hello |
Not used |
|
First Name |
Member First name |
|
Other Name |
Middle Name |
|
Surname |
Surname |
|
Address Line 1 |
Address1 |
|
Address Line 2 |
Address2 |
|
Suburb |
Town |
|
State |
State |
|
Postcode |
Postcode |
|
Country |
Not Used |
|
Occupation |
Occupation Custom Field |
|
DOB |
Date of Birth (yyyy-MM-dd) |
|
Gender |
Gender |
|
Home Phone |
Home Phone |
|
Work Phone |
Work Phone |
|
FAX |
Work Fax |
|
Mobile |
Mobile |
|
|
Email Address |
|
URL |
Member Internet Address |
|
Financial To |
Renewal Date (yyyy-MM-dd) |
|
Date Joined |
Date Joined (yyyy-MM-dd) |
|
Magnetic Track 2 |
Not Used |
|
Membership Types |
Classification Mapped by Name using only the first Type sent |
|
IP Address |
Not used |
|
Action |
Internal Use |
|
Append Date |
Last Change Date (yyyy-MM-dd) |
|
CardID |
Alternate ID |
End of article ▲