01
Transaction & time limits
Caps per transaction and per window (e.g. $100/txn, $500/week) keyed to the participant’s program, not the whole card product.
Purpose-built controls
Ensure funds are used as intended.
Your Highnote card product sets the floor. Stretch adds the program layer so you can precisely define where, when, and how disbursed funds are spent — with granular controls at the participant level.
Custom controls
Five dimensions of spend control.
02
Merchant category blocking
Restrict by MCC when program intent requires — gambling, gaming, anything misaligned with the intended use of disbursed funds.
03
Specific-merchant allow/deny
Down to the single storefront. Useful when a program is partnered with a specific retailer or service provider.
04
Payment-protocol restrictions
Block cash-back requests, specific processing methods, or non-participant-initiated auths.
05
Terminal-type restrictions
Restrict use at ATMs and Automated Fuel Dispensers — e.g. fuel pump only, no ATM withdrawals.
Common questions
Frequently asked.
How does this relate to Highnote’s own card-product controls?+
Highnote’s controls are set at the card-product level. Stretch adds program-scoped controls on top so the same card product can back different disbursement programs with different rules.
Can you block access to cash?+
Yes — most commonly by blocking ATM withdrawals and denying any transaction that includes a cash-back request.
Can you block P2P apps like Zelle, Cash App, and Venmo?+
Yes. Blocking peer-to-peer payment apps helps keep disbursed funds aligned with program intent and protects participants from social-engineering scams.
Let's map your program controls.
Tell us what your participants should (and shouldn't) be able to spend on. We'll translate it into a controls profile on your Highnote card product.