Tuition paid during a visit
Describe how staff currently identify the student’s charge and record a payment collected on site. Ask which parts of that workflow can be supported.
Discuss how a terminal should fit your reception and billing workflow. Confirm availability, integration scope and terms before choosing a solution.
A conversation about payment terminals should start with the institution’s real reception process. Which fees are collected on site? Who accepts the payment? How does the team identify the student and confirm which charge has been settled? Those questions matter before choosing hardware or promising an integration.
This Eduwallet service page helps you prepare the requirements for an in-person payment arrangement. Terminal availability, supported integrations, institution onboarding and commercial terms need direct confirmation with the team. Do not assume that creating an Eduwallet account automatically orders a terminal or activates a connection between a device and student billing.
Ask the team about terminal availability, institution onboarding, supported integrations and commercial terms. Confirm the arrangement appropriate for the way your organization takes in-person payments.
Describe how staff currently identify the student’s charge and record a payment collected on site. Ask which parts of that workflow can be supported.
Prepare examples of occasional charges so the team can assess the required payment and reconciliation process.
Agree who verifies payments and how the next shift can understand the billing status. Confirm available capabilities rather than inferring multi-device or multi-site support.
Describe the fees collected on site, staff responsibilities and how the student or payer is identified.
Ask what data can be connected and how a payment should be matched to a receivable. Do not assume automatic synchronization.
Confirm availability, provider requirements, device costs and settlement terms for the proposed arrangement.
Decide who checks disputed or unmatched transactions and how staff document the outcome.
Prepare real examples of tuition and other charges collected at reception.
Explain the institution’s process and ask about current terminal availability and compatibility.
Agree the supported workflow, onboarding requirements and commercial conditions before committing.
Define how payments are checked and how exceptions are handled for the confirmed arrangement.
Plan reception payments around the way dancers actually settle fees on site.
Define what reception needs when a student pays for a course in person.
Discuss an on-site payment process that fits the club’s front-desk responsibilities.
Prepare a clear school-office workflow before deciding on a payment terminal.
Assess on-site payment requirements against your academy’s actual reception process.
Accepting a card payment and maintaining a student receivable are separate parts of the process. A suitable arrangement must explain how they relate, which records staff review and what happens when a payment cannot immediately be matched. Ask for a demonstration of the specific workflow you need.
Keep hardware selection separate from assumptions about the software. Supported devices, payment methods, connectivity, delivery, onboarding and costs must be confirmed for the actual proposal. This page does not publish unverified device specifications, prices or implementation dates.
This page is a starting point for discussing your institution’s requirements. Confirm current availability, the ordering process and commercial terms with the team. Creating an Eduwallet account should not be treated as automatically placing a hardware order or activating a terminal service.
Do not assume automatic matching or synchronization. Explain how your institution identifies students and charges, then ask which integration workflow is actually supported. Any proposed connection between a terminal transaction and a student receivable needs explicit confirmation.
Supported devices and methods depend on the actual provider and proposed arrangement. Ask the team for the current options appropriate to your reception process. This page does not present an unverified compatibility list or guarantee support for a particular model.
Ask about device charges, transaction terms, onboarding requirements and how funds are settled for the actual proposal. Compare those details with your institution’s collection process before deciding. No universal pricing or settlement schedule is promised here.
Describe the charges collected at reception, the staff involved and how transactions are currently checked against student balances. Bring a typical payment example and a difficult exception. These details make it easier to confirm whether the proposed workflow fits your institution.
Consider on-site and online collection as parts of the institution’s overall billing arrangement. Confirm the actual available setup and responsibilities for each route. Do not infer that every terminal proposal includes a unified integration with all online payment methods.
Contact the team to confirm current terminal availability, supported integrations and terms for your institution before choosing an in-person payment solution.