Using the Dashboard
Summary
Stores
Stores Tab Overview
Stores > Status
Stores > Technical
Stores > General
Web Based Store Inventory / Online Menu
Download a Pick List for easy restocking
Stores > Restock
How To Set Pars
Sales Tax
What is a KID?
Stores > Discounts
Stores > Financial
Products
Export Lots as CSV
Products > Transactions
Delete/Undelete (or Archiving) a Product
How to repurpose tags
How to Bulk Import Products
Products Overview
Products > Tag Orders
Export EPC Inventory
Products > Inventory
Add a Product
Products > Details
Tags
Transactions
Understanding Transaction Preauthorization and Processing Times
Transaction status definitions
Transactions > Logs
Coupon Reporting
Transactions > Customer Emails
Edit the default preauthorization amount
How to adjust a transaction or process a refund
How to View Transactions & Transactions Overview
How to Export Transactions for Enhanced Sales Analysis
How to prevent mischarges
Feedback
Discounts
Discounts > Add a Happy Hour Discount
Discounts > Add a Standard Discount
Discounts Overview
Discounts > Creating Coupons
Discounts > Add a Shelf Life Discount
How to redeem a coupon
How to end a Discount
Financials
Settings
Getting Started
Remittances
Transactions included in a remittance
Remittance Processing Schedule
How do I provide my banking information?
Ordering Tags
Restocking Product
Setting Up Your New Store
How to restock a Byte store
Setting up your store to be NAMA-certified
Custom graphics install instructions
Branding your store
Setting up your Byte Technology store
How soon will I receive my store?
Standard Byte Store Specs
Tagging Best Practices
Tagging Frozen Food
Tagging drinks
Tagging Non-Perishable Products
Product tagging best practices
Tagging sandwiches, wraps, and burritos
Tagging snacks or soft packaging
Tagging soups or yogurts
Tagging salads & hard packaging
Are RFID tags microwave safe?
Merchandising best practices
Test and verify inventory
Tagging heatable entrees
Tagging aluminum cans and foil-lined products
Dashboard Onboarding | A self-guided training
1. Introduction to Byte Technology Dashboard
2. Overview of Summary Page + Navigation Bar
3. Stores Section Overview
4. Products Section Overview
5. Transactions Section Overview
6. Feedback
7. Discounts Section Overview
8. Financials Section
9. Settings
10. Congratulations
Campus Card Stores
Campus Cards FAQs
What Happens When a Customer Has Insufficient Card Funds?
Understanding Campus Cards
Byte Store Dimensions/Store Types
Troubleshooting & FAQs
Connectivity
How to Install an OptConnect Cellular Device on a Byte Store
Ethernet setup and networking requirements
Transactions made while store is offline
How do I get a store back online?
Code 400C
Code 600
Code C
Code E
No IP / Red or Yellow Border
Code 200
Sending Remote Commands
Screen Issues
Store Temperature
🧊 Why Your Dashboard May Show a Higher Temperature or “Too Warm” Status
Adjusting the store temperature
Inventory
Antennas in the Byte Store - Where to Place Your Products
Customer Inquiry: Need Help With Your Transaction?
Code 400
Door Lock Issues
Open a CSV file in Excel or Google Sheets
How to Reach Support
Combatting Theft With Your Byte Store
Error Codes: Out of Service Troubleshooting Guide
Internal Troubleshooting
- All Categories
- Getting Started
- Campus Card Stores
- What Happens When a Customer Has Insufficient Card Funds?
What Happens When a Customer Has Insufficient Card Funds?
Updated
by Carolina Villatoro
Campus card/Payroll Deduct transactions work differently than traditional credit card payments. This article explains what happens when a student has limited or insufficient funds on their campus card and how Byte kiosks handle these scenarios.
Short Answer
A student/employee must have sufficient funds available on their card at the time of purchase to successfully complete a transaction.
Byte kiosks perform a balance check (preauthorization) before unlocking the door, but the final transaction amount is determined after the student selects items and closes the door. Then, the transaction will complete the processing cycle, which can take around 1-2 hours.
If the final purchase exceeds the student’s available balance, the transaction may be declined.
How Campus Card/Payroll Deduct Transactions Work
When a student/employee uses a card at a Byte kiosk, the following steps occur:
- Card Tap/Swipe
The customer presents their card (tap, swipe, or scan depending on the reader type). - Balance Check (Preauthorization)
The kiosk checks whether the card has at least the configured minimum/preauthorization amount available. - Door Unlocks
If the balance meets the preauthorization requirement, the door unlocks and the customer may select items. - Item Selection
The customer removes products from the kiosk. - Transaction Processing
After the door closes, the final transaction total is sent to the campus card provider (e.g., Transact or CBORD) for processing.
This processing cycle can take approximately 1–2 hours to fully complete.
What Happens if Funds Are Insufficient?
Scenario 1: Customer Has Enough Funds to Pass Preauthorization
- The door unlocks.
- If the student selects items within their available balance, the transaction completes successfully.
- If the student selects items exceeding their available balance, the transaction may be declined.
In most cases:
- The card payment provider returns a failed transaction
- No funds are collected from the cardholder
Note: Some campus card systems may be configured to automatically collect the remaining available balance after a failed transaction, but this behavior is campus-specific and not enabled by default. Byte does not control this configuration.
Scenario 2: Customer Does Not Have Enough Funds to Pass Preauthorization
- The door does not unlock.
- The student is prompted to use another payment method (if available).
Important Notes
- Byte kiosks do not allow negative balances.
- Negative balances (credit accounts) may be supported only if explicitly enabled by the campus card provider.
- Partial charges are not applied by Byte.
- Final transaction approval, declines, and balance enforcement are determined by the campus card provider, not Byte.
Multiple Plans or Tenders (Dining Dollars, Flex, Meal Plans)
If a student card supports multiple tenders:
- The campus card system checks balances in a predefined order set by the institution.
- The system attempts the charge against the first tender with a non-zero balance.
- If that tender lacks sufficient funds, the transaction may be denied — even if another tender later in the order has enough balance.
Because of this, proper tender priority configuration is important to avoid unnecessary declines.
Why Preauthorization Amount Matters
The preauthorization amount helps reduce declined transactions.
Best practice: Set the preauthorization amount close to the highest-priced item in the store.
This helps ensure customers have enough funds to complete a typical purchase once the door unlocks.
Does Byte Control Balance Rules?
No. Balance checks, tender priority, approvals, declines, partial collection behavior, and negative balance rules are all controlled by the campus card provider (such as CBORD, Transact, etc).
Byte kiosks follow the responses and rules enforced by the campus card system.
Key Takeaways
- Students must have sufficient funds to complete a purchase.
- Passing preauthorization does not guarantee final approval if additional items are taken.
- Declined transactions typically do not result in charges.
- Campus card configuration (preauthorization amount, tender order, negative balance rules) plays a major role in transaction outcomes.