01Product

Processa POS & EMV Terminals

Semi-integrated PAX processing through BroadPOS, with GWLink Lite on the terminal. The IDTech VP3350 still covers chip, tap, and swipe on Processa and the Virtual Terminal, including Apple Pay, Google Wallet, and Samsung Pay.

Need terminology context? Visit the payments glossary.

Fluid Pay® Emv & Mobile Feature
New for integrations

Processa POS on the PAX terminals you already deploy

GWLink Lite is the app. Your software drives the terminal, or staff sell from the screen. Every card interaction goes through BroadPOS. Catalog, vault, receipts, and results stay on Fluid Pay®.

  • Your software drives the terminal

    Send a sale, refund, void, auth or batch close. A retry with the same command ID runs once. One transaction is in flight; the rest wait their turn.

  • Or staff sell from the screen

    Product catalog, keyed amounts, tax, and receipts on the printer or by text. The counter sale lands on the same ledger your platform already reads.

  • BroadPOS takes every card

    Tap, dip, and swipe stay inside BroadPOS, under the processor’s PCI scope. Processa POS sees a masked card number.

  • Your brand, pushed to the fleet

    Three colors, a logo, and a name from PAXSTORE. The running terminal restyles without a reinstall, and a cold start is already branded.

PAX Android, with BroadPOS

  • A920
  • A920Pro
  • A80
  • A35
  • A77
  • IM30
  • Other PAX Android terminals

GWLink Lite

Terminal ID and an app key

Remote commands, card sales, batch close, today’s totals, and history. A Lite badge in the header shows which mode the terminal is in.

Full

Add a gateway API key

The product catalog, customer vault, card-on-file charges, and catalog-priced tax. Push the key from PAXSTORE or enter it in Settings. Same app, no reinstall.

Talk to our team

Processa POS on PAX™. EMV, NFC, and contactless on every other device your merchants own.

EMV stands for Europay, MasterCard® and Visa® and refers to the security model added to card-present payments through the chip embedded in credit, debit, and prepaid cards. Chip cards are extremely difficult to clone, and combined with hardware encryption, tokenization, and additional authentication they meaningfully reduce card-present fraud. *

Semi-integrated on PAX™, through BroadPOS

Processa POS runs on the PAX™ Android terminals partners already deploy. GWLink Lite is the app on the device. It keeps one outbound, encrypted connection open to the gateway. Your platform sends a sale, refund, void, auth, batch close, or card read, and BroadPOS takes the screen for tap, dip, or swipe. The approved or declined result comes back on that same connection, matched to the command you sent.

A retry with the same command ID runs once. The terminal handles one transaction at a time and queues the rest.

Staff can also sell from the terminal itself: a product catalog, a keyed amount, tax, a receipt on the built-in printer or by text, and batch close. That counter path posts to the same ledger and the same results your platform already receives. If the connection drops, the result stays on the device and is delivered when it reconnects. Terminal-initiated results are also posted to your webhook.

Configuration is a PAXSTORE parameter push: environment, terminal ID, app key, API key, merchant ID, tax rate, and brand. A corrected key brings the terminal back. Settings covers pilots and development when you would rather type it in.

GWLink Lite needs a terminal ID and an app key. Add a gateway API key and the same app unlocks Full mode: the catalog, customer lookup, card-on-file charges, and catalog-priced tax. Switching does not require a reinstall.

Supported devices include the A920, A920Pro, A80, A35, A77, IM30, and other PAX™ Android terminals with BroadPOS installed and provisioned by the processor. Dejavoo™ terminals on the certified list remain EMV chip-card ready.


One stack, every form factor

Processa POS on the PAX™ counter. Processa on the phone. Virtual Terminal on the laptop. Same vault, same reporting, same dispute flow — your merchants don't relearn payments every time a form factor changes.

We've extended certified EMV beyond the countertop. Through a native integration with the IDTech VP3350, your merchants accept chip, contactless, and swipe payments anywhere a phone, tablet, or laptop goes — and settle directly into the Fluid Pay® gateway.

We recommend connecting the VP3350 over USB-C: it's the most reliable pairing for both mobile and desktop, and it keeps the reader powered while it works. Bluetooth is supported as a fallback when a wired connection isn't practical. Card data is encrypted at the read head with DUKPT key management before it ever reaches the device or browser running Processa or the Virtual Terminal.

One reader, two surfaces

  • Processa — plug the VP3350 into a phone or tablet over USB-C and accept EMV chip, contactless tap, and magnetic swipe directly inside our partner-branded mobile app. Service techs, delivery routes, mobile retail, pop-ups — anywhere a swipe used to live, a chip read now does.
  • Virtual Terminal — connect the VP3350 over USB-C to a laptop or tablet and run card-present transactions from any browser. No plugin, no extra software — the reader is recognized the moment it's plugged in.

What you get out of the box

  • Full EMV liability shift on chip transactions — no more keyed-in chip cards in the field
  • Contactless support for Apple Pay™, Google Pay™, Samsung Pay™, and tap-to-pay credit and debit cards
  • Hardware-level encryption at the read head with DUKPT key management
  • USB-C across the board — one cable, one connection model from Processa on a phone to the Virtual Terminal on a laptop (Bluetooth available when wired isn't an option)

Same gateway, same reporting, same residuals. The VP3350 just gives your merchants a way to accept every card-present payment type without buying or learning a new terminal.


NFC payments are contactless payments that use near-field communication (NFC) technology to exchange data between readers and payment devices like Apple Pay and Google Pay e-wallets in smartphones and smartwatches, or tap-to-pay credit and debit cards. NFC devices must be within ~2 inches of each other to complete a payment. *

NFC contactless support for:

  • Apple Pay™
  • Google Wallet™
  • Samsung Pay™

For merchants who are hybrid by default

Today's coffee shop is also today's catering business and today's online subscription. They need every form factor and one bill — one vault, one reporting view, one dispute flow.

Touch-screen terminal models are also available, with 3G support where needed. WiFi support is built in to every device, so your merchants process anywhere with an active data connection. Daisy-chain to a phone hotspot when WiFi isn't available. Skip the per-year mobile-swipe replacement cycle by using the same VP3350 across phone, tablet, and laptop.

Every signature captured on the terminals is stored in the gateway alongside the transaction — so receipts, disputes, and reporting all live in one place. Less paper for the merchant, less context-switching for support.

Contact us for the current certified mobile processing options.

Work smarter, not harder.

Frequently asked questions

What does semi-integrated mean on a PAX terminal?

Your software sends the payment. Processa POS, running as GWLink Lite on the terminal, carries that command to BroadPOS, which takes the screen for tap, dip, or swipe. The approved or declined result comes back on the same connection, matched to the command you sent. Staff can also sell from the terminal screen, and that sale lands on the same ledger.

What does GWLink Lite need to go live?

A PAX Android terminal with BroadPOS installed, a Fluid Pay terminal ID, and an app key. That covers remote commands, card sales, batch close, and the day’s totals. Add a gateway API key and the same app unlocks Full mode: the product catalog, customer vault, card-on-file charges, and catalog-priced tax. Push the key from PAXSTORE or enter it in Settings. No reinstall.

Does card data pass through Processa POS?

Card data stays inside BroadPOS, under the processor’s PCI scope. Tap, dip, swipe, and keyed entry stay there. Processa POS receives a masked card number. The app key authenticates the terminal. The gateway API key is used for catalog, vault, and transaction calls, and it stays off the terminal connection.

Talk to a gateway that isn't trying to sell to your merchants.

No direct boarding. No residual surprises. No legacy stack to work around.