Walletium DigitalWalletdocumentation.

A complete overview of Walletium — a cutting-edge digital mobile wallet solution that lets you add, send, withdraw, and exchange money seamlessly within a secure and intuitive platform.

Step 01

Welcome to Walletium

Walletium is a cutting-edge digital mobile wallet solution designed to revolutionize how you manage your finances. With a comprehensive suite of features, Walletium empowers users to add, send, withdraw, and exchange money seamlessly, all within a secure and intuitive platform.

Core features of Walletium

Add Money

Easily add funds to your wallet using both automatic and manual payment methods for seamless transactions.

Send Money

Conduct peer-to-peer transactions effortlessly between registered users with instant money transfers.

Withdraw Money

Enjoy hassle-free payouts via manual gateways, accessing your funds whenever and wherever you need them.

Multi-Currency Support

Manage funds in your preferred currency with ease and embrace global financial freedom with Walletium.

Money Exchange

Seamlessly exchange money between different wallet balances for optimal flexibility and convenience.

Request Money

Easily send money requests to streamline your payment collection process — no more chasing payments.

Voucher System

Utilize vouchers for adding funds to your wallet — a convenient and secure payment method for users.

Developer API

Integrate Walletium with other business applications to accept payments effortlessly and expand capabilities.

Admin Role Management

Empower administrators with robust role management for secure and efficient oversight of the platform.

Step 02

Before You Start

You do not need to be a coding expert to run this template. Just make sure the following free software is installed on your computer.

No coding experience required

Every command in this guide is copy-paste ready — you do not need to write any code from scratch.

Required Software

SoftwareWhy You Need ItDownload Link
VS CodeFree code editor used to view and modify filesDownload →
Node.js (LTS)JavaScript runtime required to run the project locallyDownload →
Google ChromeRecommended browser to preview your websiteDownload →

Important: choose the LTS version

When installing Node.js, always select the LTS (Long Term Support) version. It is the stable and recommended option.

Step 03

fileName

Project Folder Overview

After extracting the ZIP file you downloaded, you will see the following folder structure. Understanding what each folder contains makes customization much easier.

Project Structure
walletium-next
├── messages/            # site languages static data (en, ar, es, hi, fr)
├── public/              # images, logo, favicon, static files
├── designs/             # design references / extracted templates
├── src/                 # main source code
│   ├── app/             # website pages (App Router)
│   │   ├── [locale]/    # locale-prefixed routes (landing + dashboard)
│   │   └── api/         # route handlers
│   ├── components/      # reusable sections/components
│   │   ├── layout/      # navbar, footer, shells
│   │   ├── sections/    # landing page sections
│   │   ├── partials/    # small shared widgets
│   │   ├── ui/          # base UI + form fields
│   │   ├── charts/      # chart components
│   │   ├── providers/   # context/provider wrappers
│   │   └── integrations/# third-party integrations
│   ├── redux/           # Redux store, slices, RTK Query apis
│   │   ├── api/         # RTK Query endpoint modules
│   │   ├── features/    # slices (auth, etc.)
│   │   └── store.js     # store config + persist
│   ├── lib/             # axios, token, toast, auth helpers
│   │   └── api/         # endpoints + fetchers
│   ├── utils/           # error/success extract, image url, formatters
│   ├── contexts/        # theme, auth, dashboard providers
│   ├── hooks/           # reusable hook functions
│   ├── i18n/            # next-intl routing, request, navigation
│   ├── config/          # env export root
│   ├── data/            # static content (faq, terms, testimonials)
│   └── middleware.js    # locale + auth middleware
├── package.json         # project dependencies info
├── next.config.mjs      # Next.js settings
├── .env                 # API URL configuration
└── jsconfig.json        # path alias (@/ -> src/)

Important folders explained

Folder / FilePurpose
messages/Site language static data (en, ar, es, hi, fr)
public/Holds all images, logo, favicon, and static assets
src/Main source code — most customization happens here
src/app/Website pages via the App Router ([locale] routes + api)
src/components/Reusable sections, layout, UI, charts, and providers
src/redux/Redux store, slices, and RTK Query API modules
src/lib/Axios, token, toast, and auth helpers
src/data/Static content like FAQ, terms, and testimonials
.envAdmin panel API URL configuration (very important)

Step 04

Opening Project in VS Code

Follow these steps to open the downloaded project inside VS Code.

  • 01

    Extract the downloaded ZIP file to a location like Desktop.

  • 02

    Open the VS Code application.

  • 03

    From the top menu, click File → Open Folder.

  • 04

    Select the extracted walletium-next-template folder.

  • 05

    Click the “Open” button to load the project.

Pro tip

Once the project is loaded, you will see the folder tree on the left sidebar. Click any file to open it in the editor.

Step 05

Install Project Dependencies

Before you can run the project, you need to install the required packages. This only needs to be done once.

Open the terminal

In VS Code, click Terminal → New Terminal from the top menu. A terminal window will open at the bottom.

Run the install command

Paste the following command into the terminal and press Enter:

Terminal
npm install

This may take a few minutes

Depending on your internet speed, the install process can take 2 to 5 minutes. You will see a lot of scrolling text in the terminal — that is completely normal.

How to confirm success

When you see a message like added XXX packages, the installation has finished successfully.

Step 06

Run the Project

Once installation is complete, it is time to run the project locally. Paste the following command into the terminal:

Terminal
npm run dev

After a few seconds, the terminal will display a message like:

Output
✓ Ready in 2.3s
- Local: http://localhost:3000

Now open your browser and go to:

Browser URL
http://localhost:3000

Your website is live!

You can now see the Walletium website running on your computer. Use this preview to test every customization you make.

Do not close the terminal

Keep the terminal window open while previewing the website. Closing it will stop the local server.
WalletiumNextjsTemplate

Step 08

Change Business Name

Replace every occurrence of “Walletium” across the website with your own business name. The visible text lives in the language files, and the SEO metadata is set in the layout file.

Configuration file

File Path
/messages/(ar.json, en.json, es.json, fr.json, hi.json, fe.json)

Edit steps

  • 01

    Open the language file you want to edit inside /messages/ (e.g. en.json).

  • 02

    Find the Metadata block shown below.

  • 03

    Replace “Walletium” with your own business name.

  • 04

    Save the file (Ctrl + S or Cmd + S).

Metadata block

JSON
"Metadata": {
  "title": "Walletium - Your Ultimate Digital Mobile Wallet Solution",
  "description": "It is a cutting-edge digital mobile wallet solution.",
  "keywords": "Walletium, digital wallet, mobile wallet, online payments",
  "ogImageAlt": "Walletium - Digital Mobile Wallet"
},

Meta config set

File Path
src/app/[locale]/layout.js
JavaScript
const SITE_URL = process.env.NEXT_PUBLIC_SITE_URL || "https://walletium.com";
const OG_IMAGE = "/images/logo/logo.png";

export async function generateMetadata({ params }) {
  return {
    openGraph: {
      siteName: "Walletium",
      images: [
        {
          url: OG_IMAGE,
          width: 1200,
          height: 630,
        },
      ],
    },
    twitter: {
      card: "summary_large_image",
      images: [OG_IMAGE],
    },
  };
}

Be careful with syntax

Do not delete the quote marks (") or commas (,). Only change the text between the quotes.

Step 09

Change Website Content

Customize the default language, homepage sections, and all on-page text from a single, organized location.

Default language change

File Path
src/i18n/routing.js
JavaScript
export const routing = defineRouting({
  defaultLocale: "en",
});

Content files location

File Path
src/app/[locale]/(public)/page.js

The homepage is composed of the following sections — add, remove, or reorder them to match your needs:

JavaScript
<main>
  <Navbar />
  <HeroSection />
  <PartnerSection />
  <FeaturesSection />
  <WhyChooseUsSection />
  <SecuritySection />
  <TestimonialsSection />
  <AppDownloadSection />
  <NewsletterSection />
  <Footer />
</main>

Multi-language ready

All section text is pulled from the files in /messages/. Edit the matching language file and the browser preview updates automatically when you save.

Step 10

Change Images & Graphics

Update banner images, feature icons, and section graphics to match your own brand identity.

Images folder location

Folder Path
public/images/

Replace process

  • 01

    Navigate to the public/images/ folder.

  • 02

    Note the file name of the image you want to change.

  • 03

    Save your new image using exactly the same file name.

  • 04

    Delete or rename the old image, then paste the new image in.

  • 05

    Refresh the browser to see the new image.

Image guidelines

Keep the same Name

Match the original Name other ways not working .

Keep the same size

Match the original width × height to keep the layout intact across pages.

Preferred format

Use PNG or WebP — they offer great quality with a smaller file size.

File size

Aim for under 500 KB per image to keep your website loading fast.

Step 11

Configure Admin Panel API

Most important section

If this configuration is not set correctly, your website will not be able to connect to the admin panel. Follow these steps carefully.

The Walletium website fetches data from your existing Walletium Admin Panel through its API. You need to point the website to the correct API URL.

Configuration file

File Path
.env

Can't find the .env file?

The project root contains a file named .env.example. Copy it and rename the copy to .env.

Edit steps

  • 01

    Open the .env file in VS Code.

  • 02

    Find the API URL line shown below.

  • 03

    Replace the example URL with your admin panel domain (including https://).

  • 04

    Save the file.

  • 05

    In the terminal, press Ctrl + C to stop the server, then run npm run dev again.

Example configuration

.env
NEXT_PUBLIC_API_URL=https://yourdomain.com/api
NEXT_PUBLIC_SITE_URL=https://yourdomain.com

URL format matters

✅ Correct: https://yourdomain.com/api❌ Wrong: yourdomain.com/api (missing https://)❌ Wrong: https://yourdomain.com/api/ (trailing slash)

Step 12

Connect Existing Admin Panel

If you already have a Walletium Admin Panel installed, this website will connect to it directly and pull live data.

How it works

Admin Panel

Your data, transactions, and users are stored on the backend.

API Connection

The URL in .env tells the website where to fetch live data from.

Website Display

Your customers see real-time content rendered from the backend.

Example setup

ComponentExample URL
Admin Panelhttps://yourdomain.com
API Endpointhttps://yourdomain.com/api
Website (Live)https://www.yourdomain.com

Connection test

When the API is connected correctly, the website will display real data from your admin panel — including pricing, features, and the services list.

Step 13

SEO & Website Settings

Configure browser tab title, favicon, and meta description so your website appears correctly in Google search results.

SEO configuration file

File Path
src/config/seo.js

Editable fields

JavaScript
title: "Your Business — Tagline",
description: "Short description of your business (160 chars)",
keywords: "payment, business, secure, online",
ogImage: "/images/og-image.png",

Change the favicon

To change the browser tab icon (favicon):

  • 01

    Go to the public/ folder.

  • 02

    Replace the favicon.ico file (32×32 or 64×64 pixels).

  • 03

    Clear browser cache and refresh the page.

Favicon generator

Use favicon.io to generate a custom favicon — it is free and easy to use.

Step 14

Common Beginner Mistakes

The most frequent mistakes new users make — and how to avoid them.

Skipping npm install

Always run npm install before running the project for the very first time.

Wrong API URL

Missing https:// or a trailing slash in the .env file will break the API connection.

Wrong logo dimensions

Logos that are too large or too small will distort the header layout.

Deleting important files

Never delete package.json or the node_modules/ folder by accident.

Stale browser cache

If your changes don't show up, do a hard refresh with Ctrl + Shift + R.

Removing quotes or commas

Deleting " or , while editing config files will cause syntax errors.

Step 15

Troubleshooting Guide

Solutions to the most common problems you may run into during setup.

Problem: white screen or blank page

  • Open the browser console (press F12).

  • Check the Console tab for any error messages.

  • In the terminal, press Ctrl + C and run npm run dev again.

Problem: “npm command not found”

Node.js is not installed, or the installation did not complete properly.

  • Download the LTS version from nodejs.org.

  • Restart your computer after installation completes.

  • Run node -v in the terminal to verify the version.

Problem: website not loading

  • Check that the terminal shows a “Ready” message.

  • Verify the URL: http://localhost:3000.

  • Make sure no other program is using port 3000.

Problem: API not connecting

  • Verify the API URL inside your .env file.

  • Open the admin panel domain in a browser and confirm it works.

  • Always restart the dev server after editing .env.

  • Using HTTP instead of HTTPS may block the connection.

Problem: images not changing

  • Confirm the file name matches the original exactly.

  • Clear browser cache (Ctrl + Shift + Delete).

  • Do a hard refresh (Ctrl + Shift + R).

Still not working?

If the solutions above don't fix your issue, reach out to our technical support team using the links in the next section.

Step 16

Support & Assistance

Our team is here to help. If you run into any issue, contact us through one of the channels below.

Support channels

What to include in your support request

For the fastest possible response, please share the following:

ItemWhy It Helps
ScreenshotHelps us visually understand your issue
Error messageCopy the full error text from terminal or browser
Browser consoleScreenshot of F12 → Console tab
Hosting detailsServer type, domain, and admin panel URL
Purchase codeYour CodeCanyon license code

Response time

We usually respond to support requests within 24–48 hours. Our working days are Monday to Friday