The AceDraft for Teams Wallet: Top-ups and Paused Exports
Gowri Shanker·Sep 23, 2026
The wallet page carries one number and three controls, and the honest opening is that its worst state is one you cannot set from this page at all. Exports can be paused for your whole organisation, and the only thing here that lifts the pause is a completed top-up. I haven't watched it run. I read its code on 19 September 2026, and everything below is what the code says. The Top up button opens a live checkout, so I have never pressed it.
Key takeaways
- The balance is prepaid and shown in the wallet's own stored currency.
- Type your top-up amount in that currency. The small label beside the amount box names the wallet's currency, and the amount box had no such label until August 2026.
- Low balance appears only once you have saved a threshold above zero.
- Exports paused, top up to resume is a different state from a low balance, and it is set elsewhere.
- Limitation: Top up is real money through live checkout, so I read the code and stopped there. Nothing on this page was executed.
Prerequisites. An enterprise admin account with an organisation already created. Every route behind this page is admin-only, and an admin without an organisation gets an error telling them to create one first rather than an empty wallet.
What the balance card tells you
If you want one glance that says whether your students can export today, read the badges, not the number. The card shows the wallet's currency and balance, then up to two badges underneath.
Low balance is computed on the server and needs two things at once: a saved threshold greater than zero, and a balance below it. A threshold of zero switches the warning off entirely, which is why the save button now refuses a blank or negative value instead of quietly writing zero.
Exports paused, top up to resume reads exactly that, in red. It reflects an export lock on your organisation.
Type the amount in the wallet's own currency
Before you type anything into Add funds, look at the small currency label to the left of the box. That label is the wallet's billing currency, and the number you type is charged in it.
This sounds like pedantry until you see where it came from. In August 2026 a rupee per-export rate was subtracted from a dollar balance with nothing noticing, and the amount input had no currency label at all, so there was nothing on screen to catch it.
Two things came out of that. The export path now refuses to debit when the rate's currency and the wallet's currency disagree, which fails a student's export rather than overcharging you. And the suggested amount above the box changes shape: when the estimate is priced in the same currency as your wallet, it is a button you can click to fill the box, and when it is not, the same figure appears as plain text with a line telling you to enter an amount in your wallet's currency yourself.
Heads up. Top up opens a real payment. The credit applied afterwards is read back from the payment processor rather than from your browser, so editing the request on the way out gains you nothing.
When do exports pause?
An export lock is a flag on your organisation, and while it is on, every student export that would be charged to the wallet is refused before money moves. Free credits attached to a batch are checked first and are not affected by the lock.
Nothing an admin does on their own pages turns that flag on. It is set on our side, and a successful top-up clears it in the same database transaction that credits the balance. Hence the wording on the badge.
The student sees none of this. A blocked export returns a short message saying there was a temporary issue and the team has been notified, with no mention of wallets or balances. The email that reaches you as the admin carries the actual reason, and that one has no cooldown, so every blocked export sends one.
Low-balance reminders, and exactly when the email is sent
The sentence above the threshold box reads: "We never charge your card automatically. When the balance drops below this threshold, we'll email your admin a reminder to top up, and show a reminder in the app."
I went looking for code that contradicts the first half and found none. There is no saved card and no off-session charge anywhere in the wallet module. The ledger declares an automatic-recharge entry type that no code path writes today.
The second half is true with a narrower trigger than you might read into it. The reminder email is sent when a student's export is charged to the wallet and that charge leaves the balance below your threshold. It is limited to one per organisation per day, and that limit is held in memory, so a backend restart lets the next qualifying export send another.
A second email works differently. A daily scan looks for organisations sitting at zero or below and emails the admin every three days until the balance moves. That cadence is stored in the database, so it survives a restart, and a top-up resets it.
The in-app half of the promise is real too. A low or zero balance raises a banner across the enterprise area, not only here.
Author's take. The gap I would fix first sits between those two triggers. If your balance drifts down to your threshold and then nobody exports anything, no email is sent, because only an export charge can fire it. So set the threshold high enough that an ordinary week of exports crosses it while there is still room, rather than treating it as a last warning.
Who this page is for
Use it once you have students exporting and a balance worth watching. Skip it on day one, when there is no usage to react to and any threshold you set is a guess, and open the usage calculator at /enterprise/wallet/calculator instead. Come back here when it has given you a number worth funding.
Related pages
Comments
No comments yet. Be the first to comment.