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.

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.

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 plans. Included at no extra charge on Business and Enterprise plans.

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 signed the AccountSet transaction in Xaman, the platform has verified the issuer wallet has sufficient XRP funding (minimum 12 XRP), and the bond is now open for investor subscriptions. The bond page is publicly accessible and listed in the marketplace.
• 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 XRPL reserve requirements and transaction fees. The minimum to operate as an issuer is approximately 12 XRP, though this may vary with XRPL network reserve changes.

See the Wallet & Security section for full setup instructions.

Creating Your Token — Step by Step

1. Create an accountSign up at onrampdlt.io with your email address. Verify your email and log in to the dashboard.
2. 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.
3. Register your issuer walletIn the dashboard, navigate to Issuer Wallet and enter your Xaman XRPL r-address. The platform will construct an AccountSet transaction and send it to Xaman for you to sign. This enables DefaultRipple on your account, which is required for token distribution.
4. Configure your tokenEnter your token name, symbol, and total supply. Review all settings carefully — some token parameters cannot be changed after issuance.
5. 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.
6. 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.

1. Register and fund your issuer walletIn the dashboard, register your Xaman XRPL r-address as your issuer wallet. Fund it with at least 12 XRP before proceeding — the platform checks your live balance before allowing activation. The dashboard shows a real-time balance indicator.
2. Enable token issuance (one-time)The platform will generate an AccountSet transaction with SetFlag 8 (DefaultRipple). Copy the payload and import it into Xaman via Transaction Import. Sign it. This is a one-time step that enables your wallet to issue tokens to investors.
3. 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.
4. 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.
5. Activate the bondClick Activate in your bond dashboard. The platform verifies your wallet balance meets the minimum. It then generates a Xaman QR code for the AccountSet transaction. Scan it with your Xaman app and sign. Once confirmed on-chain, the bond status moves to Active, the full payment schedule is generated, and your bond page goes live in the marketplace.
6. Share your bond pageThe dashboard provides a shareable link to your bond detail page at onrampdlt.io/bonds/{id}. Investors can view terms, calculate returns, and subscribe directly from that page.
7. Distribute tokens and rewardsAfter investors subscribe, use the Xaman Payloads section in your dashboard to send bond tokens and XRP rewards. The platform generates batch payment transactions for you to sign in Xaman — one signing covers all 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. Activation requires signing one AccountSet transaction on the XRP Ledger.

What activation does on the blockchain

Activating a bond signs an AccountSet transaction with SetFlag: 8 (DefaultRipple) on your issuer wallet. DefaultRipple is an XRPL account flag that allows bond tokens issued from your wallet to ripple — that is, to be transferred between investor wallets. Without DefaultRipple enabled, trust line transfers to investors will fail at the ledger level. This is a one-time, per-wallet operation. OnRampDLT constructs the transaction; you sign it in Xaman, Crossmark, or GemWallet. Your private keys never leave your device.

When to activate

Activate your bond after:

• The bond has been created and reviewed in Draft status
• Your issuer wallet is funded with at least 12 XRP (the platform verifies your live balance before allowing activation)
• All bond terms have been confirmed — activation is irreversible and bond parameters cannot be changed afterward

How to activate

1. Open your bond in the dashboard and click the Activate Bond button on the bond detail page.
2. The platform generates a Xaman QR code containing the AccountSet transaction (SetFlag 8).
3. Scan the QR code in your Xaman app (or use the deep link on mobile), review the transaction details, and sign.
4. Once the transaction is confirmed on the XRP Ledger, submit the transaction hash via the dashboard to complete activation.

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

1. 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.
2. 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.
3. Connect your XRPL walletYou will need a funded XRPL wallet (Xaman, Crossmark, or GemWallet) with sufficient XRP to cover the subscription amount plus XRPL transaction fees and trust line reserve (approximately 2 XRP per trust line).
4. 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.
5. 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.
6. Confirm your subscriptionSubmit your XRPL wallet address and the transaction hash from your payment. The platform verifies the transaction directly against the XRP Ledger — confirming the payment type, destination, sender, amount (within 2% tolerance), and that it settled successfully. Only after on-chain verification is your subscription recorded.
7. 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 transactions. All three are self-custodial — your private key is generated on your device and never transmitted. When registering a wallet, set wallet_type to the corresponding value.

• Xaman (formerly XUMM) — iOS and Android — wallet_type: "xaman". The primary wallet for QR-based transaction signing. Required for the bond activation QR flow. The platform generates a XAMAN payload with a QR code and deep link; the user reviews and signs in the app. Signing is also supported via XAMAN OAuth2/PKCE for embedded web-app wallet connection. Recommended for most users.
• Crossmark — Browser extension (desktop) — wallet_type: "crossmark". Uses an AccountSet + Memo challenge flow for authentication. The platform issues a one-time challenge; Crossmark signs an AccountSet transaction embedding that challenge in a memo; the server cryptographically verifies the transaction signature and derives the XRPL account address from the signing public key. Recommended for desktop-first issuers who prefer a browser-native experience.
• GemWallet — Browser extension (desktop) — wallet_type: "gemwallet". Registered as a valid wallet type for wallet management. The XAMAN QR flow is used for bond activation steps regardless of which wallet type you have registered.

Only classic r-addresses are supported. X-addresses (which start with X) are not compatible with the platform.

Setting Up Xaman

Xaman is the recommended wallet and the one used throughout this guide. Here is how to get started:

1. 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.
2. 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.
3. Fund your walletYour XRPL account requires a minimum base reserve (currently 1 XRP) to activate, plus 2 XRP per trust line. For issuer wallets, plan for at least 12 XRP to start.
4. 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 requires a 2 XRP reserve while active
• If a trust line has a zero balance, you can remove it and recover the 2 XRP 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 verifiable, timestamped record tied to the user’s account. For legal counsel and issuers, here is exactly what the platform collects and when.

Self-Certification (506(b) offerings)

Investors submit the following through the platform’s self-certification form. All data is stored in the kyc_documents table in Cloudflare D1:

• Full legal name
• Date of birth
• Full mailing address (street, city, state/province, postal code, country)
• Accreditation basis — one of: income ($200K+ individual / $300K+ joint), net_worth ($1M+ excluding primary residence), or professional (Series 7, 65, or 82 license holder)
• Timestamp and IP address of certification

On successful submission, kyc_status is set to verified and accredited_investor is set to true in the users table. This record is surfaced to the issuer on the bond detail page for their due diligence records.

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 & Platform Schema — For Legal Counsel

This section details exactly what data OnRampDLT stores about users, issuers, and investors. It is intended for legal counsel performing due diligence on the platform’s data handling.

Data Stored

• Users: Email address, hashed password (PBKDF2/SHA-256 — plaintext never stored), subscription tier, KYC status, accreditation status and basis, accreditation timestamp and IP, Stripe customer ID, account creation and last login timestamps, suspension status.
• Wallets: XRPL address (public on-chain data), wallet label, wallet type (xaman / crossmark / gemwallet), network (mainnet / testnet), default wallet flag, verification status, creation timestamp. Linked to user account.
• KYC Documents: Full name, date of birth, full address, accreditation basis, self-certification timestamp and IP, Stripe Identity session ID and verification status (if applicable). Linked to user account by user_id.
• Issuer Profiles: Company name, tagline, description, website URL, logo URL, LinkedIn URL, Twitter URL, verified/enhanced flags. Linked to user account.
• Bonds: All offering terms (name, symbol, description, face value, interest rate, duration, total raise, minimum investment, bond type), offering status, network, XRPL transaction hashes (AccountSet, TrustSet, tokens sent), subscription count and total, creation and update timestamps. Linked to user account (issuer).
• Bond Subscriptions: Investor XRPL address, subscription amount, payment transaction hash, status, creation timestamp. Linked to bond by bond_id. Note: investor user_id is not stored in subscriptions — subscriptions are keyed by XRPL wallet address.
• Bond Investors: Investor name, email, XRPL wallet address, commitment amount, unit count, status. Linked to bond by bond_id and user account by user_id.
• Bond Invites: Invitee email and name, invitation acceptance status, expiry, timestamps. Linked to bond and inviting user account.
• Audit Log: User ID, action type, target type and ID, metadata (JSON), IP address, timestamp. Written for team operations (invites, revocations) and admin actions. Not written for all user actions — admins can review the log through the admin backend.
• Transaction History: User ID, token ID, wallet address, action, XRPL transaction hash, ledger index, currency code, amount, status, error messages, network, timestamp.
• Team Members: Account owner ID, member user ID, invited email and name, role, status, invite token, invite expiry, acceptance timestamp. Enables Business/Enterprise accounts to add team members.
• Sessions: Session token table (reserved — JWT revocation is handled via Cloudflare KV, not this table).
• Email Verifications: User ID, verification token, expiry, verified timestamp. Used for email confirmation and password reset tokens.

Data NOT Stored

• Private keys or seed phrases — never requested, collected, or stored
• Payment card data — Stripe handles all payment processing; only Stripe customer ID is stored
• Government-issued ID documents — not collected by the platform
• Plaintext passwords — only PBKDF2/SHA-256 hashes with unique per-user salts
• XRPL transaction contents beyond metadata — private transaction details are on-chain and publicly verifiable

Data Retention & Deletion

All data is stored in Cloudflare D1 (SQLite) within Cloudflare’s infrastructure. JWT revocation tokens are stored in Cloudflare KV with automatic TTL expiry. For GDPR, CCPA, or other data deletion requests, contact support@onrampdlt.com. See the Privacy Policy for full retention schedules.

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.

1. 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.
2. Recipient opens the link — They land on a guided claim page at onrampdlt.io/claim.
3. 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.
4. Trust line (if needed) — If they don’t already have a trust line for your token, a TrustSet QR is shown for them to approve in Xaman. One-time step. If they already have one, this step is skipped entirely.
5. 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.
6. 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 queries gateway_balances directly from the XRPL for your issuer address and updates the platform record to match exactly what is outstanding on-chain. 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:

1. 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.
2. 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.
3. 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

Token Supply & Minting

FAQ — Investor Questions

FAQ — Legal & Compliance

FAQ — Investor Account Questions

FAQ — Technical Questions