Why we switched studio billing to Wise.
Stripe is excellent for product. It's not the right tool for studio invoices that span four currencies.
Until early this year, Amalbryx invoiced through Stripe. It worked, mostly. We're switching to Wise. Here's the boring, real reason.
The currency math
We invoice in USD, EUR, GBP, and occasionally AED. Clients pay from whatever account they have. The studio has bank accounts in EUR (Albania) and GBP (UK).
On Stripe: every cross-currency payout incurred a 2.9% conversion fee, and the FX rate was Stripe's mid-market plus a markup. On a $25k engagement, that's ~$725 of friction.
On Wise: the FX rate is interbank mid-market, and the per-transfer fee is fixed (typically £4–10). On the same engagement, the FX cost is closer to $40–60.
The dashboard math
Stripe's dashboard is built for product. Recurring revenue. Subscription churn. Disputes. None of which a five-figure project invoice needs.
Wise gives us multi-currency balances on one dashboard. We can hold EUR until the EUR/USD rate is favorable. Or convert immediately when the math is fine. Either way, we see the numbers without filtering through 'Stripe Atlas Connect Express Standard' product surfaces.
What we lost
Stripe Checkout. We had a clean two-click 'pay this invoice' surface. Wise's payment-request links are functional but less pretty.
Webhooks for accounting. Stripe pushes events; Wise has a public API but the webhook story is thinner. We rebuilt the bookkeeping reconciliation script.
Worth it? At our volume, absolutely. At a higher monthly transaction count, maybe not.
What we kept
Stripe still handles client product checkout — Alemiin, Juhaynh, Termka all run Stripe in production for their end-customer flow. Stripe is excellent there. It just isn't the right tool for invoicing a studio engagement.
"Use the tool that's built for the job. Stripe for product. Wise for studio invoicing. Don't pay Stripe's conversion margins on what isn't a product transaction."