Smart one-card

Identity, spend, and benefits, on one card platform

MeetCarbon Cloud Smart one-card keeps tenants, card types, wallets, benefit supply, and carbon events on one platform. Funded tenants use a main account and a subsidy wallet. Benefit-only tenants have identity and quotas, with no balance on the card. Tap events map to carbon-benefit methodologies. Local points and official points stay in separate columns. Day-to-day issuance for offices and hospitals stays in those scene products. Parking charges stay in Smart parking.

4 forms
Fund, benefit, hybrid, carbon only
Subsidy first
Then the main account
Benefit supply
Catalog, admission, parking tiers
Two columns
Local and official stay apart
One-card desk
Sample data
12
Active tenants
1,860
Spends today
4
Merchants to settle
2
Events to map
Open items
  • Office canteen · settlement to confirmSettle
  • Clean-plate · event map to checkCarbon
  • Association · provider to enableBenefit
How it runs

From issuance to two point columns

Four steps match menus already in the product. After identity is on file, funds or benefits, settlement, and carbon events follow the same tenant.

1

Enroll

Set the tenant form, org tree, and card type. A physical card or a phone code is only a carrier.

Tenant · Identity
2

Enable

Funded tenants open wallets and a deduct order. Benefit tenants open a catalog and never show a balance.

Wallet · Benefits
3

Settle

Terminal spend enters the merchant network, then a settlement per merchant, checked against the daily recon.

Terminal · Settlement
4

Record

Behavior events go to carbon-benefit methods. Local and official points stay in two columns.

Events · Points
Product tour

What you see in Smart one-card

The menu groups tenants and identity, cash and merchants, benefit supply, and carbon links. Open any item to see the job it actually does.

Workbench

See active tenants, settlements waiting, and events still unmapped, then jump to the tenant form. Figures are for the shift. Published amounts follow the settlement.

Tabs
OpenTenantsSettle
What it does
  • Open-item total
  • Jump to the form
  • Figures are samples
Screen sample
MeetCarbon Cloud · Smart one-card
12
Tenants
1,860
Spends
4
To settle
2
To map

Tenant counts, ticket counts, and amounts in the samples only show the screen layout.

Forms

Decide whether this tenant is cash, benefits, or carbon only

Four templates already exist on the form page. Identity stays on. The lists below show which layers open and which stay closed.

Choose a form
Opens
Identity and cardMain accountSubsidy walletMerchant settlement
Stays closed
Benefit balance page

Campus canteens and office meal subsidies use this form. Subsidy is deducted first, then the main account.

Park and community service desks are still marked planned in the scene-pack list. The platform can store a form first. A separate desk is not delivered yet.

Deduct sample

Drag the spend, and see subsidy versus main

The sample uses the default order: subsidy wallet first, then the main account. The live order and per-transaction cap follow the template saved on the deduct-order page.

Spend45 CNY
0 CNY60 CNY

Sample: a 20 CNY subsidy wallet, subsidy first, the rest on the main account

Subsidy pool
20.00CNY
Subsidy wallet
20.00CNY
Main account
25.00CNY

The slider omits the prepaid wallet, limit blocks, and a live terminal deduct. The deduct-order page currently stores a template. Once tenant config is connected, that tenant’s order applies.

Who uses it

Admins set the form, card desks issue, settlement faces merchants

Carbon operators watch event maps and the two point columns. An association’s day-to-day redeem stays in Zero-carbon organization, not on the platform supply page.

Question to answer

Should this tenant open cash, benefits, or carbon scoring only?

What they watch
  • Active tenants
  • Form template
  • Whether a scene desk already exists
Pages they open
WorkbenchForm templatesScene packs
Where data enters

Rosters, terminals, and events enter the same tenant

Every spend or redeem has to match a card and a tenant. Carbon formulas are not rewritten here. Parking prices are not edited here.

Tenant and org roster

The tenant, org tree, and identity source decide who receives a card.

TenantOrgSource

Card types and carriers

Physical cards, codes, and delegation live on the identity page. A benefit card carries no balance.

Terminal spend

Funded spend enters the ledger from a terminal, then splits across wallets by deduct order.

Merchant settlement

Settlements are issued per merchant. The recon daily checks that day’s lines.

Benefit redeem

The catalog and admission rules decide whether a redeem is allowed. Day-to-day issue stays in the scene product.

Behavior events

Clean-plate and travel events map to carbon benefit. Official points return in their own column.

What this page does not rebuild

  • Reduction methods and the points ledger live in carbon benefit.
  • Lot pricing, monthly passes, and orders live in Smart parking.
  • Office meal-subsidy desks live in Zero-carbon office. Hospital card desks live in Zero-carbon hospital.
  • Association member issue and redeem live in Zero-carbon organization.

Park and community desks are marked planned in the scene packs. The platform can store forms and merchants. A separate service page is not delivered yet.

Go-live steps

Set the form and the card, then open cash or benefits

Use this order for the first tenant. Carbon mapping can wait until events exist. Identity can be built first.

Before you start
  • 1Tenant name and org levels
  • 2Form: funded, benefit, hybrid, or carbon only
  • 3Card types and carriers
  • 4If funded: merchants, terminals, subsidy and main account
  • 5If recording carbon: behaviors and the matching methods

The deduct-order page stores a template. After tenant config is connected, terminals deduct in that tenant’s order.

  1. 01

    Create the tenant

    Register the tenant and pick one form template.

    You get · Tenant file
  2. 02

    Connect the roster

    Set the org tree and identity source, then card types.

    You get · Ready to issue
  3. 03

    Open cash or benefits

    Funded tenants write wallets and a deduct order. Benefit tenants build a supply catalog.

    You get · Ready to spend or redeem
  4. 04

    Attach merchants

    Register merchants and terminals, then the first settlement.

    You get · Ready to recon
  5. 05

    Map events

    Point behaviors at carbon-benefit methods and turn on the two columns.

    You get · Two point columns
  6. 06

    Hand off to the scene

    Office, hospital, and eldercare use desks that already exist.

    You get · Scene can serve
On the platform

Identity, cash, benefits, and carbon stay on one platform

Smart one-card is the card platform. Methods, parking charges, and each scene’s daily desk have their own products.

Identity first

Org, card type, and carrier exist before cash or benefits attach to the card.

The form picks the layers

Benefit-only hides the balance. Carbon-only leaves cash off.

Subsidy, then main

The default deduct order can change, with its own per-transaction cap.

Supply apart from redeem

The platform holds the catalog and admission. Scene products handle day-to-day issue.

Two columns

Local incentives and official carbon-benefit points sit side by side. Summing them is blocked.

Desks stay in the scene

Eldercare reuses the office shell. Hospitals use the hospital card shell.

Questions

Keep the card platform apart from the carbon ledger and the parking ledger

How do Smart one-card and carbon benefit split the work?

This page collects behaviors, maps events, and shows points in two columns. Reduction methods and the points ledger live in carbon benefit. One-card does not write a second accounting rule.

Can local points and official points be shown as one total?

They must not be added. The display rule keeps local points and badges in one column and official carbon-benefit points in another, and it states that summing is blocked.

Is a parking waiver handled on this page?

This page only keeps benefit parking tiers. Lot pricing, monthly passes, and orders stay in Smart parking.

Why does a benefit-only card have no balance?

Benefit-only is identity plus quota. The card shows no balance and creates no cash settlement. Membership issue and redeem stay in Zero-carbon organization.

Can a park or a community open its own desk now?

Those two service shells are marked planned in the scene packs. The platform can store a form and merchants first. A separate desk is not delivered yet.

Can the deduct amounts on this page be used as terminal rules?

Quote them only as samples. The slider uses a 20 CNY subsidy pool. The live order and per-transaction cap follow the template on the deduct-order page, and that page currently stores a template.

Start with one tenant’s form and card type

Tell us whether it is an office meal subsidy, hospital staff, membership benefits, or carbon scoring only. We will walk through identity, wallets or benefits, settlement, and the two point columns for that scope.