Skip to main content

Quickstart

Launch your first Hilt flow quickly, then decide how far you want to automate it.

This page is deliberately split into:

  • the fastest merchant launch path
  • the developer handoff after the merchant flow is live

Before you start​

  • a Hilt account with HiltPay enabled
  • a Solana wallet you want payments to settle to
  • one clear access outcome Examples: Telegram invite, Discord role/server access, redirect, download, paid unlock

In the dashboard these are called templates. In the API and CLI, the same objects are called products.

Merchant launch path​

1. Create a template​

In the merchant dashboard:

  1. Open Templates
  2. Choose an offer format
  3. Add a title, description, price, and payout wallet
  4. Set the amount in SOL or USDC if the flow is fixed-price
  5. Add branding if you want the hosted checkout to look merchant-owned from day one

2. Configure access and renewal​

Choose what happens after payment:

  • Telegram Invite-based or membership-oriented community access
  • Discord Paid server or role access
  • Redirect / Download Send buyers to a URL or unlock destination
  • Custom Manual or bespoke delivery logic

If the template is membership-based, also define:

  • the destination name the merchant should see later in members, receipts, and support
  • the billing interval in days
  • the grace period in days
  • any platform-specific delivery destination or saved automation override

For Telegram and Discord flows, buyer identity is handled in checkout with Connect Telegram or Connect Discord.

3. Preview the buyer journey​

Use the builder preview before publishing. Check:

  • the checkout headline and branding
  • the price and fee summary
  • the buyer identity step
  • the success state and final access handoff

Publishing gives you a hosted checkout URL like:

https://www.hilt.so/p/your-slug

Share that URL wherever the buyer enters the flow.

5. Run a tiny-value live payment​

Open the link as a buyer:

  1. connect a wallet
  2. connect Telegram or Discord if the flow uses a community format, or enter the buyer detail you requested for a custom or redirect flow
  3. approve the payment
  4. wait for Hilt to confirm the transaction

After confirmation you should see:

  • a recorded payment
  • a receipt
  • a member record if the template uses memberships

6. Verify the trail afterward​

Use:

  • Payments to inspect transaction state
  • Members to search by wallet, identity, or transaction
  • Receipts for proof and support context
  • Support to open or reply to structured tickets
  • Billing to inspect your Hilt plan and merchant totals

Developer handoff after the merchant flow is live​

Once the merchant workflow is working in the app, the usual next steps are:

  1. create an API key
  2. inspect the same live templates through the API as products
  3. use signed buyer handoff links if your bot or app already knows who the buyer is
  4. use memberships, receipts, and payment status routes for the operating trail
  5. use the CLI for fast support and verification checks

Start here next:

What to do if something feels off​

  • if the buyer paid but the UI is still catching up, keep the original payment_id and check status instead of asking them to pay again
  • if delivery failed but payment settled, retry delivery instead of replaying the payment
  • if the merchant setup is unclear, return to the template and clean the access destination before sending real traffic