Creator guide
How to sell digital products from your own website with UPI
Keep your website, add a product button, and let buyers open checkout from the page they are reading. Here is the setup, what customers see, and how to test it.
Can you sell a PDF from a website you already have?
Yes. You need a product listing, a way to collect payment, and a way to deliver the file after payment is confirmed. With Bondin, you publish the digital product once, then place its buy button on your own website. The button opens Bondin checkout in a modal over that page.
For example, a tutor can place a revision-notes button beneath a free lesson, or a designer can offer a template alongside a portfolio project. The surrounding page explains the product; Bondin handles checkout and access. You do not need to rebuild that website as a full online store for this flow.
The website must allow the Bondin JavaScript snippet. If your site cannot run custom scripts, use the product’s direct Bondin link instead. The embedded option is for a single product purchase, rather than a multi-product shopping cart.
Choose a direct link or an embedded buy button
Both options point to the same product. Using an embed does not create a second listing or a separate product price. Review the current digital-product fees and the total shown to the buyer before promoting either option.
| Where you are selling | Useful starting point | Buyer experience |
|---|---|---|
| Instagram bio, email or a message | Direct product link | The buyer opens the product page on Bondin. |
| Your own blog, portfolio or landing page | Embedded product button | The buyer opens checkout over your website. |
| A website builder that removes scripts | Direct product link | Checkout remains available through a normal link. |
1. Publish the product and get its website code
In Creator Studio, open Offers → Digital products. Create your product or open an existing one. Add the file, a clear title and description, and your price. Enable Public and save so customers can buy it.
Open the product’s Embed on website tab. Choose a short button label, such as “Get the ebook” or “Download the templates”. Use See the visitor experience to preview checkout, then choose Copy website code. Installation instructions are available on the same tab.
Each product has its own product ID in the snippet. Use the code generated for the product you are promoting so the button opens the right checkout.
2. Add the button to your website
Paste the generated code into a Custom HTML or Embed block that permits JavaScript. Put it near the product description and sample, where a visitor has enough information to decide. Publish the page and open its public URL to test it; an editor preview may not run external scripts.
The example below shows the structure. Replace the username and product ID placeholders with the values from your dashboard, or copy the complete generated snippet directly. Include the library script once per page, even when you have several Bondin buttons.
<script async src="https://bondin.io/embed/v1.js"></script>
<bondin-product
username="YOUR_USERNAME"
product-id="YOUR_PRODUCT_ID"
label="Get the ebook">
</bondin-product>What about WordPress, Webflow or a custom HTML site?
For a custom HTML site, place the snippet in the page where you want the button. Use an HTTPS website for the published integration. A developer testing locally should serve the page over HTTP localhost rather than double-clicking an HTML file.
WordPress offers a Custom HTML block, but whether scripts survive saving depends on your setup and permissions. WordPress.com also restricts some code by plan and hosting features. Confirm that your site permits script tags before choosing this route.
Webflow offers a Code Embed element on eligible Workspace or Site plans. Check the current plan requirements and test the published page. Other builders may place embeds in a restricted iframe, which can affect checkout size, payment permissions or opening links. A direct product link is a useful fallback when the builder cannot support the required behavior.
3. Check the experience your buyer gets
Clicking the button opens a checkout with the creator, product and price. Buyers enter their name and delivery email. They can leave the optional phone field closed, and they do not need a Bondin account. A coupon field is available when applicable.
Embedded digital-product payments use Razorpay. Buyers choose from the payment methods offered for their transaction, including UPI where available. A UPI app switch or bank verification may take them outside the browser temporarily, so test the return journey on a phone.
After the payment is confirmed by the server, checkout shows access to the purchased product. The purchase link is also sent by email so the buyer can return later. A successful payment is separate from the creator’s bank payout; your Payouts page shows the earnings and payout state.
4. Test before sending traffic
- Open the published page in a fresh browser session and on a phone. Check that the button loads without first visiting your Bondin page.
- Confirm the creator, product, price, buyer fee and total are correct. Try a valid coupon if you offer one.
- Enter a name and email while leaving the phone field empty. Check that the pay button becomes available.
- Test cancellation and returning to checkout, as well as payment confirmation and access to the correct file.
- Check the email delivery path. Keep a direct product link near the button for visitors who cannot use the embedded checkout.
- If you are using a test environment, confirm the backend is configured for Razorpay test mode. A sample website connected to live checkout can still create a real payment.
If the button does not work
| What you see | What to check |
|---|---|
| No button appears | Confirm the builder kept the script tag and test the published page. |
| Checkout says the product is unavailable | Check the username, product ID and saved Public setting. An archived product cannot accept new sales. |
| Checkout cannot load inside the website | Check script and iframe permissions, HTTPS and any site security policy; use the direct link while investigating. |
| Payment is confirmed but the download has not loaded | Retry loading access or use the emailed purchase link. Avoid paying again to retrieve the same purchase. |
Frequently asked questions
Can I sell an ebook from my own website using Bondin?
Yes. Publish the ebook as a digital product, open Embed on website, and add the generated button code to a website that permits JavaScript. Buyers open checkout over your page.
Do buyers need an account or phone number?
The embedded digital-product checkout supports guests. It asks for a name and delivery email; the phone number is optional.
Can customers pay with UPI?
Embedded checkout uses Razorpay and offers UPI where available for the transaction. Check the payment methods shown and test the app-switch and return experience on mobile.
Can I add several products to one page?
Yes. Add a separate bondin-product button for each product ID and include the shared library once. Each button opens an individual product checkout.
Can I use product, Support Me and Ask a Doubt buttons together?
Yes. All three use the same Bondin embed library. Include the script once and use the generated element for each button.
Does the embed work on every website builder?
It requires a published website that allows the script and checkout iframe. Builder plans, permissions and sandbox restrictions vary. Use a direct Bondin product link if your site cannot run the embed.
Does embedding change the product price or fees?
The embed uses the same product and applicable Bondin fees as the public checkout. Check the total shown to the buyer and the current Pricing page; the Support Me fee is not a digital-product fee quote.