[Wallee] Improve payment onboarding experience

Our client base consists of Swiss asset managers and law firms, among others. These are companies where compliance officers have heart palpitations if data crosses the Atlantic. Naturally, we spent months architecting a sovereign European tech stack. We host in the EU and Switzerland, we use local service providers, and we minimize US dependencies. When it came to payments, we applied the same logic. We wanted a Swiss or EU-based alternative to the US giants. After evaluating Payrexx, Datatrans, and others, we settled on Wallee. On paper, it looked perfect: Swiss-origin, strong API documentation, very competitive pricing, and data locality guarantees. But then the nightmare started. **A "Paper Forms" Reality Check** The difference between "Digital Switzerland" marketing and reality is stark. While our tech stack uses Next.js and serverless edge functions, our payment onboarding experience with Wallee felt like stepping back into 1995. \* Application: We filled out a digital web form. Standard stuff. \* A Data Black Hole: They seemingly lost the data. We entered a loop of email ping-pong with support. Paperwork: We were asked to print out physical forms, sign them, and scan them back. For a digital SaaS product. \* After wasting a week jumping through hoops, we finally received a generic rejection letter. The reason? "Internal acceptance policy regarding your industry." How about telling us that right at the start of the onboarding process? \> "After careful review, we regret to inform you that we are unable to consider your request at this time. Our internal acceptance policy excludes cooperation with companies operating in your field/industry. Please note that this decision is final and no further explanation can be provided." (...) Your Wallee Team Apparently, a standard B2B SaaS platform generating slides is considered "too high risk" for the traditional Swiss acquiring banks that underwrite local payment gateways. **Stripe's Experience: Live in 24 Hours** Out of options and out of patience, we grudgingly turned to the US giant: Stripe. The contrast was humiliating for the European tech ecosystem. \* SaaS-First: From the very first screen, Stripe made it clear that software companies are their core demographic. We didn't have to explain what a "subscription" is. \* Zero Wait Time: The onboarding was fully automated. No humans, no paper forms, no scans. \* Speed: We integrated the API, ran our tests, and were processing live payments within 1 day. Stripe even solves the complex VAT compliance for B2C startups out of the box, acting as the Merchant of Record for tax collection in different constituencies. While we are B2B focused, seeing that level of "legal-as-a-service" built into the platform is impressive. **Technical Gap: Environments** Beyond the bureaucracy, there was a glaring UX gap in the European alternative. In Wallee, "Test" and "Live" environments are treated as completely separate silos. There is no way to copy settings between them. We had to manually click through every webhook configuration and processor setting twice, hoping we didn't make a typo in production. In Stripe, you flip a toggle when creating the live environment - that's it. Later, you can also easily copy e.g. new products you're testing from sandbox to live. **The One Thing Wallee Did Better** To be fair, there was one technical aspect where the Swiss approach felt more transparent. In Wallee, enforcing a specific billing address (crucial for VAT logic) via API was straightforward. Stripe makes this surprisingly difficult. They seemingly obscure the ability to "lock" a billing address pre-checkout, likely to upsell you to their automated Stripe Tax product (which adds 0.5% per transaction on top of Stripe's already hefty fees). We managed to architect around this to enforce our tax rules without the extra fee, but it felt like the only part of the Stripe experience that was "hostile" by design. **Conclusion** We are now live on Stripe. Our payments work, our subscriptions renew, and our team can focus on shipping features rather than scanning paper forms. It hurts to admit this. We want to support the European ecosystem. We want to pay Swiss fees to Swiss companies. But until European fintechs stop treating modern SaaS startups like high-risk liabilities and start building developer-first experiences, US tech giants will continue to eat the market. For other Swiss founders: Fight for sovereignty where you can (hosting, data storage), but don't let ideology kill your launch velocity. Sometimes, you just have to use the tool that actually works. Originally posted on: https://octigen.com/blog/posts/2026-03-09-payment-nightmare/