What is OnRampDLT?
OnRampDLT is a technology platform that lets businesses and individuals issue digital tokens and structured debt offerings on the XRP Ledger — without writing a single line of code.
The XRP Ledger (XRPL) has native token issuance built directly into the protocol. That means creating a token does not require smart contracts, audits, or blockchain developers. For issuers raising capital through a structured bond offering under Regulation D, the platform provides the same no-code workflow: configure your offering terms, connect your Xaman wallet for signing, and manage your investor subscriptions through the dashboard. In both cases, your private keys never touch our servers.
Think of it this way: the XRPL is the infrastructure. Your Xaman wallet is your identity and signing authority. OnRampDLT is the interface that makes working with both accessible to anyone.
Who Is It For?
OnRampDLT is designed for three groups of people:
- Issuers — businesses or individuals who want to create and distribute a digital token or structured bond offering on the XRP Ledger. This includes tokenizing equity, loyalty points, membership credentials, real-world assets, or raising capital through a Reg D debt offering.
- Investors — accredited individuals or entities who want to participate in token or bond offerings hosted on the platform and understand how to subscribe, fund, and hold XRPL-based instruments.
- Legal Counsel — attorneys and compliance advisors representing issuers or investors who need to understand the platform's technical structure, custodial model, and the boundaries of what OnRampDLT does and does not do.
Roles on the Platform
Every account on OnRampDLT has a role that determines what actions are available. The two primary roles are Issuer and Investor.
Issuer
A business or individual creating and distributing a token or bond offering to raise capital.
- Create and configure tokens or bonds
- Register an XRPL issuer wallet
- Set supply, symbol, pricing, and distribution terms
- View subscriber records and payment history
- Manage offerings through the dashboard
Investor
An accredited individual or entity participating in token or bond offerings on the platform.
- Browse available token and bond offerings
- Submit accreditation confirmation
- Subscribe using XRP from your XRPL wallet
- Receive and hold tokens in your XRPL wallet
- View your subscription and payment history
Plans & Pricing — Overview
OnRampDLT is available in five tiers. The tier you are on determines which features are accessible — most importantly, which Regulation D exemption structure you can use for bond offerings.
| Plan | Price | Token Issuance | Bond Issuance | Wallets |
|---|---|---|---|---|
| Free | $0 | Not available | Not available | 0 |
| Investor | $49/yr | Not available | Subscribe to bonds only | 1 |
| Starter | $49/mo or $499/yr | mainnet + testnet, unlimited | Subscribe to bonds + issue tokens | 1 |
| Pro | $149/mo or $1,499/yr | mainnet + testnet, unlimited | 506(b) bonds | 3 |
| Business | $499/mo or $4,999/yr | mainnet + testnet, unlimited | 506(b) and 506(c) bonds | 10 |
| Enterprise | Custom / annual | mainnet + testnet, unlimited | 506(b), 506(c), white-label | Unlimited |
Annual plans save 15–17% versus monthly. All billing is processed through Stripe. OnRampDLT charges flat subscription fees only — we do not take a percentage of your offering proceeds.
506(b) vs 506(c) — Which Exemption Do You Need?
This is one of the most important decisions an issuer makes before launching a bond offering. The two exemptions determine who you can reach and how.
Rule 506(b) — available on Pro plan:
- No general solicitation or advertising permitted — you may only approach investors with whom you have a pre-existing relationship
- Up to 35 non-accredited but sophisticated investors may participate, plus unlimited accredited investors
- No cap on the amount raised
- Accreditation verification is self-certification — the issuer must have a reasonable basis to believe the investor qualifies
Rule 506(c) — available on Business plan:
- General solicitation and advertising are permitted — you can publicly market the offering, post on social media, run ads
- All investors must be accredited — no exceptions
- Accreditation must be actually verified, not just self-certified — this typically means reviewing tax returns, bank statements, or using a third-party verification service
- No cap on the amount raised
Add-Ons
The following add-ons are available on any paid plan:
- Investor KYC — $6 one-time per investor: Stripe Identity verification for investor accreditation. Valid for two years and reusable across all of your offerings. Required for 506(c) access.
- Verified Issuer Badge — $199 one-time: Entity document review by the platform. Adds a verified badge to your bond listings, signaling legitimacy to investors.
- API Access — $99/mo: Available as an add-on for Starter and Pro; included on Business and Enterprise. There is no public route list. Contact sales for Business+ API documentation.
Issuer Guide — Overview
As an issuer, you are using OnRampDLT to create a token or bond offering on the XRP Ledger and make it available to investors. The platform handles the technical complexity of XRPL transaction construction. You handle the business decisions: what the instrument represents, how much is available, on what terms, and who can participate.
Before you begin, understand that issuance on the XRPL is a technical act — not a legal one. Creating a token or configuring a bond offering does not automatically determine its regulatory classification. What matters is what the instrument represents and how it is marketed. Work with legal counsel to determine the appropriate classification and exemption structure before distributing to investors.
Bond Lifecycle
Every bond on OnRampDLT moves through four distinct states. Understanding the lifecycle helps both issuers and investors know what to expect at each stage.
- Draft — The bond has been configured and saved but is not yet visible to investors. The issuer can review and adjust settings. No subscriptions are accepted in this state.
- Active — The issuer has reviewed and signed the activation request in their wallet, the issuer wallet has enough XRP to operate on the ledger, and the bond is now open for investor subscriptions. The bond page is accessible to invited or eligible investors.
- Closed — The offering period has ended. No new subscriptions are accepted. The issuer is in the distribution phase — sending bond tokens and any XRP rewards to investors.
- Matured — The full bond term has elapsed. All scheduled interest payments have been made. The bond is complete.
Token vs Bond — What's the Difference?
These two words describe fundamentally different things, and the distinction matters legally.
- A token on the XRPL is a technical object. It has a name, a symbol, a supply cap, and an issuing wallet. By itself it carries no legal rights — it is a container. What legal rights, if any, attach to that container is determined by your offering documents, your jurisdiction, and how you market the token.
- A bond is a debt instrument — a legal promise to repay principal plus interest on a schedule. Bonds are securities in the US. An issuer selling its own bonds to accredited investors under Regulation D does not need to be a broker-dealer — the exemption applies to principals raising capital for their own ventures. A real estate LLC funding a new project, for example, can issue a Reg D bond to investors directly. What matters is that the issuer, not the platform, owns the compliance obligation. The bond platform features on OnRampDLT are currently in development.
Wallet Setup — What You Need
To issue tokens or bonds on the XRPL you need an issuer wallet. OnRampDLT supports three XRPL wallets: Xaman (formerly XUMM, iOS and Android), Crossmark (browser extension), and GemWallet (browser extension). All three are non-custodial — your private keys are generated on your device and never transmitted anywhere. Xaman is recommended for issuers as the bond activation flow uses Xaman QR-based signing.
Your issuer wallet needs to be funded with XRP to cover network reserves and transaction fees. Keep a modest XRP balance in the issuer wallet before you activate an offering — network reserve amounts can change.
See the Wallet & Security section for full setup instructions.
Creating Your Token — Step by Step
- Create an accountSign up at onrampdlt.io with your email address. Verify your email and log in to the dashboard.
- Upgrade to Starter or higherToken issuance requires at least a Starter plan ($49/mo or $499/yr). Free accounts cannot register wallets or issue tokens. Billing is handled via Stripe — your card is never stored on our servers.
- Register your issuer walletIn the dashboard, navigate to Issuer Wallet and enter your XRPL r-address. The platform prepares a one-time setup request for you to review and sign in your wallet so the account can issue tokens to holders.
- Configure your tokenEnter your token name, symbol, and total supply. Review all settings carefully — some token parameters cannot be changed after issuance.
- Sign and issueThe platform constructs the issuance transaction and sends it to Xaman. Open Xaman on your device, review the transaction details, and sign. Your token will be live on the XRP Ledger within seconds.
- Share your offeringOnce issued, investors who want to hold your token must first set a trust line from their wallet to your issuer address. The platform generates the trust line request automatically when an investor subscribes.
Launching a Bond — Step by Step
Bond issuance requires a Pro plan or higher and follows a distinct workflow from token creation. Your issuer wallet must be registered before you begin.
- Register and fund your issuer walletIn the dashboard, register your XRPL r-address as your issuer wallet. Fund it with enough XRP to cover network reserves before you activate. The dashboard shows your wallet balance.
- Enable token issuance (one-time)The platform prepares a one-time setup request. Open it in your wallet, review it, and sign. This lets your wallet issue tokens to investors.
- Configure your bondFill in the bond creation form: name, ticker symbol (up to 8 characters), total units available, price per unit in XRP, annual interest rate in basis points (100 bps = 1%), term in days, payment schedule (monthly, quarterly, semiannual, or annual), and an optional XRP reward for early investors. Add a description covering use of proceeds and any collateral. The dashboard shows live metrics — total raise, annual interest, reward pool, and minimum wallet funding required — as you type.
- Review and save as DraftSubmit the form. Your bond is saved in Draft status and is not yet visible to investors. Review all terms carefully — activation is irreversible.
- Activate the bondClick Activate in your bond dashboard. Review the request in your wallet (QR or in-app prompt) and sign. Once confirmed on-ledger, the bond status moves to Active, the payment schedule is generated, and your bond page is ready to share.
- Share your bond pageThe dashboard provides a shareable link to your bond detail page. Investors can view terms, calculate returns, and subscribe from that page.
- Distribute tokens and rewardsAfter investors subscribe, use the dashboard to send bond tokens and XRP rewards. The platform prepares the payments; you sign in your wallet — one approval can cover the batch of holders.
Bond Activation — What It Does and How to Complete It
Bond activation is the step that moves your bond from Draft to Active status, making it available for investor subscriptions. You sign one setup request in your wallet. OnRamp constructs that request; your keys never leave the device.
What activation does
Activation tells the XRP Ledger that your issuer wallet is ready to issue the bond instrument and that holders can receive and transfer it. It is a one-time, per-wallet operation. After it confirms on-ledger, the offering can accept subscriptions.
When to activate
Activate your bond after:
- The bond has been created and reviewed in Draft status
- Your issuer wallet is funded with enough XRP for network reserves
- All bond terms have been confirmed — activation is irreversible and bond parameters cannot be changed afterward
How to activate
- Open your bond in the dashboard and click Activate Bond.
- Review the request the platform prepared for your wallet (QR or in-app prompt).
- Sign in Xaman, Crossmark, or GemWallet.
- Wait for the dashboard to show Active status once the ledger confirms.
What happens after activation
Once activated:
- The bond status changes from Draft to Active
- The full payment schedule is generated (interest dates, amounts per unit)
- The bond detail page goes live at
onrampdlt.io/bonds/{id} - Investors you invite can begin subscribing
- You receive an activation confirmation email that includes a Form D reminder
Investor Guide — Overview
As an investor on OnRampDLT, you are participating in token offerings created by issuers on the XRP Ledger. This guide explains what that means, what you need to get started, and what happens at each step of the subscription process.
The Investor Plan
The Investor plan is a dedicated annual subscription at $49/year for individuals who want to subscribe to tokenized bond offerings on OnRampDLT but do not need token issuance or bond creation capabilities.
What the Investor plan includes
- Ability to subscribe to Reg D bond offerings on the platform
- One XRPL wallet registration
- KYC self-certification for 506(b) offerings
- Access to your investment portfolio dashboard and payment schedules
- Investment records remain accessible even if the plan lapses
Who needs it
You need the Investor plan if you want to invest in bond offerings on the platform and you do not already have a paid issuer plan. If you are on a Starter, Pro, Business, or Enterprise plan, investor access is already included — you do not need to purchase the Investor plan separately. The Investor plan is purpose-built for participants whose sole interest is investing, not issuing.
How to get it
Subscribe to the Investor plan at the pricing page on onrampdlt.com, or via the upgrade prompt that appears when you attempt to view a bond offering without an active subscription. The Investor plan is annual only — $49 billed once per year through Stripe.
Finding Offerings
Active token offerings are listed in the investor portal. Each listing includes the token name, symbol, and issuer information; total supply and units available; price per unit in XRP; and offering terms and documentation provided by the issuer.
OnRampDLT does not vet, endorse, or guarantee any offering. It is your responsibility to conduct due diligence on any issuer and offering before committing funds.
Subscribing to an Offering
- Create a platform account and upgrade to InvestorSign up at onrampdlt.io. A free account cannot subscribe to bond offerings — you must have at least an Investor account ($49/yr). If you are an issuer on a Starter plan or above, investor access is included at no extra charge. The Investor annual plan is purpose-built for participants who want to invest but not issue.
- Set your display profileIn the dashboard, add your first name, last name, and display name. This is distinct from your KYC record — it is used for dashboard personalization and issuer communications.
- Connect your XRPL walletYou will need a funded XRPL wallet (Xaman, Crossmark, or GemWallet) with enough XRP for the subscription, network fees, and the reserve for authorizing the issuer’s token.
- Set a trust lineBefore you can receive tokens, your wallet must authorize a trust line to the issuer's XRPL address. The platform generates this request for you to sign in your XRPL wallet. This is a one-time step per token.
- Send paymentXRP subscription payments flow directly from your XRPL wallet to the issuer's XRPL wallet. OnRampDLT does not intermediate this payment — we do not hold or touch your funds. Send the exact XRP amount shown and save your transaction hash — you will need it in the next step.
- Confirm your subscriptionSubmit your XRPL wallet address and the transaction hash from your payment. The platform checks the payment on the XRP Ledger (destination, sender, amount, and successful settlement). Only after that check is your subscription recorded.
- Receive tokensOnce the issuer distributes, bond tokens are sent to your XRPL wallet address. You can view your holdings in Xaman and on any XRPL block explorer using your transaction hash as a permanent receipt.
Accreditation — What It Means and Why It Matters
The offerings on this platform are structured as private placements under Regulation D of the US Securities Act. Participation is restricted to accredited investors as defined by the SEC.
You qualify as an accredited investor if you meet at least one of the following:
- Individual net worth exceeding $1,000,000, excluding the value of your primary residence
- Individual income exceeding $200,000 in each of the past two years with reasonable expectation of the same going forward
- Joint income with a spouse exceeding $300,000 in each of the past two years
- Holder of a Series 7, 65, or 82 license in good standing
- Certain entities with assets exceeding $5,000,000 or whose equity owners are all accredited investors
By certifying your accreditation status on the platform, you are making a legal representation. OnRampDLT does not independently verify accreditation. Under 506(b), that responsibility lies with the issuer who must have a reasonable basis to believe you qualify. Under 506(c), the issuer must take affirmative steps to actually verify accreditation — self-certification alone is not sufficient.
Legal Framework — Overview
This section is written for issuers, investors, and their legal counsel who need a plain-English explanation of the regulatory context in which OnRampDLT operates. It is not legal advice. Consult a qualified securities attorney for guidance specific to your situation.
Regulation D — Rules 506(b) and 506(c)
Regulation D provides exemptions from the securities registration requirements of the Securities Act of 1933. Rather than filing a full public offering, companies can raise capital from investors privately — as long as they comply with Reg D conditions.
Rule 506(b) is the most commonly used exemption. Under 506(b):
- There is no cap on the amount that can be raised
- Up to 35 non-accredited but sophisticated investors may participate, plus unlimited accredited investors
- No general solicitation or advertising is permitted — you cannot publicly advertise the offering
- Issuers must file a Form D with the SEC within 15 days of the first sale
- Purchasers receive restricted securities that cannot be freely resold without registration or another exemption
Rule 506(c) permits general solicitation and advertising but comes with stricter requirements:
- All investors must be accredited — no exceptions, no sophisticated non-accredited investors
- Accreditation must be actually verified by the issuer through reasonable steps — self-certification alone is not sufficient
- Issuers must still file Form D within 15 days of the first sale
- No cap on the amount raised
OnRampDLT's Role — What We Are and Are Not
OnRampDLT is a technology platform. We provide software tooling for token issuance and structured debt offerings on the XRP Ledger. We are not a registered broker-dealer, investment adviser, securities exchange, alternative trading system, or custodian of investor funds or assets. We are not a party to any transaction between issuer and investor.
Payments between investors and issuers occur directly on the XRP Ledger — wallet to wallet. OnRampDLT never holds, receives, or transmits investor funds. The platform constructs transaction objects that are signed by users in their own Xaman wallets. We cannot move funds on your behalf and never request private keys.
What You Are Buying
When you subscribe to an offering on this platform, you are acquiring an instrument — a token or a bond — issued by a third-party issuer. The rights associated with that instrument are defined entirely by the issuer's offering documents, not by the platform. For bond offerings, those documents will include repayment terms, interest rate, maturity date, and any conditions. For tokens, the rights depend entirely on what the issuer has defined and disclosed.
OnRampDLT makes no representation about the value of any offering, whether any instrument constitutes a security or utility, the financial condition of any issuer, or whether any offering complies with applicable securities laws in your jurisdiction.
XRPL-native instruments are non-custodial — they live in your wallet. If you lose access to your wallet, OnRampDLT cannot recover your holdings. There is no SIPC or FDIC equivalent protection for XRPL holdings.
Wallet & Security — Supported Wallets
OnRampDLT supports three XRPL wallets for signing. All three are self-custodial — your private key is generated on your device and never transmitted.
- Xaman (formerly XUMM) — iOS and Android. Recommended for most users. Sign by scanning a QR code or opening a deep link in the app.
- Crossmark — Browser extension (desktop). A good fit if you prefer to sign in the browser.
- GemWallet — Browser extension (desktop). Another browser-native option for registration and everyday signing.
Use a classic r-address (starts with r). Addresses that start with X are not supported.
Setting Up Xaman
Xaman is the recommended wallet and the one used throughout this guide. Here is how to get started:
- Download XamanSearch for "Xaman" in the App Store or Google Play. The developer is XRPL Labs. Do not download any other app claiming to be Xaman or XUMM.
- Create a new accountSelect "Create a new account." The app will generate a 24-word secret family seed. Write these words down on paper — do not screenshot, do not store digitally. This seed phrase is the only way to recover your wallet.
- Fund your walletA new XRPL account needs a small XRP reserve to activate, plus a reserve for each trust line. Issuer wallets should hold enough XRP to operate before you launch.
- Connect to OnRampDLTIn your dashboard, enter your r-address (your public XRPL address). When the platform needs your signature, it will push a request to your Xaman app or display a QR code.
What Is a Trust Line?
The XRP Ledger will not automatically deliver tokens to your wallet — you must first explicitly authorize a token by creating a trust line. This is a record on the ledger that says: "I authorize this issuer's address to send me this specific token, up to this limit."
- Trust lines are created by you and signed in your XRPL wallet — no one can force one onto your account
- Each trust line is specific to one issuer address and one token symbol
- Each trust line ties up a small XRP reserve while it is active
- If a trust line has a zero balance, you can remove it and recover that reserve
When you subscribe to an offering on OnRampDLT, the platform generates the trust line transaction automatically for you to sign in your XRPL wallet. You review and sign — nothing happens without your explicit approval.
Your Keys, Your Assets
OnRampDLT is designed from the ground up to never touch your keys. The flow is:
- OnRampDLT constructs an unsigned transaction object and sends it to Xaman
- Xaman signs the transaction locally on your device
- The signed transaction is broadcast to the XRPL network directly
- Our servers never see your private key at any point in this process
Protect your Xaman seed phrase accordingly. Store it offline in multiple secure physical locations. Do not share it with anyone — including us. We will never ask for it.
Accreditation — Platform KYC Process
OnRampDLT provides a built-in self-certification mechanism for accredited investor status. This creates a timestamped record tied to the user’s account so the issuer can keep a due-diligence file. Here is what the platform collects, at a high level.
Self-Certification (506(b) offerings)
Investors submit the following through the platform’s self-certification form:
- Full legal name
- Date of birth
- Full mailing address
- Accreditation basis — income, net worth, or professional license (Series 7, 65, or 82)
- When they certified (the platform keeps a timestamped record)
That record is available to the issuer on the bond page for their files. OnRamp records the representation; it does not independently verify it.
Stripe Identity Verification (506(c) offerings)
For 506(c) bond access, investors must complete a $6 one-time Stripe Identity verification. This is an independent verification step that goes beyond self-certification and satisfies the “reasonable steps” standard for 506(c) accredited investor verification.
Data we keep — for counsel and operators
OnRamp stores account, offering, and subscription records so issuers and investors can run a raise. It does not publish a field-level schema. In plain language:
What we keep
- Account contact details, plan, and login history
- Public XRPL addresses you register, plus offering terms you enter
- Accreditation self-certification (and Stripe Identity status when you use it)
- Subscription amounts, payment hashes, and distribution history
- Team invites on Business and Enterprise accounts
What we do not keep
- Private keys or seed phrases — never requested or stored
- Payment card numbers — Stripe processes cards; we keep a customer reference only
- Government ID images — not collected by the platform
- Plaintext passwords
For retention, deletion, and GDPR/CCPA requests, contact support@onrampdlt.com. See the Privacy Policy. Counsel who need a deeper data map can request it through sales on a Business+ engagement — it is not published here.
Distributing Tokens to Recipients
Once your token is issued, OnRampDLT gives you three ways to get tokens into wallets without ever handling a recipient’s private keys.
Send Direct (Wallet-to-Wallet)
Use My Tokens → Send when you already know the recipient’s XRPL address. Enter the address and amount. The platform checks whether they have a trust line. If they do, payment goes straight through. If not, a Trust Line QR is generated for them to scan in Xaman first.
Send by Email (Claim Link Workflow)
Use this when recipients don’t have a wallet yet, or when you want to distribute by email without collecting addresses upfront.
- Generate a claim link — Go to My Tokens → Send by Email. Enter the recipient’s name, email, and amount. The platform emails them a unique single-use claim link.
- Recipient opens the link — They land on a guided claim page at onrampdlt.io/claim.
- Recipient identifies their wallet — They scan a Xaman Sign In QR (which returns their address automatically) or paste their XRPL r-address manually. No transaction is signed here — this step only tells the platform where to send.
- Trust line (if needed) — If they don’t already have a trust line for your token, they approve a one-time authorization in Xaman. If they already have one, this step is skipped.
- You are notified — Once their wallet is ready, you receive an email with a Xaman deep link. Tap it on your phone, approve the payment in Xaman, and tokens go directly from your issuer wallet to theirs. The recipient can close their browser after Step 3 — they do not need to wait.
- Recipient is notified — Once the transaction confirms on the XRPL ledger, the recipient receives a confirmation email with the amount, destination wallet, and a link to view the transaction on the XRPL explorer. The reply-to on that email is your account email — they contact you, not OnRampDLT support.
Note: Claim links are single-use and expire after 30 days. You can generate a new one at any time from the token detail page.
Sharing a Trust Line QR
To let recipients pre-authorize your token before you send — useful for launches or campaigns — use My Tokens → Trust Line QR. Generates a QR and shareable link recipients can scan in Xaman. Embed it in a webpage, print it, or share it in a message.
Syncing Your Supply from the XRPL
The supply counter in your dashboard is maintained by the platform as tokens are minted and sent. If it ever drifts from the true on-chain state — for example after tokens are returned to your issuer wallet by recipients, or after direct on-chain transactions outside the platform — use the Sync Supply button on each token row.
Sync Supply reads the outstanding balance from the XRP Ledger for your issuer address and updates the dashboard to match. It is read-only and safe to run at any time.
Ending a Token Program
When a rewards or distribution program is complete and all tokens have been returned or redeemed:
- Sync Supply — Run Sync Supply to confirm on-chain outstanding balance is zero (or whatever the true remaining amount is). The dashboard will update to reflect reality.
- Archive the token — Click Archive on the token row. A confirmation dialog will remind you that tokens already in recipient wallets are not affected. Archiving marks the token inactive on the platform: no new minting, no new sends, no new claim links. The token is hidden from your active list.
- Restore if needed — Archive is reversible. If you restart the program, click Restore to bring the token back to active status.
Important: Archiving is a platform-level action only. Tokens already in recipient wallets remain on the XRPL ledger — archiving does not touch them. The ledger is always the source of truth. See the FAQ below for advanced on-chain options (GlobalFreeze).
FAQ — Issuer Questions
Getting StartedAll transactions are signed by the appropriate wallet at each step. The platform is never a custodian.
Step 2 — Archive. Click Archive on the token row. Confirm the dialog. The token is marked inactive on the platform — no new minting, sends, or claim links are possible. It is hidden from your active list.
Tokens already in recipient wallets are not affected. Archive is a platform flag only. The XRPL ledger is the source of truth and does not change. Tokens holders have are theirs.
Archive is reversible — click Restore at any time to reactivate.
Ledger-level freeze options exist on XRPL but are not a dashboard feature. Talk to counsel before taking any on-chain step that would restrict holders.
Token Supply & Minting
Token Supply & MintingMax supply is an optional cap on the total number of tokens that can ever exist for your token. If you set a max supply, no more than that amount can be minted in total — ever. If you leave max supply blank, there is no cap: you or future platform features can issue additional tokens at any time.
Example: Initial supply 100,000 and max supply 1,000,000 means you start with 100,000 tokens but can mint up to 900,000 more in the future. Initial supply 500,000 and max supply 500,000 means the total is permanently fixed at 500,000.
This is a permanent, irreversible decision. If you believe you may ever need to mint more tokens — for additional investors, for liquidity, for loyalty reward programs — do not set max equal to initial. Either leave max supply blank (open-ended) or set it significantly higher than your initial supply.
This is appropriate for tokens where you expect to issue to additional investors over time, tokens used as loyalty or rewards points that will grow with usage, or any use case where future minting may be needed.
Investors and token holders should be aware that open-ended supply means dilution is possible. Be transparent with your token holders about your intended supply policy.
Rule of thumb: if you might ever need more, set max supply at 5–10x your initial supply, or leave it blank for an open-ended token.
The platform will not let you mint past your max supply cap. If your token has no cap, you can mint additional amounts from the dashboard.
Tokens that have reached their cap can still be transferred between wallets, used in transactions, or redeemed for value — the cap only restricts new issuance. If you need more supply and the cap is reached, you would need to issue a new token.
If you need to retire tokens from circulation, consult your legal counsel first — depending on how your token is structured, burning or repurchasing tokens may have regulatory implications.
Customer engagement: loyalty points for retail, coffee shops, and gyms; tiered membership programs (silver/gold/platinum); referral rewards; event attendance tokens.
Gaming & entertainment: in-game currency for indie studios; tournament prize tokens redeemable for merch or cash; fan tokens for sports teams, streamers, or podcasters.
Business operations: employee spot bonus programs; contractor milestone payments; vendor settlement tokens in closed B2B networks; franchise royalty tokens earned on sales.
Community & governance: voting weight tokens for co-ops or member organizations; volunteer hour tracking for nonprofits; community contribution points for forums or DAOs.
Supply chain & provenance: product authenticity tokens (scan QR = receive proof-of-genuine token); carbon credit micro-tokens; batch/lot tracking in food, pharmaceutical, or luxury goods supply chains.
Education: course completion credentials; skill certification tokens issued by training programs or bootcamps; student achievement badges that live in the holder’s own wallet.
A security token (equity or debt) represents a financial claim: an ownership stake, profit sharing, or repayment of capital with interest. If your token gives holders a financial return or ownership right, it is a security and must be structured accordingly under Regulation D.
OnRampDLT’s declaration wizard walks you through the classification with built-in legal guidance before you issue. When in doubt, consult your attorney.
With rippling enabled, token holders can send tokens to each other, trade them on XRPL’s built-in DEX, or transfer them freely. This is what you want for loyalty points, retail rewards, fan tokens, or any token designed to circulate between customers.
Turn it OFF only if you want tokens to flow exclusively from you to each holder with no peer-to-peer transfer — for example, single-use vouchers, non-transferable access credentials, or one-way distribution programs where resale is prohibited.
With Require Auth off, any customer wallet can freely receive your token without you approving them individually. This is the correct setting for open rewards programs, loyalty points, fan tokens, and most utility distributions.
Only turn Require Auth ON if you are running a restricted program: private beta access, whitelist-only distribution, or a compliance-gated program where you need to screen each recipient before they can hold your token. When it is on, you must authorize every holder’s wallet individually before they can receive tokens — which is a significant operational overhead for any large program.
After this, your wallet is the issuer. Token balances appear when you send tokens to holders who have authorized your instrument. OnRamp prepares each request; you review and sign in your wallet.