Skip to main content

Points wallet and levels

Points Wallet and Levels is a level-0, write-capable source route for a credit_point loyalty plan, business participation, levels, and add-on configuration.

Availability and safe access

The sidebar item requires addon_points_and_levels; the route can also mount while configuration is loading. The base category view does not mount the plan controller. Selecting Points wallet, or loading its matching ?id deep link, mounts the controller: it reads loyalty plans and, when credit_point is absent, reads businesses and can create a default plan for the first result. Do not open the route or panel for documentation.

Blocked runtime boundary

  1. Use only a synthetic, pre-provisioned credit_point plan and synthetic business/customer records.
  2. Intercept loyalty-plan, business, level, configuration, image, wallet, and value-transfer requests.
  3. Prove the exact fixture cannot create a plan or reach production customer value.
  4. Admit runtime only with immutable receipts for every read, write, and blocked downstream effect.
Points Wallet and Levels catalogue cards without plan or customer details

The screen also exposes a dynamic add-on configuration list. An unavailable card or empty wallet-panel state is not proof that no change occurred: current source can create a default plan while that panel loads.

Points wallet

Source models a loyalty plan of type credit_point, general rates, and per-business accumulation/redemption participation. It does not establish a universal conversion formula or deployed customer behavior.

Plan and business controls map to loyalty-plan/business writes. Levels can be read, created, updated, or deleted, and images can be involved. These are customer-value effect classes; no balance, order, customer, redemption, image, configuration, or save operation was run.

Levels

The Levels surface can list records and expose add/edit/delete controls. Returned level data can include names and images. This source trace is not a runnable procedure or proof that a level is available or effective.

Customer-value effects

Loyalty levels can be linked to customer records and rewards eligibility. Treat creating, editing, or deleting a level as a production change; confirm the intended customer impact and preserve the current configuration before saving.

Troubleshooting

Why is Points Wallet and Levels missing?

The sidebar entry needs addon_points_and_levels; the route is administrator-only. Ask a project administrator to confirm both conditions.

Why did a plan appear after opening the wallet panel?

The wallet controller creates a default credit_point plan when it cannot find one and a business is available. This is a known side effect, not a harmless empty state. Use a pre-provisioned fixture for training and captures.

Can I test points by changing a live rate or level?

No. Rate, business, and level changes can affect customer value. Test only with an approved non-production project and synthetic customer data.


Related guides: Customers