If one person can expense it, use the normal checkout and stop reading — this page exists for the case where your finance process cannot put a card through for software at all. That is a surprisingly common wall, and it is not a size-of-company problem. It stops studios, schools, councils and post houses buying things that cost less than a microphone cable.
- Can't use a card? Email hi@aidxn.com. This path exists and has been used.
- Send four things: billing entity, billing address, any PO or vendor reference, and the mailbox the key should go to.
- The licence can go somewhere other than the payer — procurement pays, the department uses it.
- No separate enterprise build. Same download, no admin rights, no kernel extension.
The wall, and why it is not about money
An $89 one-time purchase is below the threshold where most procurement teams even want to be involved. The problem is rarely the amount. It is that the organisation has a process which assumes a vendor relationship — an entity on file, an invoice with a reference on it, payment by transfer — and a Stripe checkout page does not produce any of those.
So the engineer who wants the tool hits a wall that has nothing to do with whether the tool is worth having. In practice they either pay personally and never claim it back, or they give up. Both are bad outcomes, and the second one is invisible to us.
What actually happened in November 2026
A major game studio's sound department wanted a licence. Their finance process could not pay by card. Rather than the engineer putting it on a personal card, the order came through the studio's external procurement agent: the agent purchased on the studio's behalf, and the licence was then issued directly to the studio's own sound-department mailbox rather than left sitting with the agent.
That is worth stating plainly for two reasons. First, because it is the honest version of "used by professionals" — a sound department bought a licence through a purchasing agent, which is a real signal about how it is being used but is not an endorsement and should not be read as one. Second, because the only reason it happened is that somebody asked instead of giving up.
What to put in the first email
Four things, and sending them together removes the round trip that makes this slow everywhere else:
- The legal billing entity. The name your finance team expects on paperwork, which is often not the name on the studio door.
- The billing address. Including any tax identifier your side needs shown.
- Any PO or vendor reference. If your system will not pay an invoice without a reference quoted on it, say the reference and we will quote it.
- Where the licence key should be delivered. Name the mailbox. See below for why this one matters more than it looks.
Send the key to the people who will use it
The address that pays is usually not the address that uses the software. If the key is issued to a purchasing inbox, it has to be found and forwarded by somebody with no stake in it, and six months later — when a machine is replaced and the key is needed again — nobody in the department knows where it went.
Naming a department mailbox rather than an individual is the version that survives staff turnover. It costs nothing to specify at order time and is the single most common avoidable problem with company software purchases.
What IT will ask, answered in advance
These are the questions that actually hold up an install, so here they are up front:
- Is there a separate build? No. The same download everyone else uses. Nothing to repackage.
- Does it need admin rights? No, which is why it works on locked-down machines. The install overview covers each platform.
- Kernel extensions or drivers? None. It creates a virtual MIDI port through the operating system's own API — CoreMIDI, WinMM, ALSA.
- Does it need an internet connection? Not to run. Licences verify offline.
- What leaves the machine? Crash reports, on by default with a switch in Settings → Privacy. Usage telemetry is off by default. Mappings, presets and project data are never sent anywhere.
Deploying to more than one machine
A single engineer on a single workstation is the simple case. A studio putting it on several machines, or a school running a lab, is not — and it is better handled on the order than discovered afterwards. Say how many machines it needs to run on in the first email.
For classroom-scale deployments specifically, the 30-student gamepad lab write-up covers the room layout, the shared mapping preset and the per-seat budget in detail. That is a different problem from procurement and has its own page.
Before you involve finance at all
Try it first. The free tier bridges a controller to MIDI over USB and shows every input live, which is enough to confirm your controllers are detected and that real MIDI reaches your host — on your actual machines, in your actual room, before anybody fills in a form.
A procurement process is a lot of effort to spend on something that turns out not to fit the workflow. Prove it works, then buy it. If you want to compare it against the alternatives first, the software comparison is the honest version.
FAQ
Can I buy Universal Controller MIDI without a credit card?
Yes. Email hi@aidxn.com with your billing entity and the address the licence should go to. A studio sound department did exactly this in November 2026 — their finance process could not pay by card, so the purchase came through their procurement agent and the licence was issued directly to the studio mailbox.
Do you accept purchase orders?
Email hi@aidxn.com with the PO reference and billing entity and it will be quoted on the paperwork. We are a small vendor, so this is handled per order rather than through a self-serve portal — which in practice means it is answered by a person the same day rather than queued.
Can the licence go to a different address than the one that paid?
Yes, and for company purchases it usually should. Procurement pays, the sound department uses it. Name the destination mailbox when you order and the key is issued there rather than forwarded.
Is there a separate enterprise or site build?
No. Everyone installs the same download from the downloads page. There is no repackaged installer, no kernel extension and no admin rights needed, which is the main thing IT asks about.
Does the app phone home or need an internet connection to run?
Licences verify offline, so the app does not need a connection to check your key. Crash reporting is on by default with a switch in Settings, Privacy, and usage telemetry is off by default. Nothing about your mappings or projects is sent anywhere.
What do you need from me to get started?
Four things: the legal billing entity, the billing address, any PO or vendor reference to quote, and the mailbox the licence key should be delivered to. Send those in one email and there is usually nothing further to ask.