PaymentTerminal

PaymentTerminal

Payment Terminal (Card Machine Integration)

A product-knowledge guide for support and internal staff.


1. What is it?

A payment terminal is the card machine a customer taps, inserts, or swipes their card on. iPadPOS can connect to a payment terminal so that when the cashier takes a card payment, the amount is sent to the terminal automatically and the approved/declined result comes straight back into the sale — no re-typing amounts, no separate reconciliation.

The app supports a few terminal brands — some connect over your network, and one (GKash) is a cloud gateway with no physical machine at all, where the customer is charged remotely.


2. Why merchants use it

  • Fewer errors — the sale amount is sent to the terminal automatically, so staff can't key in the wrong figure.
  • Faster checkout — approve on the terminal and the POS records the payment instantly.
  • Cleaner books — card payments are tied to the sale, and terminals support settlement (batching the day's card transactions).
  • Void support — a card payment can be voided back through the terminal from Sales History.

3. Supported terminals & how they connect

Brand How it connects Notes
CardBiz Network (Ethernet / Wi-Fi) Reached by its IP address on the same network as the iPad.
M1Payment Network Reached by IP address + port, and needs an Encryption Key.
GKash Cloud (remote) No physical terminal. The customer is charged in the cloud and the result returns automatically. Only one GKash terminal can be configured.

How a card payment works with a terminal

1. Cashier chooses the card / terminal payment method on the Payment screen and enters/confirms the amount.

2. The amount is sent to the terminal.

3. The customer taps / inserts / swipes their card and the terminal processes it. (For GKash, the charge happens in the cloud — no local device step.)

4. The result (approved or declined) comes back to the POS automatically, and an approved payment is recorded against the sale.


4. Requirements & access

  • A supported terminal — CardBiz, M1Payment, or a GKash account.
  • The right connection:
  • CardBiz / M1Payment → the terminal and iPad on the same network; you'll need the terminal's IP address (and port for M1).
  • GKash → cloud credentials (Terminal ID, Client Merchant ID, Client Secret) from the GKash account.
  • Configured in Settings — terminals are set up under Settings → Configure Terminals (typically a manager/admin task).

5. Setup — step by step

Step A — Open terminal settings

1. Go to Settings.

2. Open Configure Terminals (under the terminal settings section).

3. You'll see any terminals already configured. Tap add / new terminal to create one.

Step B — Choose the brand

Select the Terminal Brand: CardBiz, GKash, or M1Payment. The fields you need to fill in change depending on the brand.

Step C — Fill in the details for that brand

  • CardBiz (network):
  • Terminal Name — a label you choose.
  • Terminal Address — the terminal's IP address (four boxes, e.g. 192.168.1.50).
  • The terminal must be on the same network as the iPad.
  • M1Payment (network):
  • Terminal Name, Terminal ID.
  • Terminal Port.
  • Encryption Key (provided by MobilityOne / M1).
  • GKash (cloud):
  • GKash Terminal ID, GKash Client Merchant ID, GKash Client Secret (from the GKash account).
  • No IP address — it's cloud-based. Remember: only one GKash terminal is allowed.

Step D — Save

Save the terminal. It's now available to select as a card payment method on the Payment screen.

Step E — Test

Run a small test transaction (and void it, or use the terminal's test mode if available) to confirm the iPad and terminal talk to each other before going live.


6. Good to know / limitations

  • Different brands connect differently. Network/IP (CardBiz, M1Payment) or cloud (GKash). A "terminal won't connect" issue is usually about the connection type — check the right thing for the brand (see Troubleshooting).
  • GKash has no physical machine and is limited to one configured terminal. The customer is charged remotely; the result returns on its own.
  • Network terminals need matching networks. CardBiz/M1 must be on the same network as the iPad, with the correct IP address (and port for M1).
  • Settlement matters at close. Card terminals typically need a settlement (batch close) to bank the day's transactions — make sure staff do this per the terminal provider's process.
  • Voids go through the terminal too. Voiding a card payment (from Sales History) sends the void to the terminal — the terminal must be connected/reachable for it to work.
  • Credentials come from the provider. Encryption keys and GKash credentials are issued by the terminal provider; the app can't generate them.

7. Troubleshooting

Symptom Check Fix
CardBiz / M1 terminal unreachable Are the iPad and terminal on the same network? Is the IP address correct (and port for M1)? Correct the IP/port in Configure Terminals; confirm both devices are on the same Wi-Fi/LAN.
M1 payments fail / rejected Is the Encryption Key correct? Re-enter the exact key supplied by M1/MobilityOne.
GKash charge doesn't come back Internet connection on the iPad? Correct GKash credentials? GKash is cloud-based — ensure the iPad is online and the Terminal ID / Merchant ID / Secret are correct.
"GKash Terminal Already Exist" Trying to add a second GKash terminal? Only one GKash terminal is allowed — edit the existing one instead of adding another.
Can't void a card payment Is the terminal connected/reachable? The void is sent to the terminal — reconnect it, then retry the void from Sales History.
Day's card totals don't match the bank Was settlement run on the terminal? Perform the terminal's settlement/batch-close per the provider's process.

8. FAQ

Q: Which card machines does iPadPOS support?
CardBiz (network), M1Payment (network), and GKash (cloud/remote).

Q: Do I need a physical terminal for GKash?
No. GKash is cloud-based — the customer is charged remotely and the result returns automatically. Only one GKash terminal can be configured.

Q: Where do I set up a terminal?
Settings → Configure Terminals.

Q: The terminal won't connect — what's the first thing to check?
For CardBiz and M1, check the IP address and that both devices are on the same network; for GKash, check internet + credentials.

Q: Where do the encryption key / GKash credentials come from?
From the terminal provider (M1/MobilityOne, GKash). The app doesn't generate them.

Q: Can I have more than one terminal?
Yes — multiple network terminals can be configured, except GKash, which is limited to one.

Q: How do card payments get banked?
Terminals use settlement (batch close) — run it per the provider's process, usually at end of day.


    • Recent Articles

    • How to create stock request in Xilnex Classic

      Stock Request Stock Request is the function allowing the outlets to make request stocks from HQ or other outlets. Basic Stock Request Go to Inventory > Stock Request Select Request Stock From outlet. Select ETA (Expected Time Arrival) if any. a) Add ...
    • Coming Soon: Promotion Hierarchy

      What is Promotion Hierarchy? Promotion Hierarchy is a new feature in the Xilnex Portal that allows users to define promotion eligibility by combining multiple item attributes within a single rule. Instead of creating multiple separate promotion ...
    • SecondaryScreen

      Secondary Screen (Customer-Facing Display) A product-knowledge guide for support and internal staff. 1. What is it? The Secondary Screen turns a second display — connected to the iPad by cable — into a customer-facing screen. While the cashier keeps ...
    • PaymentTerminal

      Payment Terminal (Card Machine Integration) A product-knowledge guide for support and internal staff. 1. What is it? A payment terminal is the card machine a customer taps, inserts, or swipes their card on. iPadPOS can connect to a payment terminal ...
    • OutOfStock

      Out of Stock (Marking Items Unavailable) A product-knowledge guide for support and internal staff. 1. What is it? Out of Stock (OOS) lets a cashier mark a menu item as temporarily unavailable — the "we've run out" / "86'd" button. Once an item is ...
    • 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. ...