Integrate SBC on Canton
SBC is a USD-backed stablecoin issued by Brale and available natively on the Canton Network.
This guide explains how to add SBC to a wallet or application that already supports the Canton Network Token Standard (CIP-56).
No separate holder onboarding or Brale API integration is required.SBC Token Information
| Parameter | Value |
|---|---|
| Network | Canton Network |
| Name | Stable Coin |
| Symbol | SBC |
| Token ID | f29bdd7a-1469-498a-ba2a-796bf5387b31 |
| Provider Party ID | party-28dc4516-b5ca-44ff-86c7-2107e90a6807::1220b8301e18aa8a401d6e34e6c20f8b0243183c514373bca8f1b6b9270246341a9e |
| Registrar Party ID | party-28dc4516-b5ca-44ff-86c7-2107e90a6807::1220b8301e18aa8a401d6e34e6c20f8b0243183c514373bca8f1b6b9270246341a9e |
1. Connect to Canton
Your application should have access to a Canton participant and a Canton party representing the wallet or user.
Use your participant's Ledger API v2 to read the ledger state visible to that party and submit transactions.
If your wallet already supports Canton Network Token Standard assets, you can use the same infrastructure to support SBC.
2. Discover SBC
SBC's canonical Token ID is:
f29bdd7a-1469-498a-ba2a-796bf5387b31SBC does not require a separate Brale registry API.
After the applicable contracts have been disclosed to your party, use Ledger API v2 to query the relevant Utility templates and locate SBC's instrument configuration.
SBC uses:
Template:
Utility.Registry.V0.Configuration.Instrument:InstrumentConfiguration
Package ID:
3b25e7327b493bbe063e89d34fdacbfcc491007e5eabefea3a2919044a28f452Match the instrument's Token ID to the SBC Token ID above.
3. Display an SBC Balance
Query the Canton Network Token Standard holdings visible to the user's party.
Filter those holdings for SBC using the SBC Token ID and calculate the user's available SBC balance.
Party
↓
Query token holdings
↓
Filter for SBC Token ID
↓
Sum available SBC holdings
↓
Display SBC balanceFor example:
Stable Coin
SBC
Balance: 1,250.00 SBCYour application should update the displayed balance based on current ledger state.
4. Receive SBC
No separate holder onboarding is required to receive SBC.
To receive SBC:
- Provide the user's Canton party ID to the sender.
- Monitor the ledger for the resulting SBC transfer.
- Complete any actions required by the applicable Token Standard transfer flow.
- Update the wallet balance when the SBC holdings become available.
The wallet should confirm that the received asset matches the SBC Token ID before displaying it as SBC.
5. Send SBC
Use the standard Canton token transfer workflow to send SBC.
The wallet should:
- Query the user's available SBC holdings.
- Enter the recipient's Canton party ID.
- Enter the amount of SBC to send.
- Prepare and authorize the transaction.
- Submit the transaction.
- Monitor the transfer until completion.
- Update the user's SBC balance.
SBC holdings
↓
Recipient + amount
↓
Prepare transaction
↓
Authorize
↓
Submit
↓
Transfer completes6. Display Transaction History
Use ledger events visible to the user's party to build SBC transaction history.
A wallet may display:
- Send or receive
- Amount
- Sender or recipient
- Status
- Date and time
- Canton update ID
Because Canton provides ledger-level privacy, wallets should build history from the transactions visible to their party rather than assuming all network activity is publicly available.
Integration Checklist
Before enabling SBC, verify that your wallet can:
- Connect to Ledger API v2
- Support the Canton Network Token Standard
- Identify SBC by Token ID
- Discover the SBC instrument configuration
- Query and display SBC balances
- Receive SBC
- Send SBC
- Track transfers through completion
- Display SBC transaction history
SBC at a Glance
Token IDf29bdd7a-1469-498a-ba2a-796bf5387b31Utility.Registry.V0.Configuration.Instrument:InstrumentConfigurationHolder onboarding: Not required
External registry API: Not required
If your wallet already supports Canton Network Token Standard assets, SBC can be integrated using your existing Token Standard workflows.
Next Steps
- Canton Network Overview - SBC token and party configuration
- CIP-56 Token Standard