OMAR OG GAME MART is a production-ready, mobile-first gaming top-up platform for Bangladeshi gamers. It sells exactly two game products — Free Fire Top Up and eFootball Coin — through a secure wallet funded by bKash only (01996358306), with WhatsApp Support at 01996358306. The product intent is a premium dark gaming storefront that feels like a game client rather than a generic commerce template: UID entry, instant wallet debit, a unique Order ID, and a reward ping when the top-up lands.
The audience is phone-first, bKash-native, price-literate gamers (roughly 16–30) who need a fast, trustworthy top-up with a traceable order and a wallet they can top up and audit. The secondary audience is the operator (Admin) who manages the catalog, orders, deposits, refunds, users, settings, and an immutable audit trail through protected, server-authenticated admin routes.
The system is delivered as a Customer Frontend + Secure Backend + Database + Admin Panel, with authentication, wallet, payment verification, orders, transactions, audit logs, rate limiting, and privacy protection as first-class production concerns — not a UI/demo.
OMAR OG GAME MART is a single first-party application with two access planes:
Actors. Two accepted human personas: Customer and Admin. bKash is an external payment channel referenced by number only (no provider API integration is specified); WhatsApp is an outbound support channel at 01996358306. The backend is a non-persona system actor that owns all wallet balance and payment state.
Accepted behavior. Customers browse the two games and their packages, select a package, enter the required game ID/UID and WhatsApp number, pay from wallet, and receive a unique Order ID. Orders move through Pending → Processing → Completed → Cancelled. Completed orders show a lightweight celebration animation with optional sound/mute control. The Home page optionally shows a Recent Orders section with fully masked customer information. Admin manages users, games, products (prices, images, visibility, ordering), deposits, orders, refunds, and settings, and reviews dashboard statistics and immutable audit logs. The catalog is modular so Admin can add future games/products without changing the core structure.
Ownership and exclusions. Wallet balances and payments are controlled only by the secure backend. A customer must never access another customer's orders, wallet, transactions, or personal information. The system does not collect or store unnecessary sensitive information such as passwords, OTPs, or verification codes for game accounts. The reference site https://riogameshop.com/ is used only for general shopping-flow inspiration — its logo, branding, layout, colors, text, images, code, and copyrighted assets are not copied.
Delivery ownership. OMAR OG GAME MART is a first-party web application. The customer frontend, the admin panel, the backend business logic, the database, authentication, wallet, order lifecycle, transaction ledger, audit logs, and rate limiting are all owned and operated by this project. There is no third-party storefront, marketplace, or hosted commerce platform in the delivery path.
Access ownership. Identity is application-owned. Customers establish identity themselves through Sign Up and verify it through Login; Admin identity is provisioned server-side and verified through the same Login surface, with admin routes protected by server-side authorization. Anonymous visitors can reach Home, Games, Login, and Sign Up. Every surface that exposes customer-specific state — Top Up, Orders, Order Details, Wallet, Transactions, Account — requires an authenticated customer session and enforces ownership server-side. Every admin surface requires an authenticated admin session.
Payment and support ownership. bKash is the only accepted payment method, referenced by the number 01996358306. Deposit verification is performed by the backend against the recorded bKash deposit reference; the wallet is credited only by the secure backend. WhatsApp Support is an outbound contact channel at 01996358306 — the platform surfaces the number and hands the conversation to WhatsApp; it does not host the conversation.
Current vs. future boundary. Current scope is exactly the two games (Free Fire Top Up, eFootball Coin), the wallet, bKash-only deposits, the order lifecycle, the admin panel, and the security controls listed above. The modular catalog is a current structural requirement: Admin can add future games/products without changing the core structure. Those future games/products are not current catalog content and are not part of current acceptance; only the modular capability to add them is current.
Not applicable — the only reference directive declares uses: ["structure_reference"] with authority: "inspiration_only" and no content_source. No factual entities, collections, fields, values, dates, contacts, links, or media from the reference site are carried into this product.
FR-01 — Brand and original identity (explicit) As a visitor, I should see the OMAR OG GAME MART brand with a completely original gaming logo and branding, so that I recognize the operator as a distinct, premium storefront.
FR-02 — Reference used for inspiration only (explicit) As the product owner, I should have the reference site used only for general shopping-flow inspiration, so that no copied logo, branding, layout, colors, text, images, code, or copyrighted assets appear in this product.
FR-03 — Two games only (explicit) As a customer, I should see exactly Free Fire Top Up and eFootball Coin as the current games, so that I browse a focused catalog.
FR-04 — Modular catalog extension (explicit) As an Admin, I should be able to add future games/products without changing the core structure, so that the catalog can grow without re-engineering.
FR-05 — Customer registration (explicit) As a customer, I should be able to register an account, so that I can own a wallet, orders, and a dashboard.
FR-06 — Customer login (explicit) As a customer, I should be able to log in, so that I can reach my protected surfaces.
FR-07 — Customer profile (explicit) As a customer, I should be able to view and update my profile, so that my account details stay correct.
FR-08 — Order history (explicit) As a customer, I should see my own order history, so that I can track every top-up I placed.
FR-09 — Account dashboard (explicit) As a customer, I should have an account dashboard, so that I can see my profile, wallet, and order summaries in one place.
FR-10 — Secure wallet with balance (explicit) As a customer, I should have a secure wallet with a balance, so that I can pay for top-ups without leaving the platform.
FR-11 — Wallet deposits (explicit) As a customer, I should be able to deposit into my wallet, so that I can fund top-ups.
FR-12 — Wallet transaction history (explicit) As a customer, I should see my wallet transaction history, so that I can audit every deposit, debit, and refund.
FR-13 — bKash only (explicit) As a customer, I should pay using bKash only at 01996358306, so that I use the operator's accepted payment channel.
FR-14 — WhatsApp Support (explicit) As a customer, I should reach WhatsApp Support at 01996358306, so that I can get help with deposits or orders.
FR-15 — Admin-managed package prices, images, visibility, and ordering (explicit) As an Admin, I should manage package prices, images, visibility, and ordering, so that the customer catalog reflects current offers.
FR-16 — Package selection and required inputs (explicit) As a customer, I should select a package and enter the required game ID/UID and WhatsApp number, so that the operator can fulfill my top-up.
FR-17 — Pay from wallet and receive a unique Order ID (explicit) As a customer, I should pay from my wallet and receive a unique Order ID, so that I have a traceable purchase.
FR-18 — Order statuses (explicit) As a customer, I should see my order move through Pending, Processing, Completed, or Cancelled, so that I know its current state.
FR-19 — Admin manages users, games, products, deposits, orders, refunds, and settings (explicit) As an Admin, I should manage users, games, products, deposits, orders, refunds, and settings, so that I can operate the storefront end to end.
FR-20 — Completed-order celebration with sound/mute (explicit) As a customer, I should see a lightweight celebration animation with optional sound/mute control when my order completes, so that success feels rewarding without being intrusive.
FR-21 — Optional masked Recent Orders (explicit) As a visitor, I should optionally see a Recent Orders section with fully masked customer information, so that activity is visible without exposing anyone's data.
FR-22 — Admin Panel surface set (explicit) As an Admin, I should have Dashboard statistics, Game Management, Product/Package Management, Order Management, User Management, Wallet/Deposit Management, Website Settings, and Admin Action Audit Logs, so that every operational responsibility has a home.
FR-23 — Admin credentials in environment variables (explicit) As the product owner, I should have admin credentials stored in secure environment variables with server-side authentication, so that they are never exposed in frontend or source code.
FR-24 — Secure authentication and password hashing (explicit) As the product owner, I should have secure authentication and password hashing, so that credentials are never stored or compared in plaintext.
FR-25 — Server-side authorization and ownership checks (explicit) As the product owner, I should have server-side authorization and ownership checks, so that every protected resource is validated on the server.
FR-26 — Customer privacy protection (explicit) As a customer, I should have my privacy protected, so that my data is never exposed to other customers.
FR-27 — Rate limiting and abuse protection (explicit) As the product owner, I should have rate limiting and abuse protection, so that the platform resists brute force and automated abuse.
FR-28 — Server-side wallet validation (explicit) As the product owner, I should have server-side wallet validation, so that balances and payments are controlled only by the secure backend.
FR-29 — Duplicate-order/double-deduction protection (explicit) As a customer, I should be protected from duplicate orders and double deductions, so that I am charged exactly once per order.
FR-30 — Database transactions for wallet/order operations (explicit) As the product owner, I should have database transactions for wallet and order operations, so that wallet and order state never diverge.
FR-31 — Input validation and error handling (explicit) As a customer, I should receive clear validation and error handling, so that I can correct mistakes without losing work.
FR-32 — Protected Admin routes (explicit) As the product owner, I should have protected admin routes, so that only authenticated admins reach administrative surfaces.
FR-33 — Immutable Admin Audit Logs (explicit) As an Admin, I should have immutable Admin Action Audit Logs, so that every administrative action is traceable and cannot be altered.
FR-34 — No cross-customer access (explicit) As a customer, I should never be able to access another customer's orders, wallet, transactions, or personal information, so that my data and theirs stay private.
FR-35 — Backend-only wallet and payment control (explicit) As the product owner, I should have wallet balances and payments controlled only by the secure backend, so that no client can manipulate money.
FR-36 — Premium dark gaming theme, fast, fully responsive (explicit) As a customer, I should get a premium dark gaming theme with clean UI, fast loading, and full responsiveness on iPhone, Android, iPad, tablet, and desktop, so that the storefront feels native on my device.
FR-37 — Mobile bottom navigation (explicit) As a customer, I should have mobile bottom navigation Home | Games | Orders | Wallet | Account, so that I can move between core surfaces with one thumb.
FR-38 — Homepage required content (explicit) As a visitor, I should see OMAR OG GAME MART, Free Fire, eFootball, Wallet, Orders, WhatsApp Support, and bKash payment information on the homepage, so that I immediately understand what is sold and how to pay.
FR-39 — No unnecessary sensitive game-account data (explicit) As a customer, I should not have to provide unnecessary sensitive information such as passwords, OTPs, or verification codes for game accounts, so that my game accounts stay secure.
FR-40 — Production-ready architecture (explicit) As the product owner, I should have a functional production-ready architecture — Customer Frontend + Secure Backend + Database + Admin Panel + Authentication + Wallet + Payment Verification + Orders + Transactions + Audit Logs + Rate Limiting + Privacy Protection — so that the platform operates in production, not as a demo.
FR-41 — Original design, clean code, scalable database, secure server-side logic (explicit) As the product owner, I should have an original design, clean code, a scalable database structure, and secure server-side business logic, so that the platform can grow safely.
FR-42 — Customer self-service enrollment before first protected use (required_inference) As a customer, I should be able to establish my own account before using protected surfaces, so that my wallet, orders, and profile are bound to me.
FR-43 — Returning verification through Login (required_inference) As a Customer or Admin, I should verify my identity at Login before protected work, so that protected state stays bound to the correct participant.
FR-44 — Admin provisioning and secure server-side authentication (required_inference) As the product owner, I should have admin access provisioned and server-authenticated rather than publicly enrolled, so that administrative control cannot be self-granted.
FR-45 — Backend wallet validation, transactions, ownership checks, and duplicate protection before wallet-funded completion (required_inference) As a customer, I should have my wallet-funded order validated, transacted, ownership-checked, and duplicate-protected before it completes, so that my money and order state are always correct.
Product context. A Bangladeshi gamer, typically 16–30, phone-first and bKash-native, who tops up Free Fire diamonds or eFootball coins. They are price-literate and compare package value quickly, and they expect WhatsApp to be a real support channel rather than a form.
Primary goal. Complete a top-up fast — pick a package, enter the game ID/UID and WhatsApp number, pay from wallet, and get a unique Order ID they can track to completion.
Distinct accepted responsibilities. The Customer owns their own identity (Sign Up, Login), their own profile and dashboard (Account), their own wallet balance and deposits (Wallet), their own transaction history (Transactions), their own order history and tracking (Orders, Order Details), and the top-up submission itself (Top Up). They are the only persona who funds a wallet, selects a package, supplies a game ID/UID and WhatsApp number, and experiences the completion celebration.
Relevant inputs and decisions. Which game and package to buy; the correct game ID/UID; the WhatsApp number to be contacted on; whether their wallet balance covers the package; whether to deposit more via bKash at 01996358306; whether to mute the completion chime.
Interactions with other accepted participants. The Customer's deposit is verified by the Admin, who credits the wallet. The Customer's order is moved through Pending → Processing → Completed or Cancelled by the Admin. The Customer can escalate to WhatsApp Support at 01996358306. The Customer never sees another customer's orders, wallet, transactions, or personal information.
Observable success. A completed top-up order with a unique Order ID, a wallet debited exactly once, a transaction recorded, and a single celebration burst with an optional chime they can mute.
Product context. The operator of OMAR OG GAME MART, working from a protected admin plane that reuses the same dark HUD system as the customer frontend. They are accountable for the catalog, the money, and the audit trail.
Primary goal. Keep the catalog accurate and the order/wallet pipeline moving, with every action traceable.
Distinct accepted responsibilities. The Admin owns dashboard statistics; Game Management (including adding future games/products through the modular structure without changing the core structure); Product/Package Management (prices, images, visibility, ordering); Order Management (status transitions and refunds); User Management; Wallet/Deposit Management (bKash deposit verification); Website Settings; and review of immutable Admin Action Audit Logs. The Admin is the only persona who verifies deposits, transitions order statuses, issues refunds, and changes catalog or site configuration.
Relevant inputs and decisions. Which bKash deposits to verify against the recorded reference; which order status transition is correct; whether a refund is warranted; which packages to publish, price, reorder, or hide; which settings to change.
Interactions with other accepted participants. The Admin acts on Customer-originated deposits and orders, and every action they take is written to the immutable audit log. The Admin's changes become visible to Customers in Games, Top Up, Wallet, and Order Details.
Observable success. A managed catalog and order/wallet operation set with a complete, immutable audit trail, reached only through protected routes with server-side authentication.
Muse and headline. Gleb Kuznetsov — Cinematic future tech for a Bangladesh game top-up arcade. The register is arcade adrenaline, not calm commerce: dark voids, luminous data, motion as the hero, HUD-like numerals. Trust must read as "premium operator", not "cheap reseller".
Color tokens (dark mode).
| Role | Token | Value |
|---|---|---|
| Background (void) | --bg-void | #07060F |
| Surface (glass panel) | --surface | #12101F at 72% opacity |
| Surface border | --surface-edge | rgba(0, 229, 255, 0.22) 1px |
| Text (primary) | --text | #EDEBFF |
| Primary (instrument cyan) | --primary | #00E5FF |
| Accent (magenta) | --accent | #FF2E88 |
| Muted (labels, timestamps, masked data) | --muted | #8B87B8 |
Color rules. The near-black violet void #07060F covers roughly 70% of every screen; floating glass panels (#12101F at 72% opacity with a 1px rgba(0,229,255,.22) border) hold all content. Electric cyan #00E5FF is the instrument colour: wallet balance, UID readouts, focus rings, and the primary CTA "Pay from Wallet". Magenta #FF2E88 is reserved for exactly two jobs — the bKash payment badge/pill and the completed-order celebration burst — so it never dilutes. Muted #8B87B8 carries labels, timestamps, and masked data. Body text #EDEBFF on #07060F is approximately 17:1 contrast; muted labels appear only on surface panels, never on raw void. Blue–indigo (#2563EB, #4F46E5, #6366F1) is forbidden as primary or accent, and no white or near-white ground is permitted. Cyan and magenta are the only two luminous hues permitted; bright rainbow/multicolour gradients are excluded.
Typography. Headings: Space Grotesk 600/700, tight -0.02em tracking, sentence case for section heads and ALL-CAPS with +0.16em tracking for HUD micro-labels. Body: Manrope. Headline scale is deliberately oversized — the brand wordmark and package prices are the loudest type on the page. Modular scale 1.25 on mobile / 1.333 on desktop: 64 / 48 / 32 / 22 / 17 / 14 / 12. Prices and UID strings are set in tabular numerals; HUD labels at 12px uppercase; body 17px mobile / 16px desktop with 1.65 line-height. Inter, Roboto, Arial, Helvetica, Open Sans, Lato, Poppins, and system-ui are excluded for headings and body text.
Shape language. Glass slabs with 18–22px radii and a single luminous 1px edge; hard-edged 4px "data chips" for UID and Order ID readouts so machine data never looks like a soft button; thin 1px cyan hairlines as section rules; a circular wallet gauge (ring, not bar) for balance; pill CTAs only for the two hero actions. No blobs and no soft drop shadows — depth comes from glow and border, not from blur.
Layout. Mobile-first single column, 16px gutters, 44px+ touch targets, sticky bottom nav (Home | Games | Orders | Wallet | Account) with a cyan active indicator that slides between tabs. Desktop expands to a 12-column asymmetric grid: left 7 columns for the game/package matrix, right 5 columns as a sticky "Operator Panel" holding wallet balance, UID entry, and the Pay button. The admin panel reuses the same grid with a left rail of log-style nav items and monospace audit rows.
Imagery style. No stock people and no clip art. The hero visual is a procedural cyan particle/grid field (CSS + canvas, or a single low-poly Three.js scene) standing in for "data flowing into a game account". Game identity is carried by two abstract, original glyphs — a diamond-cut shard for Free Fire and a coin-hex for eFootball — drawn as luminous line icons, plus macro product-card crops of the two packages. The live Recent Orders feed reads as a data ticker, not as photos. Photographs of people, generic esports stock art, and copied game publisher assets and logos are excluded.
The Operator Panel over a drifting data void.
The public entry is a full-bleed dark void (#07060F). Top-left sits the OMAR OG GAME MART wordmark in Space Grotesk 700 at 64px mobile / 96px desktop, with "OG" cut out as a cyan-outlined shard mark — the original logo. Beneath it runs a horizontal HUD strip reading FREE FIRE · eFOOTBALL · bKASH 01996358306 · WHATSAPP 01996358306 in 12px uppercase cyan-on-void with hairline dividers — one ruled, uppercase, hairline-divided data line instead of a nav bar or a features row.
On the right (below the wordmark on mobile) floats a glass Operator Panel: the wallet balance rendered as a circular cyan gauge with large tabular numerals inside the ring, a UID input set as a hard-edged 4px data chip, and a magenta-trimmed bKash pill. Behind everything, a slowly drifting cyan particle grid.
The signature move is the circular wallet gauge as the hero's dominant instrument — the balance visibly depletes and fills on every transaction, so the wallet reads as a live instrument rather than a number. Package cards are loadout tiles: hard 4px-edged data chips carrying price, diamond/coin amount, and a hover/tap sweep of cyan light across the tile edge — never identical rounded hover-lift cards. Order confirmation is a full-screen HUD receipt: the Order ID in monospace on a dark inset panel with the four statuses (Pending → Processing → Completed → Cancelled) as a stepped progress rail, magenta only on the final node. The single celebratory motion in the entire product is the completed-order burst — a magenta particle burst from the wallet gauge plus an optional chime, with a persistent mute toggle.
There is no centred headline, no subtext paragraph, and no blue button. The concept recomposes only accepted content, states, and controls — brand, games, wallet, orders, support, bKash information, and the optional masked Recent Orders ticker.
Interaction Model: Animated Motion Tempo: cinematic Hero Dimensionality: webgl
Landing Hero Motion Brief. The focal subject is the procedural cyan particle/grid field standing in for "data flowing into a game account", with the circular wallet gauge as the dominant instrument in the foreground Operator Panel. The input→transformation→outcome thesis: as the visitor's pointer or scroll position moves, the particle grid drifts and the gauge ring's luminous arc responds, transforming a static void into a live instrument readout — the outcome is that the wallet reads as an active, trustworthy device before any transaction occurs. Motion vocabulary: one continuous slow parallax drift on the hero's grid/particle field, scroll-scrubbed horizontal sweep on the package matrix, 180ms functional transitions on all controls, and one choreographed moment — the completed-order celebration (ring pulse + particle burst + optional chime, with a persistent mute toggle). The composed first frame shows the wordmark top-left with the "OG" shard mark, the HUD micro-strip beneath it, the glass Operator Panel with the cyan gauge and magenta bKash pill on the right, and the particle grid already drifting behind. The reduced-motion state replaces the drift and burst with static glows and a plain success checkmark, keeping the gauge, HUD strip, and Operator Panel fully legible.
Landing Hero 3D Scene Brief — DIRECTION-DERIVED. A single crafted real-time WebGL scene: a low-poly cyan particle/grid field representing data flowing into a game account, rendered as a shallow volumetric plane that drifts slowly and reacts subtly to pointer position and scroll. The scene shows the product's defining state — a wallet instrument at rest, ready to receive a top-up — and stays behind the Operator Panel so the gauge, UID chip, and bKash pill remain the readable foreground. It must degrade gracefully: on low-power devices it reduces particle count, and under reduced-motion it renders a single static frame.
Motion rules. Bouncy spring easing, confetti spam, and celebration animation on anything other than a Completed order are excluded. The completed-order celebration is the only celebratory motion in the entire product. Light-mode-only components and admin screens that break from the dark HUD system are excluded.
NFR-01 — Secure authentication and password hashing (explicit). Passwords are hashed at rest and verified server-side; plaintext credentials are never stored, logged, or compared. Rationale: the brief requires secure authentication and password hashing.
NFR-02 — Server-side authorization and ownership checks (explicit). Every protected request is authorized server-side against the authenticated identity and the ownership of the requested resource. Rationale: the brief requires server-side authorization and ownership checks.
NFR-03 — Customer privacy protection (explicit). Customer-specific data is returned only to its owner; public surfaces expose masked data only. Rationale: the brief requires customer privacy protection and prohibits cross-customer access.
NFR-04 — Rate limiting and abuse protection (explicit). Authentication, deposit submission, and order submission are rate-limited with clear retry messaging. Rationale: the brief requires rate limiting and abuse protection.
NFR-05 — Server-side wallet validation (explicit). All balance and payment mutations are validated and applied server-side; the client cannot set a balance. Rationale: the brief requires server-side wallet validation and backend-only wallet control.
NFR-06 — Duplicate-order/double-deduction protection (explicit). Repeated submissions do not create a second order or a second debit. Rationale: the brief requires duplicate-order/double-deduction protection.
NFR-07 — Database transactions for wallet/order operations (explicit). Wallet debit, order creation, deposit credit, and refund credit commit atomically or not at all. Rationale: the brief requires database transactions for wallet and order operations.
NFR-08 — Input validation and error handling (explicit). All inputs are validated server-side with specific, actionable error messages. Rationale: the brief requires input validation and error handling.
NFR-09 — Protected admin routes (explicit). Admin routes are protected by server-side authentication and authorization. Rationale: the brief requires protected admin routes.
NFR-10 — Immutable Admin Audit Logs (explicit). Administrative actions append audit records that cannot be edited or deleted; an audit write failure blocks the underlying action. Rationale: the brief requires immutable Admin Action Audit Logs.
NFR-11 — Admin credentials in environment variables (explicit). Admin credentials are supplied through secure environment variables and verified server-side; they never appear in frontend bundles or source code. Rationale: the brief requires this explicitly.
NFR-12 — No cross-customer access (explicit). A customer can never access another customer's orders, wallet, transactions, or personal information. Rationale: explicit hard constraint.
NFR-13 — No unnecessary sensitive game-account data (explicit). The platform does not collect or store game-account passwords, OTPs, or verification codes. Rationale: explicit hard constraint.
NFR-14 — Performance and responsiveness (explicit). Fast loading and full responsiveness on iPhone, Android, iPad, tablet, and desktop, with 44px+ touch targets and skeletons instead of blank screens on slow networks. Rationale: the brief requires fast loading and full responsiveness across those device classes.
NFR-15 — Production readiness (explicit). The delivered system is a functional production-ready architecture, not a UI/demo. Rationale: explicit hard constraint.
NFR-16 — Scalable database and modular catalog (explicit). The schema supports adding future games/products without changing the core structure. Rationale: the brief requires a modular system and a scalable database structure.
NFR-17 — Original design and clean code (explicit). All design and code are original; no copied logo, branding, layout, colors, text, images, code, or copyrighted assets from the reference site. Rationale: explicit hard constraint.
NFR-18 — Accessible motion (required_inference). Reduced-motion users receive static glows and a plain success checkmark instead of the celebration burst. Rationale: the celebration is the only celebratory motion and must remain usable without motion.
Assumptions.
Constraints.

Game catalog
Two titles live today. Tap a tile to browse its packages and complete the top up with your wallet balance.
Diamonds
Choose a diamond package, enter your Free Fire UID, and pay from your wallet.
Coins
Choose a coin package, enter your eFootball ID, and pay from your wallet.
Wallet and Orders are personal surfaces. Your session is checked on the secure backend before either page loads — sign in if you are not already.
Payment & support

Game catalog
Two titles live today. Tap a tile to browse its packages and complete the top up with your wallet balance.
Diamonds
Choose a diamond package, enter your Free Fire UID, and pay from your wallet.
Coins
Choose a coin package, enter your eFootball ID, and pay from your wallet.
Wallet and Orders are personal surfaces. Your session is checked on the secure backend before either page loads — sign in if you are not already.
Payment & support
No comments yet. Be the first!