L07 / STAKEHOLDER WALLET & CARD

Stakeholder wallet and co-branded card solution for listed companies

Let stakeholders,
owns your business account.

Combine corporate brand wallets, rights management backends and co-branded card interfaces with professional implementation and operations. Let identity, contribution, rights and daily use be connected at the enterprise's own entrance.

Plan my wallet and co-branded cards View role usage scenarios

Enterprise’s own brand Configure rules by role Start with a small-scale pilot

ONE BRAND. CONNECTED RELATIONSHIPS. Interface and card interface

Your business Stakeholder Account Enterprise Example

YOUR ENTERPRISE ACCOUNT

relationship, starting with the account.

Account role Configure by identity and authorization

Rights Center Service and Contribution

Management entrance Topics and participation

Available balance Use under the rules after settlement Confirm wallet and card-program conditions separately

YOUR COMPANY Scheme diagram

Corporate co-branded card

Identity Contribution Equity Governance

Enterprise wallet and backend × Co-branded card interface × Manual implementation

Software configuration, card projects and available areas are subject to actual cooperation conditions and acceptance confirmation.

Connect more long-term relationships from one enterprise instance P05 + P06 / PRODUCTS × SERVICES

CONNECTED RELATIONSHIPS

Let the long-term relationship between enterprises,
There is a going concern entrance.

Brand, rules and accounts are built together to move the solution from interface to real business use.

Connect relationships to businesses

Use the company's own brand entrance to undertake shareholders, employees, customers and partners, and organize authority and communication by role.

Brand Account/Role Permissions

Put the rules into practical use

Let contribution, equity, governance and card scenarios have clear configuration, confirmation and usage processes to connect the daily operations of the enterprise.

Contribution rights/governance participation

Make the construction ready for acceptance and delivery

Starting from the first instance, check the account experience, interface, rules and operational feedback before deciding on the next step of expansion.

Scenario test/operation review

01 / DIFFERENT ROLES. ONE ENTERPRISE ENTRY.

The same enterprise entrance,
Connect different roles and rights.

Choose a role to explore the relationships an account can support. Begin with one or two role types.

SHAREHOLDERS & INVESTORS

Let the holding relationship extend to continuous participation.

Organize information disclosure, issue participation and rights review within the scope of authorization and qualifications, so that capital communication has a continuous corporate entrance. Capital positions and settlement status are accessed through professional interfaces on demand.

Incorporate shareholders and investors into the first discussion

Your Business/Shareholder and Investor Accounts Scene diagram

Relationship identity: Identity, qualifications and visibility
Rights and Participation: Disclosure, Issues and Delegated Governance
Expand on demand: Capital position and settlement status interface

First confirm the identity and disclosure rules, and then configure the participation and capital interface.

The role view is configured based on identity, authorization and actual rights and interests; account registration, card holding and governance participation confirm qualifications respectively.

02 / PRODUCTS × PROFESSIONAL SERVICES

Use technology to carry accounts,
Use a team to implement and operate.

Three groups of technical capabilities, combined with six types of manual work. Write the actually adopted products, interfaces and services into the same delivery scope.

P05 / ENTERPRISE WALLET

Corporate brand wallets and accounts

Use the company's own name, visuals, and account entries to organize stakeholder identities, rights, and notifications.

Corporate Brand App and Wallet Interface
Role accounts, permissions and qualifications
Contribution Record and Equity Center

Software configuration and instance deployment

P05 / GOVERNANCE & CONSOLE

Governance and enterprise operations backend

Let enterprises manage roles, rules, governance processes and operational records, and make it clear who can see, who can change, and who can confirm.

Proposal, participation and disclosure portal
Role rules and equity configuration
Operation logs, reports and permissions

Configuration, Processes & Acceptance

P06 / CARD PROGRAM API

Co-branded card and card project interface

Connect the wallet payable balance and card management process, and access virtual cards and physical cards according to cooperation conditions.

Enterprise card surface and role card configuration
Card opening, status and life cycle interface
Wallet balance & applicable payment access

Interface access + partner approval

OPTIONAL / Capital interface

Connect capital equity as needed.

STO, position holding, disclosure, exit and settlement interfaces can be evaluated; capital connection independently confirms professional entities and access conditions, and corporate wallet and role operations can be planned in advance.

Discuss optional extensions

PROFESSIONAL WORK

Put software capabilities into actual use by enterprises.

Needs & Scenario Diagnosis

Based on corporate goals, priority roles and target areas, determine the first phase scenarios, modules and acceptance boundaries.

Requirements Blueprint / Initial Scope

Brand and touchpoint design

Align branding across the app, wallet, card, backend and notifications, implementing asset permissions and review.

Brand specifications / interface and card surface

Instance deployment and interface implementation

Configure the enterprise instance, environment, interfaces and data scope; organize integration testing and scenario-based acceptance.

Configuration Checklist / Tests & Acceptance

Roles, rights and governance configuration

Put identity, contribution, rights and participation rules into the configuration and approval process to form the basis for operation.

Role Matrix/Rules and Processes

Partners and professional coordination

Check the cooperation conditions such as card issuance, payment and settlement, and coordinate the required professional review and access arrangements.

Responsibility list / access dependencies

Training and ongoing operations

Organize pilot personnel training, problem follow-up and operational review, and then decide on role and module expansion.

Operations Manual/Operation and Maintenance Plan

ACCOUNT DESIGN / CLEAR RULES

same entrance,
Separate accounts clearly.

Let users see clearly "what they can participate in, what they can hold, and what funds can be used for payment", so that there is a clear basis for operations.

01 / RIGHTS & GOVERNANCE

Contribution and governance rights

Contribution records, service rights, incentive rules and topic participation are confirmed by role and system.

Configure according to rules

02 / CAPITAL RIGHTS · OPTIONAL

Capital Equity and Positions

Display approved positions, dividends and exit status on demand, retaining professional qualifications and permission requirements.

Access via professional interface

03 / PAYABLE BALANCE

Payable balance and cards

The disbursable funds that have been formed and meet the conditions are then connected to the usage scenarios of the actual cooperation card project.

Use according to settlement and card rules

When capital equity is involved

Capital Equity
Applicable Exit & Compliant Settlement
Available balance
Card usage

Capital positions and payable balances are displayed separately, and the required transactions, custody, clearing and settlement are undertaken by the corresponding entities according to conditions.

03 / FROM PROJECT BLUEPRINT TO PILOT

From the project blueprint,
Go to the enterprise instance that can be verified.

Advance according to milestones and confirm results step by step. Check dependencies first, and then arrange joint debugging, acceptance and pilot testing for the first batch of users.

Needs Diagnosis

Determine corporate goals, initial roles, target regions and scenarios.

Delivery direction: Project Blueprint & Implementation Scope
Confirm node: Requirements Confirmation

Brand and Vision

Design unified brand touch points for wallet, card surface and backend.

Delivery direction: Brand specifications and interface solutions
Confirm node: Brand authorization and review

Wallet-instance Deployment

Configure an enterprise instance, environment and initial accounts to create a test version.

Delivery direction: Wallet Test Version & Configuration Checklist
Confirm node: User Acceptance Testing

Account and governance configuration

Implement roles, rights, permissions and rules of engagement.

Delivery direction: Enterprise backend and rule files
Confirm node: Character and scene acceptance

Card project access

After confirming the cooperation conditions, jointly debug the card interface and check the sample card and usage process.

Delivery direction: Interface records, sample cards and process testing
Confirm node: Partner approval and access acceptance

Optional capital interface

Evaluate securities, custody, disclosure, exit and settlement connections as needed.

Delivery direction: Interface scope and professional process documents
Confirm node: Professional subject and legal confirmation

The card project and capital interface stages rely on actual partners and professional confirmation; functions, scheduling, regions and acceptance are agreed upon by the project.

WHO DOES WHAT

The five types of responsibilities shall be implemented separately before cooperation.

Cooperation responsibilities for corporate wallet and co-branded card solutions
Scope of work	Responsible entity	Specific responsibilities
Brand, role and rights rules	Listed companies	Confirm business goals, brand authorization, rights basis, user scenarios and decision-making coordination.
Wallet Software & Integration Implementation	WISERUNION／Implementation Team	Deliver instances, accounts, governance and backend according to the formal scope, and coordinate interfaces, testing and operations.
Card items and payments	Card issuing and payment cooperation institutions	Responsible for card project approval, issuance, payment authorization and related transaction risk control responsibilities.
Custody, clearing and settlement	Corresponding custody and settlement institution	Be responsible for asset custody, fund settlement and registration, and liquidation records according to the actual access scope.
Securities and capital interface (optional)	Qualified Securities & Professional Institutions	Responsible for issuance, access, transaction transfer and required professional review, and all parties shall confirm access conditions.

MEASURE THE PILOT

Use actual use to verify the value of the first phase.

Within the agreed data and authorization scope, observe account activation, use of rights, governance participation, support issues and use of available cards, and formulate a pilot report and adjustment suggestions for the next period.

04 / CHOOSE YOUR STARTING POINT

First make an enterprise example,
Expand more relationships.

Select the portfolio scope from the first phase target, and confirm the software, implementation, ongoing operations and partner expenses separately.

01 / COOPERATION SCOPE Initial Recommendation

Enterprise Wallet and Dual Card Pilot

Start with a company and one or two types of roles

First verify the brand account, role rules and card usage process to form a verifiable first phase delivery.

Corporate brand wallet and basic backend
One or two types of roles and equity rules
Standard virtual card and physical card access evaluation
Joint debugging and testing, personnel training and pilot review

Planning my first pilot

02 / COOPERATION SCOPE

Stakeholder Operations

Connect more roles with real business scenarios

Expand roles, reach and operations on existing instances, and clarify arrangements for ongoing maintenance and data reporting.

Multi-role accounts, permissions and rights configuration
Card project and life cycle management
Activities, notifications and operation processes
Reporting, maintenance and release expansion plans

Discuss roles and operational expansion

03 / COOPERATION SCOPE

Capital interface extension

Add professional connections according to business needs

Based on the wallet and card projects, separately evaluate the interfaces between capital equity display and securities, custody, settlement, etc.

Separation of capital equity and payable balance
Securities and investor qualification interface assessment
Disclosure, Exit and Settlement Status Links
Division of labor among professional entities and process acceptance

Assessment Capital Interface Extension

The above is the starting point for discussion on the scope of cooperation; the actual software version, card products, professional entities and charging methods will be confirmed in the evaluation and formal agreement.

READY FOR THE FIRST CONVERSATION

Let’s make three things clear first:
Make the first round of discussions more specific.

There is no need to prepare all materials in the first round. First let both parties judge the roles, scenes and conditions, and then arrange a detailed demonstration of the plan.

01 / PEOPLE

Who to connect first?

Start with one or two roles, stating current relationships and the desired user-experience improvement.

02 / SCENARIO

What to implement first?

The highest priority business scenario among brand accounts, rights, governance and cards.

03 / READINESS

What kind of foundation is there?

Target area, existing systems, brand materials, person in charge and cooperation conditions.

Organize my cooperation needs Download plan introduction

05 / BEFORE WE START

Before cooperation,
Make the key issues clear.

Define initial scope, branding, accounts and partner conditions separately.

Do I need to launch an STO or issue a token first?

There is no need to consider the capital interface as a prerequisite for the first phase. You can first implement corporate brand wallet, role rights management and card project access. STO or securities, custody and settlement interfaces are optional extensions and require separate confirmation of business foundation, professional entities and applicable conditions.

How is it different from purchasing a separate wallet or co-branded card?

L07 Deliver the enterprise wallet, rights management backend and card project interface together with demand diagnosis, brand design, deployment, rule configuration and operation. The focus is to connect role identities, rights and usage scenarios in the same enterprise portal, and to promote implementation with clear division of labor and acceptance.

Can companies use their own brands and rules?

The company name, vision, account, role and equity rules can be configured by project. Data boundaries, permissions, logging and backup arrangements are confirmed and verified in the real architecture. The brand and logical configuration are independent, which does not automatically mean an independent license, independent custody or independent legal entity.

Can capital equity, contributions or points be directly consumed by credit card?

Capital positions, governance interests, or contribution records cannot be consolidated into payable balances. When capital interests are involved, the completion of applicable transactions, redemptions, distributions and compliance settlements may result in a payable balance. The card will only connect disbursable funds that meet the conditions of the card program.

Who will issue the card? Which regions are virtual and physical cards available for?

The card is accessed through the actual cooperative card project, and the corresponding card issuer and payment entity shall bear the responsibility. Virtual cards, physical cards, regions, limits and usage scenarios depend on partners, user qualifications, approvals and formal rules, and are confirmed separately in the first round of evaluation.

How long to launch? How are pricing and acceptance determined?

First confirm the modules, roles, target regions, existing systems and third-party dependencies, and then develop milestones, quotations and acceptance lists. Software configuration, custom development, continued use, card projects and external professional fees are confirmed separately; the actual schedule is affected by the interface, partner approval, application review and customer decision-making.

What materials can be prepared for the first discussion?

First provide an overview of the company and business, the roles you want to connect to first, target regions, existing accounts or membership systems, and the problems you want to solve. The first round summary is sufficient to judge suitability; brand materials, detailed rules and professional materials are prepared in stages after the scope is confirmed.

This page is organized based on strategic discussion materials; the account, card surface and role views are structural representations. The actual software version, delivery status, brand authorization, regional and user adaptation, cooperation entities and interface scope are subject to evaluation, technical acceptance and formal agreement.

Continue reading · Solution

Implementation options for listed company stakeholder wallet and co-branded card solutions

The listed company's stakeholder wallet and co-branded card solution combines corporate wallet, rights management and card project interfaces, and cooperates with rule configuration, deployment and continuous operation. First determine the scope of the combination based on roles and business scenarios.

Reading & Selection Guidance Technology access and personnel implementation will be confirmed separately, and the cooperation entities and regional conditions of the card project will be separately evaluated.

Let stakeholders, owns your business account.