42% of consumers still prefer receiving paper bills, especially when dealing with financial or legal matters.

In today’s digital-first world, email might be king, but when it comes to compliance, trust, or reaching customers who aren't online, snail mail still rules.

Challenge that might surprise some: the need to send paper invoices and reminders by post, not just email.

Solution? We integrated Pingen, a Swiss-based postal API service that lets digital platforms send real, physical letters automatically. Just like sending an email—but with a stamp.

Digital system triggering paper mail delivery.

Have you ever had to bridge digital and physical worlds in your product?

We’ve learned a lot building payment infrastructure in a regulated market like Switzerland.

In 2020, while working on the BNPL product Paidle, we were required to implement BVR payment slips - a legacy format that was still standard at the time.

We didn’t stop at compliance.
We made the experience efficient for the end user, enabling BVR scanning and real-time API-based payment confirmation from Credit Suisse. No delays. No reconciliation issues.

When the Swiss market moved to QR-bills in 2022, we were already ready.
Our platform supported both formats, and we ensured our clients transitioned without disruption, ahead of the regulatory deadline.

Now we’re addressing the next challenge:
How to offer structured billing without requiring users to scan, click, or enter details manually.

We’re currently working on the integration of eBill, allowing users to:

• Receive digital payment requests directly in their e-banking portal
• Schedule payments for any time they prefer

Have you ever had to migrate data from one platform to another?

We recently got such a request while moving from the widely used Transportation Management System, Sylectus, to a custom-built solution.

The initial estimation?

• 6 weeks
• A team of 3 people
• Manually copy-pasting every vehicle and all related data

Instead, I spent a weekend building a Python-based Scrapy crawler that automated the entire process.

• No more repetitive manual work
• Thousands saved in effort and cost
• And here’s the bonus: we could now recreate the database on demand using real-world data, which was incredibly helpful for testing the new system under realistic conditions.

This kind of automation doesn't just save time—it makes your dev and QA process smoother and far more efficient.

Check out the sample code on GitHub

If you're planning a similar migration, feel free to try it out—and skip the pain of copy-pasting.

Ever wondered what a real mobile message to Orange, Vodafone, or O2 looks like under the hood?

0000003F00000004000000000000000100010153656E64657249440001013338

336313237363530350000000100000000000D48656C6C6F20416E6472697921

This line is what actually travels over the wire when you integrate with mobile operators using SMPP (Short Message Peer-to-Peer protocol).

Implementing SMPP in Java was one of the first challenging yet exciting tasks we tackled while building a new platform for

Echovox, more than 12 years ago. It's a hidden engine behind every "ping" and "buzz" you get from businesses worldwide.

Back then, mastering SMPP felt like unlocking a secret language of the telecom world — and it still powers the mobile messaging ecosystem today.