Setting Up Credit Card Terminal in Xilnex ClassicPOS

Setting Up Credit Card Terminal in Xilnex ClassicPOS

Introduction

This guide explains how to configure and integrate credit card terminals with the POS system. The integration ensures smooth communication between the POS and payment devices, helping businesses process transactions securely and efficiently.

With this setup, you can:

  • Connect the POS system to supported credit card terminals.

  • Automate payment posting to reduce errors and reconciliation delays.

  • Support multiple terminal models for different business needs.

This documentation is intended for system administrators, technical teams, and implementation specialists familiar with POS operations, payment workflows, and basic network configuration.

The setup process is organized into the following sections:

  1. Terminal Connection and Network Configuration

  2. Card Payment Setup and Advanced Options

  3. Testing and Verification Procedures

  4. Troubleshooting Common Issues

Credit Card Terminal Setting

Before proceeding to the configuration, users need to make sure they are enabled with permission "Allow to access system configuration" due to the location of the setting being located in the System Configuration.

Setting Location


Setting Details

Default: Disabled (False)
When enabled: Card payments in the Sales module will be processed through the configured credit card terminal settings.



Terminal Configuration

List of supported credit card terminals:
  1. Adyen
  2. AUB PayMate
  3. BCA
  4. BCA v3
  5. BDO
  6. CardBiz
  7. Castles
  8. Castles Philippines
  9. GHL
  10. GHL CIMB
  11. GHL Global
  12. GHL Maybank
  13. GHL Philippines
  14. GHL Thailand
  15. GHL Thailand (Nexgo)
  16. IPay88
  17. IT Biz Flow
  18. IT Biz Flow (MBB)
  19. IT Biz Flow (PBB, HLB)
  20. IT Biz Flow Wireless
  21. KBank
  22. KTC
  23. Moneris (network)
  24. Moneris COM port
  25. MPOS
  26. NERA
  27. NETS
  28. PayMaya
  29. Paysys (Attended)
  30. Paysys (Unattended)
  31. PMA (NEWLAND)
  32. Revenue
  33. Share Commerce
  34. Share Commerce (A90 Pro)
  35. Softspace
  36. Softspace COM port
  37. SUNMIPAY

Common Terminal Settings: 

  1. Device Name: The display name of the selection during payment in POS.
  2. Port Name: Refers to the COM Port number used when the credit card terminal is connected to the POS device.
    1. Typically retrieved from Windows Device Manager
    2.   Applicable only to terminals with a wired connection

      NotesAdditional note: If this field is grayed out, the selected terminal does not support wired connections.
  3. IP Address: Refer to the IP Address of the terminal when it is connected to the network. Applicable to credit card terminal device with wireless connection.
    NotesAdditional note: If this field is grayed out, the selected terminal does not support wired connections.
  4. Port: Refer to the Port Number for the wireless connection device, suggest referring to terminal provider to get latest port number.
  5. Terminal ID: Refer to the Terminal ID setup for integration.
  6. Allow QR/Ewallet: The configuration to enable selection between card/ewallet payment, normally applicable to provider with ewallet payment supported.


    Notes
    Additional note: If this option is not available for the selected terminal, it means the device does not support eWallet or QR payment integration.
  7. Can Void: The configuration to enable POS auto triggers the refund request for the cancelled sales in POS.
    Notes
    Additional note: If this option is not available for the selected terminal, the integration does not support automatic void requests. Users will need to perform voids manually on the termina

Advanced Terminal Configuration:

1. Adyen
  1. Once the common setup for the Adyen terminal is completed, go to: System Configuration > Payment > Current Outlet > Adyen Setting.
  2. Enter the required details in this section.


2. GHL Nexgo
  • It is only required to setup Device Name and Can Void.
  • Please refer to this GHL Nexgo documention for more configurations.
3. GKASH
  • It is only required to setup Device Name, Terminal ID and Can Void.
  • The other required info will need to go to System Configuration > Payment > Current Outlet > GKash Setting to configure it:
4. Global Payment 
  • After setting up the common info, additionally info required is the Store ID which is located in System Configuration > Payment > Current Outlet > Global Payment.
5. MPAY
  • Common Setup: Fields such as Device Name, Allow QR/eWallet, and Can Void follow the standard configuration described in Common Terminal Settings.
  • IPOS Path: Specify the path to the program file provided by MPAY. This file is required for the integration to function.
  • Store ID: A unique Store ID will be issued by MPAY to differentiate terminals used across different store locations.


6. Payment Sense
  • Common Setup: Includes fields such as Device Name, Terminal ID, and Can Void.
  • Additional Configuration: To complete the setup, go to: System Configuration > Payment > Current Outlet > Payment Sense Setting.


7. Revenue Monster
  • Common Configuration: First, enter the basic details such as Device Name and Terminal ID.
  • Additional Configuration: Next, complete the setup in: System Configuration > Payment > Current Outlet > Revenue Monster Setting

Additional Configurations:

This Setting located at System Configuration > Payment > All Outlets > Credit Card


  1. Manual credit card info: Those configuration values will be used only when paid by manual credit card payment.
  2. Enable edit payment amount for integration: Setting to configure the edit function during Integrated Credit Card selection.
  3. Skip terminal selection for 1 terminal: This configuration is to enhance the operation flow to directly select the only 1 terminal instead of the process of required cashier to manually select again.
    1. Additional Note: If this setting is Enable and the terminal selection is with QR/Ewallet option, Classic POS will automatically select the first option to create payment request.

    • Related Articles

    • Setting Up GHL Nexgo Credit Card Terminal

      Introduction This article walks you through the setup process for the GHL Nexgo credit card terminal in Classic POS. Getting Started Before setting up the terminal configuration, there are few processes required to update first: Similar to the GHL ...

    • Enabling Staging Mode in Xilnex Classic

      Introduction The Staging Mode function provides a controlled environment for testing, configuration, and validation before applying changes to the live production system. It allows businesses to experiment with settings, workflows, and data without ...

    • Xilnex Classic BIR Discount Guidelines (Philippines)

      1. Overview The BIR Discount feature supports statutory discounts for eligible customers in the Philippines. This feature is currently: Available only for Philippines companies Supported only in the F&B POS for now Configured through Xilnex Classic ...

    • Understanding DuitNow QR Payment in ClassicPOS

      Introduction This document introduces the DuitNow QR payment feature available in the Xilnex Retail POS, enabling merchants to accept payments conveniently through Malaysia's national QR payment standard. The integration of DuitNowQR simplifies the ...

    • What is Menu Management in Xilnex Classic POS?

      What is Menu Management in Xilnex Classic POS? The Menu Management function provides a centralized and flexible platform to design, organize, and maintain your product catalog across all sales channels. It is built to streamline menu setup, ensure ...

    • Recent Articles

    • Managing Lark User Email Mapping in Xilnex for Lark

      Overview The Users card matches each Xilnex user to their Lark account by email. This is what lets features like Permission Approvals and Document Approvals deliver Lark cards to the right person. This article covers how to review the mapping and fix ...

    • E-Wallet and Credit Card Payment - Recheck Status & Force Complete

      This guide walks you through what to do when a payment goes through on the terminal or e-wallet, but Classic POS fails to commit sales. When Does This Happen? During payment, Classic POS will show a "Connecting to Ewallet party..." or processing ...

    • E-Journal for BIR Compliance (Philippines)

      Overview The E-Journal feature generates a .txt file that complies with BIR (Bureau of Internal Revenue) requirements in the Philippines. This feature is available only for the Philippines COM. Users from other countries' COMs will not be able to ...

    • Disconnecting or Reconnecting Xilnex for Lark

      This article covers how to disable a template, fully disconnect the integration from Lark, and reconnect it again. Disable a Template Turning a base off only stops that one base, everything else keeps syncing, and none of your existing data in Lark ...

    • Creating a Base in Xilnex for Lark

      Overview This article walks you through creating a base for a template, giving end users access to it in Lark, and verifying data is syncing correctly. Xilnex for Lark must already be connected before you start. If the Templates card isn't accessible ...

    • Popular Articles

    • Basic - How to create a voucher-coupon

      Voucher and coupon definition Voucher can be generated in bulk and can be used once Coupon can only be created one at a time (reusable code) and can be use multiple times Pre-voucher / coupon setup There are 2 things need to be prepared before we can ...

    • Understanding DuitNow QR Payment in ClassicPOS

      Introduction This document introduces the DuitNow QR payment feature available in the Xilnex Retail POS, enabling merchants to accept payments conveniently through Malaysia's national QR payment standard. The integration of DuitNowQR simplifies the ...

    • Intermediate - How to Configure and Use Approval Settings in Purchase Orders (PO)

      1.0 What is approval setting In general, "approval setting" refers to the configuration or process by which a request, action, or change must be reviewed and approved before it proceeds. The term is often used in business, software applications, and ...

    • Buy 2 for Special Price Promotion

      Use Case: Stock clearance, seasonal offers, or spotlight products. From the sample screenshot above, this promotion requires 2 items to trigger. If only 1 Milk Tea is added to the sales list, no discount will apply since the condition of 2 items is ...

    • Creating Delivery Type for Sales in Classic POS

      How to Create Delivery Type 1. Access to the [System Configuration] 2. Select the [Sales] section 3. In the [All Outlets] tab, look for the 'Delivery Type' 4. Click on the [Configure] In the Delivery Type Setup form: 1. Enter the Delivery Type. 2. ...