Every Business & CTE class holds a wide spread of readiness. Some students arrive knowing how a debit card clears; others have never held a checking account and freeze the moment you mention a chargeback. When you teach Payment Transactions and Payment Disruptions, that spread becomes an opportunity: the topic is naturally layered, from a simple cash exchange to a disputed wire transfer. This piece walks through how to tier the same lesson three ways so support, core, and extension learners all work on the real content, not a watered-down version of it.
Start from one shared anchor task
Differentiation collapses when every group gets a different worksheet and no one shares a conversation. Instead, open with one common scenario that every learner can enter: a student buys $60 sneakers online, the money leaves their account, and the package never arrives. Ask all three tiers the same opening question โ "Whose money is it right now, and who has to fix this?" โ then branch the depth from there. Everyone can talk about the sneakers; not everyone will reach the settlement timeline, and that is fine.
Concrete tiers: support, core, extension
Plan the same 45-minute block three ways. The verbs change, not the topic.
- Support: Give a labeled diagram of a card payment (cardholder, merchant, bank) and a sorting task โ match six everyday events to "money moves in" or "money moves out." Provide a word bank: debit, credit, authorize, decline, refund, dispute.
- Core: Students trace the full flow of one failed transaction on a blank flowchart and write two sentences explaining where the disruption happened and who is liable.
- Extension: Learners compare a chargeback with a direct refund, decide which the buyer should request, and justify it with a cost and a timeline โ then argue the merchant's side.
- All tiers: Close on the shared anchor so groups can hear each other's reasoning during the debrief.
Scaffolds that carry the weight
Support learners rarely need less content; they need the same content in smaller, visible steps. Sentence stems do the heavy lifting: "The payment failed because ______, so the ______ is responsible for ______." Keep a running word wall of transaction vocabulary and require students to point to it when they use a term. A partly completed flowchart โ three of seven boxes filled โ lets a struggling student focus on reasoning rather than blank-page paralysis. These same scaffolds transfer directly to your work on Consumer Protection and the Right of Withdrawal, where liability language reappears.
Challenge tasks that go deeper, not just faster
Fast finishers should not simply get "more problems." Give extension learners a genuine complication: a disputed transaction where both parties acted in good faith, or a case that turns on Capacity to Contract and Contract-Law Basics โ can a 15-year-old's online purchase even be enforced? Ask them to draft the email the consumer would send, then the merchant's reply. That forces them to hold two perspectives and use precise terms under pressure, which is exactly the kind of thinking a CTE program and Common Core reading-for-argument standards both reward.
Check that tiering worked
Before the bell, use a single exit ticket for the whole class with a self-select line: "I could explain today's payment problem to a friend โ independently / with the word bank / not yet." Pair that with one content question everyone answers. If your support group nails the content question but checks "with the word bank," the scaffold is doing its job and you can gradually remove it. If your extension group is coasting, raise the complication next lesson. Differentiation is not a seating chart; it is a set of moves you adjust every week.
Comments
No comments yet — be the first to share your thoughts!
Leave a comment
Comments are reviewed before being published.
Thanks for your comment!
Your comment is being reviewed and will appear here shortly.