360TravelSIM - eSIM Sales, Client and Reseller Platform
A connected eSIM commerce ecosystem with three Next.js applications, a Golang API, online payments and integrations with an eSIM supplier and ERP.
Project overview
360TravelSIM - eSIM Sales, Client and Reseller Platform
A connected eSIM commerce ecosystem with three Next.js applications, a Golang API, online payments and integrations with an eSIM supplier and ERP.
360TravelSIM was built as more than a sales website. The solution combined a public eSIM storefront, separate customer and reseller portals, a Golang integration layer, supplier fulfilment, Stripe payments and ERP-connected operational workflows. The commercial program is no longer active, although the public sales website remains online.
Next.js eSIM sales frontend
Next.js client portal
Next.js reseller and affiliate portal
Golang REST API
eSIM supplier API and ERP integrations
Stripe payments and affiliate workflows
Three Next.js applications, one integration core
A complete eSIM order lifecycle across sales, self-service and resellers
Each audience received a focused interface while the Golang API kept products, orders, fulfilment, payments and ERP records connected.
Integration core
Golang REST API
Products · orders · payments · fulfilment
Next.js eSIM storefront
The public frontend presented destinations and data bundles, supported search-friendly product discovery and guided travellers into the online purchase flow.
- Country and bundle discovery
- Conversion-focused purchase paths
- Stripe online payment entry points
Next.js client portal
Customers used a dedicated application for their account, orders and purchased eSIM services rather than relying on the public storefront for post-sale support.
- Account and order access
- Purchased eSIM service context
- Separated authenticated customer workflows
Next.js reseller portal
A separate reseller and affiliate application supported partner registration, attributed sales and commission-oriented workflows.
- Reseller and affiliate accounts
- Partner sales attribution
- Commission-oriented programme workflows
Supplier API, ERP and Stripe
The Golang backend connected the web applications with the external eSIM supplier, online payments and internal ERP records.
- External eSIM catalogue and fulfilment integration
- Stripe payment status and order handling
- ERP-connected sales and operational records
Connected commercial workflow
From destination search to fulfilment and partner attribution
The platform kept the customer purchase, supplier integration, back-office record and reseller context within one traceable flow.
Discover
A traveller selected a destination and matching eSIM bundle in the public Next.js storefront.
Pay
Stripe handled online payment while the platform preserved the order and customer context.
Fulfil
The Go API exchanged product and order data with the external eSIM supplier and customer portal.
Operate
ERP records and reseller attribution connected sales, service delivery and affiliate workflows.
Built as an operating platform, not a standalone storefront
The project separated public sales, customer self-service and reseller work into dedicated Next.js applications, with Golang coordinating the commercial and telecom integrations behind them.
360TravelSIM product surfaces
These screenshots were captured from the live public website and portal login pages. The commercial eSIM and reseller programme is no longer active, but these interfaces remain online as a record of the delivered system.
The public sales frontend introduces the global eSIM offer and starts product discovery from a destination selector.
The affiliate page directed partners into the separate reseller registration and login flows.
A separate client portal provided the authenticated post-sale entry point for customer accounts and eSIM services.
The reseller portal separated partner and affiliate workflows from the customer-facing application.
360TravelSIM
Project context and live links
Brief
360TravelSIM was built as more than a sales website. The solution combined a public eSIM storefront, separate customer and reseller portals, a Golang integration layer, supplier fulfilment, Stripe payments and ERP-connected operational workflows. The commercial program is no longer active, although the public sales website remains online.
Result
One system connected eSIM discovery and checkout with customer self-service, reseller sales, supplier fulfilment, payments and ERP operations.
Project links
Challenge
Keep the external supplier catalogue, eSIM order state and ERP records aligned across the sales and post-sale journey.
Serve public buyers, existing customers and resellers through separate applications without fragmenting the underlying business logic.
Connect Stripe payments and affiliate attribution with orders, fulfilment and operational records.
Approach
Delivered three focused Next.js applications: the public eSIM storefront, customer portal and reseller portal.
Centralised authentication, products, orders and integration workflows in a Golang REST API connected to the eSIM supplier and ERP.
Implemented Stripe payments together with partner registration, sales attribution and affiliate programme workflows.
Outcomes
An end-to-end sales path connected product discovery, online payment, supplier fulfilment and customer self-service.
Customers and resellers received dedicated portals tailored to their roles instead of sharing one overloaded interface.
The live public surfaces remain an online record of the delivered platform even though the commercial programme has ended.
Project links
Result
One system connected eSIM discovery and checkout with customer self-service, reseller sales, supplier fulfilment, payments and ERP operations.
Have a similar project?
We can help shape the technical plan, build the product, and support it after launch.
Let's talk