wiezonContact sales

Prepaid payments

Your brand. Your prepaid payments.
In-app and in-store.

We build branded prepaid payment systems and connect them to existing apps and stores, covering top-ups, balances, app, QR and NFC payments, merchant settlement and refunds.

Build your own payment service.
Start with how balances move.

Paid balances and promotional credits need different rules, as do cancellations and refunds. We turn your brand’s policies into operational controls.

Automatic top-ups when balances run low

Keep payments moving with predefined top-up rules and support balance transfers between members.

Manage policies across multiple cards

Separate cash-backed and non-cash balances. Set top-up limits and payment and refund priorities for each card.

Prepaid payments in-app and in-store

We provide customer and merchant apps, QR and NFC payments, physical cards and POS integration modules.

01

Control top-ups and balances

Operate prepaid services with automatic top-ups, member-to-member balance transfers and separate reserve balances.

  • Automatic top-ups and member-to-member balance transfers
  • Top-up limits and separate reserve balances
  • Cash-backed and non-cash balances and refund policies

02

Connect your app and in-store POS

Integrate APIs into your existing app and accept QR, NFC or physical card payments in stores.

  • Customer and merchant apps and QR payments
  • NFC tag payment/POS linkage DLL provided
  • Issuance and management of physical prepaid cards

03

Manage card usage through settlement

Set card policies and spending priorities, and connect PG-funded top-ups, merchant settlement and customer refunds.

  • Card prefixes, multi-card top-ups and priorities
  • Merchant transaction, settlement, and limit management
  • Real-time and next-day refund process support

Top-ups, spending and balances.
Configured for your brand.

Configure top-up methods, card policies and in-store payments together. Partner point conversion and POS integration depend on the relevant provider and equipment interfaces.

Members and top-ups

  • Sign up, identity verification, member management
  • PG-funded and partner-point top-ups
  • Automatic top-ups when balances run low
  • Transfer of prepaid balance between members

Balance and card policy

  • Top-up limits and separate excess reserves
  • Separate cash-backed and non-cash balances
  • Card prefixes and batch top-ups
  • Payment/refund priority by card

Online/in-store payment

  • Connect to existing apps and web APIs
  • Customer QR/shopping mall QR payment
  • NFC tag/POS linkage DLL
  • Issuance and management of physical prepaid cards

Settlement and refund

  • Merchant settlement and limit management
  • Member real-time/next-day refund process
  • Periodic merchant deposit/member refund
  • DB encryption of key information such as prepaid balance

Your implementation roadmap

We review your business and existing systems, then agree on the scope and schedule.

  1. 1

    Define top-up and spending policies

    Agree on top-up methods and limits, automatic top-up rules, card spending priorities and refund timing.

  2. 2

    Connect customer touchpoints

    We review your app, website and store systems, then build the payment screens and APIs you need.

  3. 3

    Verify transaction flow

    Verify top-ups, payments, cancellations, refunds and merchant settlement before preparing for launch.

Frequently asked questions

Can I add a prepaid feature to an app I'm already running?

We review your app’s customer and order data structures and API integration approach to define the scope. We also agree on each team’s responsibilities for app screens and the prepaid backend.

Can I manage prepaid funds, points, and multiple prepaid cards separately?

Separate cash-backed and non-cash balances, with different prepaid policies for each card prefix. You can top up multiple cards together and define payment and refund priorities by card.

Can I use it in offline stores?

We provide QR and NFC payments, physical card issuance and management, and a POS integration DLL. We check store equipment interfaces and supported functions before connecting them. Refund workflows support real-time or next-day processing, subject to payout methods and operational policies.

Are top-up fees separate from implementation costs?

Implementation, additional integration and operating costs are considered separately from payment method fees for top-ups. Responsibilities also depend on the service operator and partner agreements.

Design where customers
top up and pay.

Let’s define your prepaid service around your existing app, stores and balance policies.