PayPilot is where you do all initial configuration: merchants, payment apps, processing channels and terminal parameters.
TMS is only needed for device-level work, such as remote assistance and pushing apps or updates to terminals.
Was this helpful?
How can we help?
Answers for ISOs, ISVs and merchants on CodePay terminals, Register, PayPilot and TMS.
POPULAR
Browse by topic.
All articles
48 ARTICLESWhen we ship devices, we assign them to your TMS account only. They are not assigned in PayPilot.
To use them, create a merchant in PayPilot and assign the terminals to that merchant.
For a proof of concept or your first shipment, we can create a demo merchant for you in PayPilot and assign the terminals before they ship. Just ask your CodePay contact.
Was this helpful?
CodePay does not use separate live and test environments. Instead, select “Sandbox” in the merchant account contract in PayPilot.
Every transaction under a sandbox merchant account is a test transaction. No real charges are made.
Was this helpful?
For TSYS MultiPASS, your terminal parameters, including the TID, come from the VAR sheet. Follow the guide below to request and read it.
Was this helpful?
In TMS, create sub-agents from the partner list.
In PayPilot, use roles to separate sub-agents. See “Create an Agent Role” or “Create Manager Role” in the permissions guide.
Was this helpful?
All CodePay terminal models are certified with Fiserv and TSYS.
•Fiserv: certified on the Nashville front end.
•TSYS: certified on MultiPASS.
Elavon certification is in progress for all models.
Was this helpful?
We support the Nashville front end, with Nashville or North as the back end. The Omaha front end is not certified.
You have two options when boarding:
•Board on Nashville for both the front end and back end.
•Board on the Omaha platform (Access One), which defaults to the Omaha back end, then select Nashville as the front end.
Merchants boarded on the CardConnect platform default to the North back end.
Was this helpful?
Funding timing is the same whether the batch settles at 11 PM on the business day or overnight at 2 AM.
For example, transactions on March 18 that settle at 11 PM on March 18 or 2 AM on March 19 are both funded on March 20. This applies to Omaha and Nashville.
Was this helpful?
TIDs registered under CodePay show the equipment code “CodepayRegister GwSrsSs”. This is the same for Nashville and Omaha front ends.
Was this helpful?
Traditional terminals are usually configured as processor-direct (for example, TSYS Sierra), so their VAR sheet reflects the processor’s terminal configuration.
CodePay devices are gateway-based: the terminal talks to the CodePay gateway, and the gateway routes the transaction to the processor (such as TSYS MultiPASS). Because the transaction flow is different, the VAR sheet parameters are different too.
Was this helpful?
Sierra is terminal-based and uses traditional VAR sheets. Transactions are stored on the device and uploaded to the host in batches at close.
MultiPASS is a host-based gateway. Transactions are stored on the host in real time, and batch close is simply a command.
Was this helpful?
Not at this time. Fiserv’s Canadian platform differs from the U.S. version, so our U.S. certifications do not carry over. Our current focus is the U.S. market.
Was this helpful?
Yes. PIN bypass is supported through the CodePay gateway for TSYS and Fiserv and can be switched on or off in configuration.
It works on all terminal models, because terminal configuration is managed centrally in PayPilot.
Was this helpful?
Yes, not only devices with a separate PIN pad. On all-in-one Android terminals, PIN entry runs in a secure environment inside the terminal, connected to an HSM workflow (Futurex) and built into the EMV transaction flow.
The term “PIN pad” comes from older POS setups where PIN entry was a separate device.
Was this helpful?
Yes. EBT is included in our Fiserv and TSYS certifications, so no separate EBT certification is needed.
A single PIN encryption key covers both debit and EBT, and remote key injection supports this setup. When applying for the VAR sheet, request key code 500. For a different key code, ask Fiserv to send the key to Futurex.
Was this helpful?
This is rare, and there are two safeguards:
•Before retrying, use the gateway’s transaction query API to check the actual status. This prevents double charges.
•Void any incorrect or duplicate transaction on the terminal or in PayPilot.
Was this helpful?
Yes. In the payment app, open the Payment menu at the top of the screen and select Refund. Two refund types are supported:
•Reference refund, linked to the original transaction.
•No-reference refund, a standalone refund without the original transaction.
Was this helpful?
Partial refunds apply to the sale amount only. Fees such as tips, surcharge or tax cannot be partially refunded, because the system cannot tell which fee item a partial amount should come from. Fees are refunded separately.
Was this helpful?
At the processor level, a tip adjustment after the batch has closed is processed as a new sale. It is not added to the original authorization.
In the CodePay gateway the original transaction and the tip adjustment are linked, so you can trace them together for audits.
Was this helpful?
Surcharge depends on the card type, not the transaction type. If credit and debit are set up as separate charge methods, surcharge applies to credit cards only, even when a debit card is processed without a PIN.
To charge more when debit is processed without a PIN, dual pricing is usually the better approach.
Was this helpful?
Yes. Terminals have a built-in barcode and QR scanner for scan-to-pay and can display a QR code on screen for customers to scan.
QR payments through crypto wallets are not supported.
Was this helpful?
Not currently. Each terminal is bound to one MID. If you have a business need for multi-MID, tell us the use case and expected scale.
Was this helpful?
Gift cards are not supported out of the box. Each gift card program has its own accounts, flows and interfaces, so each needs its own integration.
We recommend:
•Running your own POS app or a third-party app on CodePay devices to accept gift cards.
•Using the CodePay SDK and device features, such as card reading, QR scanning and on-screen interaction, to build the integration.
For supported NFC card types (Type A/B, MIFARE, FeliCa and more), see the NFC section of each device’s specifications. Have a specific program in mind? Contact us.
Was this helpful?
The payment app supports standard transaction data. Full Level 2 / Level 3 enhanced data, such as invoice or line-item fields, is not currently supported. Let us know how important this is for your portfolio.
Not to be confused with certification levels: L1 certifies hardware, L2 certifies EMV and L3 certifies the processor integration.
Was this helpful?
No. PayPilot focuses on core payment functionality and does not store customer information or offer loyalty or marketing features. Terminals also do not capture customer details such as phone or address after a transaction.
If you need this, contact us to discuss options.
Was this helpful?
Yes, both are available. To print automatically after every batch close, set it up in PayPilot:
1.Merchants → Merchant list → select the merchant.
2.Pay-apps → CodePay Register → Batch Close.
3.Enable “Push the print command” and “Print statement of batch” (detailed report).
You can also choose summary or detail manually when you tap Batch Close on the terminal.
Was this helpful?
Yes. Enable Tip, but leave the “Print on the receipt” option off.
Was this helpful?
2¼" × 40 mm thermal paper.
Was this helpful?
Use rolls that match the size and thickness of the roll included in the box. Rolls from other vendors can be slightly larger or thicker and may jam.
Was this helpful?
Terminals carry a one-year warranty starting from MID activation (end-user purchase). For repairs after the warranty period, contact CodePay support.
Was this helpful?
Tested at 100% screen brightness, screen on:
•P5 Pro and P5K: about 21 hours (Wi-Fi and GPS on, Bluetooth off).
•P5L: about 9.5 hours.
•T2: about 9 hours.
A full charge takes 3 to 3.5 hours with the device powered off.
Was this helpful?
Wi-Fi 5 (802.11ac).
Was this helpful?
Kiosk mode is usually caused by ECR mode. Press and hold the triangle and square buttons at the same time.
Was this helpful?
Update the device ROM over the air from TMS. The guide below explains how to create the update task.
Was this helpful?
Developer mode is used for debugging. It is pushed to devices from TMS. Send us the serial numbers of the terminals you are developing on, and we will push developer mode to them.
Was this helpful?
1.CodePay enables your app in PayPilot.
2.Turn the app on for the merchants who need it.
3.Upload the APK file to TMS.
4.Push the app to the devices.
Uploading to TMS is only needed to install the app on CodePay terminals such as T2, P5 Pro and P5L. The integration guide below is for the app’s developers.
Was this helpful?
Open the app’s detail page in TMS.
1.Click Upload to add a new version.
2.Click Delete to withdraw a version.
Was this helpful?
Yes. GMS must first be turned on for those devices from TMS.
Was this helpful?
CodePay is not involved in third-party POS development or operation. Ask the POS provider for the CodePay-specific APK and its installation guide, then upload and push it through TMS.
Was this helpful?
Start with the software provider (ISV). They own the app and the integration logic, so they can usually see where a problem comes from.
If they find it’s related to CodePay, they can escalate to us with the technical details. For clear card-processing issues unrelated to the app, contact us directly.
Was this helpful?
Yes. The C# SDK is built on webhooks and runs on the local network. Sale, void and refund are selected with the trans_type parameter.
Was this helpful?
Not currently. You can connect to the terminal from iOS using WebSocket over the local network IP.
The WLAN API reference explains the request and response payloads, and the debug resources show how to test the connection with a Chrome extension.
Was this helpful?
1.Send us the serial numbers of your development devices and we’ll push developer mode.
2.Follow the same-terminal integration guide and sample code.
3.When finished, upload the APK to TMS (Application → App List → Create App).
4.Push the app to the terminals (App List → Operation → More → Push App).
5.Create a payment App ID in PayPilot.
6.In PayPilot, open the merchant profile → Pay-apps and turn the app on.
Was this helpful?
CodePay manages processor encryption requirements for TSYS and Fiserv. Futurex is our key-injection partner and provides the HSM and remote injection.
1.Key acquisition. TSYS issues a unique PIN key per ISO: submit a KSI request form, and TSYS sends the encrypted key to Futurex. Fiserv uses one universal PIN key and sends it to Futurex; no form is needed.
2.Injection. CodePay authorizes Futurex to inject the right key into each device enrolled in TMS, directly into its secure hardware. The device confirms completion. CodePay never handles plaintext keys.
3.Verification. The device detail page in TMS shows key-injection status, and the Key Injection page supports batch RKI for large deployments.
Was this helpful?
Billing starts the month after a terminal’s first transaction. For example, if the first transaction is in February, the SaaS fee starts in March.
Was this helpful?
No. KYC, transaction monitoring and risk management are handled by the ISO, including merchant onboarding and submitting underwriting to the processor.
Was this helpful?
Within the payment app you can customize the app icon and UI theme color. The product name stays “CodePay Register”.
For device or system-level branding, contact sales to discuss options.
Was this helpful?
Still need help?
Our partner support team works directly with ISOs, FSPs and ISVs. Include your terminal serial number and MID so we can help faster.
