A student calls with a receipt, but your team can’t find them on the class roster. They’re worried about their payment. Your staff is wondering whether the registration failed, a document is missing or the student selected a different class.
Before asking them to register and pay again, separate two questions: what happened to the payment, and what happened to the enrollment? Investigating both prevents a confusing situation from becoming a duplicate charge.
1. Confirm which transaction you’re looking at
Ask for the student’s name, registration email, class, payment date and transaction reference. A receipt can help locate the transaction, but don’t request a full card number or security code by email.
Check the payment provider’s actual transaction record. A pending payment, an authorization and a completed payment aren’t interchangeable. Stripe’s documentation, for example, distinguishes processing from successful payment states. Other providers use their own labels.
If a payment is still processing, follow that provider’s guidance before collecting again. A bank screenshot by itself may show a temporary hold rather than a completed charge.
2. Find the matching student and class
Search for an existing record before creating another. Check alternate email addresses, spelling differences, duplicate profiles and the class date or location selected.
Then identify the missing step. Is the registration form incomplete? Does the school need a prerequisite document? Is a staff approval outstanding? Did the payment get associated with the wrong enrollment?
Payment verification should not bypass required eligibility checks. Keep those decisions separate and tell the student exactly what remains.
3. Give one person ownership of the resolution
Assign a staff member to reconcile the payment and enrollment records. Record the transaction reference, the confirmed status, the missing item and the next action.
Avoid having admissions ask for another payment while accounting investigates the first one. A short shared note can prevent contradictory instructions.
If the records disagree, preserve the original information and escalate the issue. Don’t delete the receipt or mark a payment complete simply to make the screens match.
4. Send a specific update
A useful message might say: “We located your payment for the Saturday class. Your registration still needs the prerequisite document. Please submit it through the school’s approved channel so we can finish reviewing your enrollment.”
Only say the payment was received after verifying it. If you’re still investigating, explain that and give a realistic time for your next update.
Once the issue is resolved, send the class confirmation and check that the student knows where to go, when to arrive and how to get help.
A small exception log can prevent repeat problems
For each case, record the cause and how it was resolved. After several cases, look for patterns: unclear confirmation messages, duplicate profiles, missing prerequisites or a recurring payment-status mismatch.
Improve the step causing the problem rather than asking staff to memorize another workaround.
Where Steams Online can help
Steams brings class registration, student records and payment information into the same platform. Its registration fields and prerequisite options help schools define what they need, while its payment options accommodate payment in full, installments, deposits and pay later.
Those tools support the investigation, but staff should still confirm the actual payment status with the connected provider when something doesn’t match. A school’s enrollment requirements also remain its responsibility.
Start with one practical check: can your team explain whether a student is financially confirmed, administratively complete and ready for class without confusing those three states?
Source and further reading
Stripe: How Payment Intents and Setup Intents work. Consult your own processor for its payment-status definitions and resolution steps. Research checked October 7, 2026.
