To show a UPI QR code during a YouTube live stream, get the code for the account that should receive payments, then add its image to a streaming encoder that supports graphics. YouTube does not create or process the QR payment; the code is a visual overlay in the video, so you need to check its appearance and legibility before going live.
The practical workflow is to choose the receiving account, save its QR image, place it in your encoder scene, and inspect the outgoing preview. The exact controls depend on the encoder. Treat this as using an encoder’s documented graphics or overlay capability, not as enabling a special YouTube UPI feature.
Get the QR for the right receiving account
Start with the payment destination, not the broadcast. Find the QR in the UPI app, bank or payment provider for the account you intend to receive support. Confirm that it belongs to the correct account and that you know what viewers will see as the payee before you put it on screen. Do not reuse a code from an old poster or another account without checking it.
For a personal receiving QR, use the option supplied by the relevant app or provider. NPCI’s BHIM information explains that BHIM users can view a static QR in the profile and share or download it. The wording and controls in your own app may differ, so follow that provider’s current instructions. Save a clear image in a format your encoder can use, and keep an unchanged copy so you can replace the overlay if needed.
A merchant QR is a different arrangement. If you are accepting payments as a business through a merchant setup, use the QR supplied for that setup rather than presenting a personal QR as a merchant code. NPCI’s UPI FAQ says merchants need to partner with an acquiring bank, which provides the UPI infrastructure. If you are unsure which QR is appropriate, ask your bank or provider; an overlay cannot change the status or terms of the payment account behind it.
| QR context | Whose setup it represents | What to check before displaying it |
|---|---|---|
| Personal UPI QR | The personal account linked to the QR in the app or provider | The payee shown in the payment flow is the intended person or account |
| Merchant QR | A business arrangement supplied through the relevant provider or acquiring-bank setup | The code is the one issued for that merchant arrangement, and the business identity is described accurately |
This distinction matters when you name the QR on screen or in your stream description. Do not imply that YouTube has verified the payee or that adding a code makes a personal account into a merchant account. For a broader discussion of how to make a channel’s purpose and viewer support clear, see how to start a charity fundraiser on your YouTube channel.
Choose an encoder workflow with graphics
You need a way to compose an image over the video that is sent to YouTube. YouTube describes mobile, webcam and encoder workflows separately, and its guidance identifies an encoder as a route for adding overlays, graphics, audio and video. Its encoder setup guidance is a useful starting point when choosing a workflow. A phone or webcam app may be enough for a simple broadcast, but do not assume that every such app lets you add a custom QR image.
Check the current documentation for the encoder you plan to use. Look for an image, graphic, media or visual source that can remain visible as the scene plays, plus controls for position and size. You also need a preview of what the encoder is sending. Button names vary between products and versions, so rely on the chosen encoder’s help rather than expecting a universal sequence of menu clicks.
There is a trade-off between a simple, already familiar setup and a more configurable encoder workflow. A workflow that supports layered graphics gives you more control over the QR’s position and appearance, but also adds a scene element you must inspect and maintain. If you already run a loop or scheduled programme, consider how the QR will sit above that content and whether scene changes will keep it visible. This is similar to planning other visual elements in an always-on broadcast; what to look for in a cloud service for prerecorded YouTube livestreams covers separate operational questions around keeping a prerecorded channel running.
YouTube’s overlay and browser-source help documents overlay-related capability, including browser sources. It is not a built-in UPI QR function. Importing a saved QR image as a graphic is a practical way to use an encoder’s visual-source capability; the steps and supported formats are specific to the encoder.
Add the QR as an image source
Create or open the scene that will carry the programme you intend to broadcast. Add the QR image as a visual source using your encoder’s current image or graphic controls, then place it above the video in the scene’s layer order if the software uses layers. The imported image becomes part of the composed picture sent by the encoder. It does not change the payment destination or add a payment function to YouTube.
If the image appears blank, unexpectedly cropped or behind another source, check the selected file, layer order and source visibility. Make sure the QR has not been stretched so much that its square pattern becomes distorted. If the graphic has a solid background, consider whether that background makes it easier to distinguish against the content rather than trying to make the QR blend in.
The image should remain part of the intended scene when you switch between programme elements. If you use multiple scenes—for example, an opening card, a main loop and a closing card—decide whether the QR belongs on all of them or only some. Check each relevant scene rather than assuming an image added to one scene appears everywhere. For channels that play recorded material continuously, the guide to streaming relaxing flute music on YouTube 24/7 in India offers context on planning a loop; the QR overlay is a separate presentation layer.
Keep the source file somewhere you can find it again. If the receiving account changes, remove or replace the old image and repeat the checks. A stale QR is not just a layout issue: it could direct a viewer to an account you no longer intend to use. Avoid editing the QR pattern itself; change the surrounding label or the source image supplied by the payment provider instead.
Position and size it for legibility
A QR that looks large on your encoder canvas may appear small on a viewer’s phone. Leave enough area for the pattern to remain distinct, and avoid covering captions, faces, lyrics, product details or other information viewers need to follow. Place the code where it can be seen without becoming the main subject of the programme. There is no single size or corner that works for every video, screen and playback resolution.
Preserve the image’s square shape. Do not squeeze it into a wide rectangle or crop its edges; the quiet margin around a QR can be part of what makes it readable. Use a clear background and sufficient contrast between the pattern and its surroundings. Avoid transparency or decorative animation that makes the edges difficult to distinguish, and do not put a moving element across the code.
Think about what sits behind the overlay. A bright, busy scene can make a QR difficult to pick out even when its image is sharp. A plain panel behind it can help, but the panel should not obscure important programme content. If you add a label such as “Support this channel”, leave it outside the QR’s boundaries and use wording that accurately describes the receiving account.
Check the placement at the output resolution and aspect ratio you intend to stream. If you also publish clips or use a layout that may be cropped for another format, make sure that crop will not cut off the code—but do not assume the same overlay is suitable for every output. For more on how a continuous broadcast can be assembled from source material, see cloud transcoding for live streaming: what it is and how it works. That is a separate workflow; for the QR itself, the important test is whether the actual preview preserves a clear, undistorted image.
Test the outgoing preview before broadcasting
Before starting the public broadcast, inspect the stream preview in YouTube Live Control Room and, where practical, view it on a second device. YouTube’s live streaming encoder guidance recommends testing and previewing encoder streams. Look at the picture viewers will receive, not just the encoder canvas: scaling, compression, cropping or scene selection can change how an overlay appears.
If practical, use a second device to scan the QR from the preview. Confirm that the payment flow shows the intended payee, then stop before authorising any payment unless you genuinely mean to make one. This is a legibility and destination check, not proof that every viewer will be able to scan the code from every screen. A code can be clear on a desktop monitor and still be difficult to scan on a small phone or at a lower playback quality.
Use the preview check to catch both picture and workflow problems. Is the QR present in the scene that will actually go live? Does it remain visible while the video moves or changes? Is text around it readable? Does the code collide with captions or a platform interface element? If you have a scheduled start or a scene transition, inspect those states too. Make a small position or size adjustment, then check the preview again rather than relying on how the change looks in the editor alone.
YouTube’s encoder and browser-source guidance may not match every software version or available setup. If the QR image source is missing, consult the encoder’s current documentation and check that you are editing the scene used for the outgoing stream. You can also review the broader YouTube Live Control Room setup guidance for the current preview and stream workflow. Do not treat a successful preview as a guarantee that a scan or payment will work for every viewer.
Keep payment instructions clear and safe
Tell viewers what the QR is for and whose account is intended to receive the payment. If it is a personal QR, describe it as a personal account’s QR rather than calling it a merchant code. If it is a merchant QR, describe the business arrangement accurately. This helps viewers make an informed choice and gives them a chance to check the payee displayed by their own UPI app before proceeding.
Be explicit that viewers should never disclose a UPI PIN or OTP to you, to a moderator or in chat. NPCI’s fraud awareness guidance explains that scanning a QR code and entering a UPI PIN is for making a payment, not receiving one. A PIN entered after scanning authorises a payment from the person entering it; it is not needed to receive money. Do not ask for a PIN, OTP, screen recording or other private authentication detail to “confirm” a contribution.
Keep instructions short enough to be understood while the programme continues. A label beside the image, a spoken reminder, a pinned message or a channel description can clarify the purpose, but each should agree with the others. Tell viewers to check the payee and amount in their own payment app and proceed only if they intend to pay that recipient. Do not claim that YouTube has checked the destination or that the overlay itself confirms a payment.
There is a difference between making a QR visible and setting expectations around support. You can explain how voluntary support helps the channel, but do not promise a result or imply that payment is required to watch. If your content includes a fundraiser or a specific appeal, make the destination and purpose clear and check any applicable platform and payment-provider guidance yourself. An on-screen graphic cannot resolve questions about account ownership, merchant status or the terms of a payment service.
Review visibility during the stream
After the broadcast begins, check that the QR remains in the expected scene and that the outgoing picture has not changed in a way that makes it hard to read. A programme may switch scenes, change crops or replace a background; a graphic that was legible over one segment may be lost over another. If you have a moderator or a separate viewing device available, ask them to watch the actual stream presentation and report whether the code is still visible.
For an always-on channel, review the overlay as part of routine content checks. Confirm that the image has not been hidden during a scene change and that the surrounding message still describes the intended account. If you update the QR, test the replacement before relying on it and remove old copies from scenes or graphics that may still be used. A brief review is more useful than assuming an earlier test covers every later change.
If you cannot keep an encoder running from your own computer, the burden of maintaining the broadcast becomes a separate issue from obtaining and displaying the QR. StreamNeo turns an uploaded video into a YouTube live stream, so you can switch off your computer while the broadcast continues; that can remove the need to leave a personal machine running, but it does not select, verify or manage your UPI destination. You still need to provide the correct QR artwork and check how it appears in the broadcast workflow you use.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Does YouTube make a UPI QR code for my live stream?
No. Get the QR from the relevant UPI app, bank or payment provider for the account meant to receive payment. Add it to the video as an encoder graphic; YouTube does not generate, verify or process the UPI QR payment.
Can I add the QR from a phone or webcam app?
Only if the app or workflow provides a way to add a custom graphic or image. YouTube distinguishes mobile, webcam and encoder routes, and you should check the current documentation for the tool you plan to use rather than assume a QR overlay control is available.
How do I know whether viewers can scan it?
Inspect the outgoing preview and, where practical, try scanning it from a second device. Check that the code is square, clear, not cropped and large enough in the preview, while remembering that different screens and playback conditions can affect legibility.
Should a viewer enter a UPI PIN after scanning?
A viewer should never disclose their PIN or OTP to you or anyone in chat. NPCI explains that entering a UPI PIN after scanning is for making a payment, not receiving one, so viewers should check the payee and amount and proceed only if they intend to pay.