Issuer workflow

This page follows the issuer portal: your workspace, Assets, and each asset's tabs (Investors, Fundraising, Payouts, Operations, Marketplace, Profile & documents, and Rules & roles).

1. Set up the issuer workspace

An issuer workspace represents the organization that operates its token suites. It has a primary wallet and members with the Admin, Operator, or Viewer role. You manage members in Settings → Team. A workspace role does not give on-chain authority; see token suites.

The platform offers two onboarding paths: operator-reviewed issuer onboarding, and a self-service path on Real Testnet. The self-service path is for eligible personal-wallet accounts. It does not:

• create a Safe,
• give Business Validator admission, or
• replace production admission requirements.

For testnet self-service, prepare:

• a personal wallet,
• enough native ASSET for wallet-signed actions,
• the asset terms, and
• the intended owner and investor rules.

Self-service needs a full-authority session in which the personal wallet acts for itself. A Safe or delegate session cannot use this path.

On Real Testnet, each account can have one workspace, and each issuer can deploy five suites. The deployment limit can change. Testnet registration does not set production KYB, admission requirements, fees, or service timelines.

Finish issuer registration before you request a deployment. The platform refuses deployment while registration is pending. Do not create another workspace or repeat the deployment request, because neither one completes the registration.

2. Define the token and its rules

In Assets, start a new asset. On Real Testnet, the page is called Create a test token. Prepare the token name, symbol, precision, and the asset it represents. Decide which investor requirements and supported compliance controls the suite needs, such as jurisdiction restrictions, a supply cap, or a maximum holding per wallet.

Allowed countries is optional. Leave it empty to allow every country. In that case, the suite has no jurisdiction rule. You can change the supply cap, the per-wallet limit, and the countries later on the asset's Rules & roles tab.

New suites require KYC, AML, SANCTIONS_CLEARED, and JURISDICTION claims, and you cannot remove them. Before you add another required topic, read required topics. The change can immediately affect existing investors.

The token suite connects these settings to the contracts that enforce them. The rights that the token represents still come from the asset's terms and supporting agreements.

3. Deploy and confirm control

In the operator-reviewed path, an operator must approve your suite request before deployment. Where automatic deployment is turned on, as on Real Testnet, you can submit a request as a registered issuer, within the environment's limits.

Deployment has several steps. It creates the suite, configures the requested modules and roles, and gives the relevant ownership to the issuer wallet. Wait for the process to finish before you treat the suite as ready.

New tokens start paused. Deployment does not:

• admit investors,
• mint a supply,
• unpause transfers, or
• list the asset in the Marketplace.

4. Prepare the asset information

On Profile & documents, create the asset description, classification, jurisdiction information, and public document set. Review this information before you authorize the on-chain link to the token.

Asset information and documents explains how stored files and on-chain records work together, and how to publish the asset in the Marketplace.

5. Admit eligible investors

Investors select Request access after they are verified on the platform. On the asset's Investors tab, you review each request and authorize registration in the suite's identity registry. Approval in the workflow is not complete admission. Admission is complete only when the required on-chain registration succeeds.

You can also bring in investors that you verified independently. That path uses your own claim authority. You stay responsible for the verification and ongoing screening. Do not describe it as platform verification. The portal does not let you revoke a claim that you issued. To revoke one, ask platform operations.

6. Run and maintain operations

On the Operations tab, issue tokens only to recipients who meet the suite's requirements. Before you unpause ordinary transfers, review the configuration and operational readiness. Keep documents, investor access, and token controls up to date as the asset changes.

If a Safe controls your issuer wallet, its actions wait in Approvals for co-signatures. See How transactions settle.

7. Raise funds and pay holders

For primary issuance, use the asset's Fundraising tab and read offerings and subscriptions. A deployed token alone is not an open offering. Before you open an offering, check the payment window, agreement requirements, selected payment asset, and fee terms.

The Payouts tab shows the scheduled payments of the asset. The asset's Tokenization Validator prepares each payment, and investors claim it on Income. You fund the payment from the issuer wallet that governance approved. See how payments are recorded.

Until the validator activates the payment, you can take the funds back with Withdraw funding. After activation, you cannot.

A token deployment does not configure redemption or corporate actions.

Open the testnet workspace

Use the testnet issuer portal. If your wallet is not configured, first add Real Testnet.