Network Configuration for Fuel Station Loyalty Programs

Fortinet Switches and Management

• Fortinet switches can be managed by SageNet and should not require contacting Hughes for firewall rules.
• Pre-whitelisted Tobacco Scan Data and Engage traffic should be allowed.

Branded Fuel Sites

• BP, P66, 76, and Conoco sites should be pre-configured to allow loyalty traffic.
• Branded fuel sites include:
  • BP
  • Chevron/Texaco
  • Conoco/Phillips/66/76
  • Citgo
  • Sunoco
  • Marathon
  • Sinclair

Mako Topology

• Mako supports Desktop Sync and Cloud Sync.
• Supported versions: 4 port, 6500-M or higher (2 ports do not support secure network segmentation for back-office devices).
• 4 ports (Mako Model 6500 M +) have a specific segment for the back office.
• Contact information: [email protected], Phone: 1-800-851-4691

Paysafe Topology

• Paysafe is PDI owned.
• ControlScan manages PaySafe and CradlePoint routers.
• Paysafe no longer adds firewall rules for Back-Office computer loyalty.
• Requirements: all loyalty sites must be on Cloud sync, and only chat Paysafe for issues with the VPN tunnel (or SNAT) assigned to the site.
• Verify store and transaction in SkuOps:
  • Search for Store ID
  • Sync Status must show connected
  • At least one transaction in the 30-Day TX Count table

Cloud Sync

• Allows retailers to use Skupos services without a back-office computer.
• Established VPN connection through MNSP providers.
• Communication channels are enabled between MNSP cloud and Skupos cloud using cloud-to-cloud VPN tunnels.
• Loyalty communication is always initiated by the client POS Site Controller.
• Back Office communication is always initiated by the Skupos Cloud.
• Skupos communicates and pulls transactions via the SNAT IP assigned by the MNSP provider.

Cloud Sync - SNAT IP

• No two sites MNSP router should have the same SNAT IP.
• SNAT is one-to-one for a point-of-sale's onsite MNSP router.
• SNAT is assigned to the specific MNSP router itself, not a store ID.
• Integration needs to have the right SNAT entered in the most up-to-date Skupos SID in Sku-Ops.

Cloud Sync Installation

• Clover Sync Installation steps:
  1. Confirm Skupos App on Clover Device.
  2. Confirm correct Merchant ID mapped.
  3. Customer Integration covers talk tracks to educate retailers.
  4. Verify Email address, enroll in SMS messages.
  5. Review Dashboard, Stores page, Promotions, Scan Data Enrollment, Payout, Employee Handbook, Support Chat/Help Center, Survey Response.

Cloud Sync - Verifone Installation Steps

• Mako MNSP requires Firewall Form process before installation.
• Cybera and PaySafe do not require MNSP approval.
• Steps:
  1. Confirm SNAT is available in Salesforce.
  2. Configure the Verifone Commander (skuposcloud user).
  3. Uninstall Desktop Sync (if applicable).
  4. Configure the store in Sku-Ops.
  5. Configure loyalty on the Verifone Commander (PCATS) with Device Specific Route.
  6. Verify site is communicating with the Engage Host.
  7. Perform a test transaction.
  8. Onboarding Talk Tracks.

Cloud Sync - Gilbarco Installation Steps

• If site is Mako MNSP, they will need to go through Mako Firewall Form process before installation.
• Cybera and PaySafe do not require MNSP approval.
• Steps:
  1. Confirm SNAT is located in Salesforce account.
  2. ID: Store ID.
  3. POS: Verifone, GVR, NCR, and Clover.
  4. Store Name: Name of Store.
  5. State: Store Location State.
  6. MP: This checkbox aids in influencing the MP Discounts that appear in the report.

Sku-Ops - TSD Reporting tab

• RJR/ITG Reporting Accounts – Generate.
• Quick link to the Submissions subtab for a particular file and week-ending date.
• Altria/RJR Submissions:
  • Shows an account’s or group of accounts’ Altria/RJR files for a particular week-ending date.
  • You can search by different criteria on the Submissions Report List subtabs.
  • Submission Report List Statuses:
    • Generation Pending.
    • Generation Failed.
    • Not Ready.
    • Ready to Submit.
    • Submission Pending.
    • Submitted.
    • Submission Failed.

Challenge Questions

• Answers:
  1. Where can you find the Retailers Skupos Dashboard login information?
     • On the Chain Page.
  2. Where can you find the Sync/CloudSync status for a retailer?
     • On the Store Page.
  3. Which Subtab of TSD Reporting allows you to search for files for a particular week-ending date?
     • The Altria/RJR Submissions Subtab.
  4. Where can you find the Reporting Status of an Altria Account?
     • Through the Altria Reporting Accounts – Config section.
  5. Where can you find a list of all the stores associated with the report, their configurations, and POS information?
     • Through the Altria/RJR Reporting Accounts – Stores section.
  6. Which can you find the MP checkbox?
     • The RJR/ITG Reporting Accounts – Stores section.
  7. What does the Reporting status of Certified represent on the RJR Reporting Accounts tab?
     • The account is submitting weekly files to try and get validated, and has submitted four weeks of back data files to MSA.
  8. Who is MSA?
     • MSA is the company that processes files for RJR submissions.