Card processing is configured per location under Locations → Integrations. Enable processing, pick your processor, enter the credentials from enrollment, map each terminal to a register on the Registers & Terminals tab, then initialize the reader before the first real sale.

Integrated card processing is what makes the register send the exact total to a terminal and bring the approval straight back onto the sale. Setup always happens on the location — not in Store Config — so each store can run its own merchant account, processor, or terminal fleet.

If you are still deciding which processor to use, start with choosing a payment processor. For PHP POS Payments Standard and Premium (Valor and Equinox terminals), the full walkthrough is in PHP POS Payments. This article covers the shared setup path, every field on the Integrations and Registers & Terminals tabs, and a credential summary for each third-party processor — dedicated per-processor setup guides live alongside this article in the Payments section of the Help Center.

The shared setup path

You need the Locations module with the Add, Update permission action to do this. For every processor the steps look the same:

1. Go to Locations and click to edit the location that will take cards.
2. Open the Integrations tab.
3. Check Enable Credit Card Processing. A Credit Card Processor dropdown appears.
4. Choose your processor from the dropdown.
5. Enter the credentials from your enrollment letter or processor dashboard (field-by-field lists below).
6. Open the Registers & Terminals tab and enter the terminal identifier for each register that takes cards — Terminal ID, Valor EPI, or CardConnect HSN depending on the processor.
7. Click Save.
8. For Datacap-family processors, click Initialize credit card reader and wait for it to finish — initialization can take a minute or two.

HTTPS is required: integrated processing only runs when the point of sale is served over a secure connection (always true on the cloud edition).

Every setting on the Integrations tab

Not every field applies to every processor — the form shows only the ones your selected processor uses.

• Enable Credit Card Processing — master switch; unchecking it returns the register to non-integrated Credit/Debit entry. Off by default.
• Credit Card Processor — the processor this location uses. The full list of choices is in choosing a payment processor.
• Disable Amount Confirmation when processing credit card — skips the on-screen amount confirmation step when sending a charge to an EMV terminal. Off by default.
• Use Integrated EBT — runs EBT tenders through the terminal instead of recording them manually. Requires an EBT-capable merchant agreement. Off by default.
• Integrated Gift Cards (Datacap family) — adds an Integrated Gift Card tender processed through the terminal. Off by default.
• EMV Merchant ID / Terminal ID (Datacap family) — the merchant identifier from your processor's setup sheet.
• COM port (Datacap family) — serial port for the terminal; COM 9 is the default.
• Listener port (Datacap family) — the port the local Datacap listener answers on; port 3333 is the default.
• Net E-Pay Server (Datacap family) — only set a value here if NETePay is not installed on the same machine as the browser; enter the host running it.
• EMV Device Override / Non EMV Device Override (Datacap family) — device profile names that override the processor default. Each processor ships with a sensible default (for example, Worldpay uses EMV_VX805_WORLDPAY, Heartland uses EMV_IPP320_HEARTLAND); with Other EMV processor selected, these two fields are required because there is no default. Your setup sheet tells you what to enter — TSYS enrollments typically use EMV_VX805_TSYS with VX805XPI_CTLS.
• Initialize credit card reader — button that loads parameters into a Datacap-family terminal. Run it after first setup, after a terminal swap, and after NETePay reinstalls.

Processor-specific credential fields (Merchant IDs, API keys, and so on) appear in the same panel and are listed per processor below.

The Registers & Terminals tab

Each register row maps one physical terminal to one lane. The columns you may see, depending on the processor:

A colored status dot next to each register name shows whether its terminal is currently reachable on processors that report status. Below the table, Register to use for manual entry & payment links picks which register's terminal credentials are used for keyed-in payments and emailed payment links.

PHP POS Payments (recommended path)

PHP POS Payments is the house-branded processing. Standard (processor choice "PHP POS Payments Standard") runs Valor VP100 / VL110 terminals with a Valor App ID on the location and a Valor EPI + Valor App Key per register. Premium (processor choice "PHP POS Payments Premium") runs Equinox 6200 / 8500 devices with a PHP POS Payments Merchant ID, API Key, Bearer Token, and Signing Key on the location and a Terminal ID per register, plus an in-app portal. Hardware networking and every field are covered in PHP POS Payments.

CardConnect

CardConnect provides the terminal hardware as part of enrollment. After you receive your letter:

1. Enable credit card processing and set the processor to CardConnect.
2. Enter the Merchant ID exactly as shown.
3. Enter the Rest Username and Rest Password from enrollment.
4. On Registers & Terminals, enter each terminal's CardConnect HSN — shown on the terminal screen — on its register row.

CardConnect support: 877-828-0720.

Square and Square Terminal

Two Square paths exist:

• Square (mobile) — pairs with the PHP Point Of Sale mobile app and the Square app on the same device. Choose Square, then set the Currency Code (default USD) and leave Multiplier to get total in cents at its default of 100 unless support tells you otherwise. On a sale the app hands off to Square to finish the charge and returns to the point of sale.
• Square Terminal — choose Square Terminal, click Connect To Square to authorize via Square's OAuth login, pick your Square Location ID, then on each register row click the get-device-ID button and enter the pairing code on the Square Terminal when prompted. Disconnect From Square reverses the authorization.

Stripe

Stripe is configured with keys from the Stripe Dashboard (Developers → API keys):

1. Enable credit card processing and choose Stripe.
2. Set the Currency Code (default usd; Stripe's supported-currency list is linked from the field).
3. Paste the Stripe Secret Key and Stripe Publishable Key (live keys, not test keys).
4. For countertop chip-and-tap, on each register row click Register Stripe Reader and enter the registration code shown on the Stripe reader's screen. Unregister Stripe Reader removes the pairing.

Without a Stripe Terminal reader, card entry uses a MagTek USB swipe reader or keyed entry.

Braintree

Braintree uses three values from the Braintree Control Panel (Account → My User → API Keys):

1. Generate an API key if you do not already have one.
2. Enable credit card processing, choose Braintree, and enter the Merchant ID, Public Key, and Private Key.

This path is aimed at swipe or keyed entry rather than a full EMV pin pad; use an EMV-native processor when chip and contactless at the counter are required.

Worldpay (Vantiv / Mercury) and the other Datacap processors

Several processors share the same Windows + Datacap pattern: an EMV terminal (Verifone VX 805 or compatible; Heartland uses the Ingenico iPP320), Datacap NETePay, and its local listener. The listener must stay running whenever you take cards. The family includes Worldpay (Formally Vantiv/Mercury), Heartland, EVO, Worldpay, First Data, and Other EMV processor (used for TSYS and unlisted Datacap-compatible enrollments).

The outline (each processor's dedicated guide has the exact screens):

1. Install NETePay from the link in your enrollment letter and restart when prompted so the listener launches. Allow it through the Windows firewall.
2. In NETePay, obtain a serial number from Datacap PSCS when asked, then under Setup → Merchant Parameters → Load New Parameters choose I have my Deployment ID and enter the ID from your processor's technical support.
3. In PHP Point Of Sale, enable credit card processing, select the processor, and enter the EMV Merchant ID / Terminal ID from your setup sheet.
4. Keep COM port at 9 and Listener port at 3333 unless your installer changed them.
5. Save, then click Initialize credit card reader and wait for it to finish.

Hosted Checkout (Worldpay/Vantiv) needs no local pad: enter the Hosted checkout Merchant ID and the Mercury Generated Password created in the Vantiv Integrated Payments portal. IP Tran Cloud puts a small device on your network so several stations share terminals: enter each IP Tran Device ID on the register row, leave the merchant ID blank unless Vantiv says otherwise, and use the per-register Update Params and Initialize credit card reader links.

If initialization fails with "Unable to initialize device," confirm the listener is running, the COM port matches, and the terminal has power and a network or serial path to the PC.

After setup

1. Ring a small test sale — turn on test mode first from the register's menu (Enable Test Mode) so nothing posts to your reports.
2. Choose Credit at payment time; the terminal should wake with the amount for chip, tap, or swipe.
3. Confirm the approval attaches to the sale and the receipt shows the card tender, then disable test mode.

Day-to-day card flows — signatures, cards on file, pre-auths, voids, refunds, manual entry, stuck terminals — are in taking card payments. Tips and split tenders are in payment types, tips and split payments.

Troubleshooting

The processor dropdown doesn't appear. Check Enable Credit Card Processing first — the dropdown and credential fields only render once it is checked.

"Unable to initialize device" on a Datacap setup. The listener isn't reachable. Confirm NETePay is running, the firewall allows the listener port (3333 by default), the COM port matches the terminal (COM 9 by default), and the terminal is powered.

Cards worked yesterday and stopped today (Datacap family). Almost always the Windows PC rebooted or slept and the listener didn't come back. Start NETePay, then run Initialize credit card reader from the location.

Which register's terminal is used for keyed-in payments? The one selected under Register to use for manual entry & payment links on the Registers & Terminals tab.

Can two registers share one terminal? Enter the same terminal identifier on both register rows. With Worldpay's IP Tran Cloud this is the designed model — the IP Tran device sits on the LAN so multiple stations reach it.

Do I need to re-enter credentials at my second location? Yes. Every location carries its own processor, credentials, and register mappings, even when both use the same merchant account.

Where do I turn processing off? Uncheck Enable Credit Card Processing on the location and save. Existing sales keep their card history; the register simply records Credit/Debit tenders without talking to a terminal.