To show a BharatPe or PhonePe QR code during a YouTube live stream, get the current receiving QR from the relevant merchant account, add it as an image overlay in your encoder, and inspect YouTube’s outgoing preview from a second device. This checks both that the code can be read at its on-screen size and that it points to the intended payee.
The provider-specific steps for exporting either QR are not established by the sources used here, and YouTube does not document a payment-QR setup. Treat this as a general encoder workflow: use an image you have obtained from the official account, test it before asking viewers to pay, and do not imply that a QR display guarantees a successful payment.
Get the current QR from the merchant account
Start with the account that should receive the payment. Open the official merchant app or account for BharatPe or PhonePe and find the current QR intended for receiving payments. The precise app screens and export navigation can change, and they were not verified for this guide. Do not rely on a menu name or sequence copied from an old tutorial; look for the provider’s current instructions or ask its support if you cannot identify the right code.
Use the merchant QR associated with the receiving account, rather than an image saved from an unrelated post or another person’s screen. If the account offers more than one QR or receiving method, check which one is meant for the payments you want to accept. Keep a note of the payee or account identity you expect a payer to see, so you have something to compare against during the preview check.
BharatPe’s Google Play listing for BharatPe for Business describes its single merchant QR as accepting payments from PhonePe, Google Pay, Paytm, BHIM, Amazon UPI and other banking apps. That is the listing’s claim, not a guarantee that every account, QR or transaction will work. PhonePe’s general terms and UPI terms describe QR-based UPI payments, including paying a merchant using a QR through the PhonePe app. These documents do not establish a comparison of fees, settlement speed or suitability for a livestream.
The useful choice is the account you want to receive money into, not a presumed winner between app brands. If viewers may use different payment apps, BharatPe’s listing makes an explicit cross-app claim for its merchant QR; the sources here establish PhonePe’s QR-based UPI capability but do not set out an equivalent cross-app claim. Check the conditions that apply to your own account and make sure the displayed code is the one the provider currently associates with it.
A saved QR image can become stale if you change accounts or replace the receiving method. When you prepare the stream again after a change, retrieve the current image rather than assuming the old overlay is still correct. Do not alter or redraw the code to make it look neater: preserve the QR pattern and any identifying details supplied with it.
Prepare the QR image for the stream
Save or export the QR using the provider’s official account workflow, if available. The source material for this article does not establish where either app places that function or what its current button labels are. If you cannot find a way to save an image, consult the current official help for that provider instead of guessing at a sequence or capturing a code from a screen whose account identity you cannot confirm.
Keep an unmodified original. Make a separate working copy only if your encoder needs a particular image format or transparent canvas. A QR needs its contrasting light and dark modules intact, with a clear margin around the code; do not crop tightly into the pattern, blur it, put text over it, or add decorative effects that merge with its edges. If the provider includes a logo or payee label, retain it unless you have a clear, safe reason to prepare a separate version.
Before importing the image, view it at ordinary size on a phone or computer. Check that the entire code is visible and not clipped, that the light areas have not become transparent against a busy background, and that the image opens without a password or temporary sharing link. Keep the source file in a place you can find again when you update the broadcast. A simple name such as merchant-qr-current is more useful than a sequence of vague filenames, but do not put account secrets in the filename.
The QR is a payment destination, so treat it with the same care as other payment details. Share only the code you intend viewers to use. Never ask viewers to disclose a UPI PIN, one-time password, bank login or other banking credential in chat or as a condition of payment. A payer should complete any payment in their own trusted payment app and verify the details shown there.
If you are building a longer-running channel around a video loop, the image is only one part of the broadcast composition. The practical distinction between a local playback setup and a cloud-based broadcast is explained in how cloud video streaming works; whichever route you use, the overlay still needs a clear source image and a real preview check.
Add the QR as an encoder overlay
YouTube lists encoders as one way to livestream and notes they are commonly used for streams with overlays and hardware. That makes an encoder the natural route when you want a fixed QR image visible over a video or other programme content. YouTube’s documentation describes live-streaming and overlays in general, not a payment QR feature or provider-specific instructions.
In your encoder, add the saved image as an image source or overlay, then position it in the programme canvas. The wording differs between encoder applications, so follow the documentation for the software you are actually using rather than expecting a universal menu name. If your encoder provides layers or source ordering, keep the QR above the background video but below any graphic that must remain legible. Avoid making the QR part of the underlying video unless you want it permanently baked into that file and can still adjust it later.
Check how the overlay behaves when you switch scenes, playlists or video sources. Some layouts may contain a separate scene for a holding screen or a changeover. If the QR is meant to stay visible throughout, confirm that it appears in every relevant layout; if it is only appropriate for particular content, make its visibility deliberate rather than accidental. This is especially worth checking for a continuous programme that changes material across the day, as in a day-and-night playlist schedule.
Do not assume that seeing the image in the encoder’s canvas means viewers are receiving it. The local canvas shows a composition before the signal reaches YouTube. A separate preview from the outgoing stream is needed to catch a missing source, an unexpected crop, a wrong scene or a layout that differs from what you intended to broadcast.
Size and place it for clear viewing
A QR must be large enough to identify as a code and scan at the size viewers actually see, but it should not dominate the programme. There is no universal pixel size that guarantees a scan: the result depends on the source image, stream resolution, the viewer’s screen, video scaling, compression, distance and the scanning device. Decide by testing your own outgoing picture on a second device, not by treating a number from another setup as a promise.
Choose a quiet part of the frame where the code will not cover a face, lyrics, subtitles, news text, product details or other information viewers need. A lower corner may work for a static devotional or ambience image, but it may be a poor choice if the scene places important material there. For a news loop, keep the code clear of tickers and captions; for a study stream, do not cover a timer, notes or the area viewers are meant to follow.
Give the image a plain, contrasting background if the scene behind it is detailed. Preserve clear space around all four sides of the QR so the camera can distinguish its boundary from the video. Avoid moving, pulsing or rotating the code. If you add a short label such as “Pay by UPI”, keep it outside the code and ensure it does not crowd the image or suggest a payment destination different from the one the QR resolves to.
When you resize, scale the image proportionally. Stretching it wider or taller changes the geometry of the code and can make it harder to scan. Do not judge legibility only on your editing monitor: viewers may watch in a small mobile player, with the stream fit to a vertical or horizontal screen, or through a connection that reduces picture detail. YouTube’s live-stream help covers encoder-based streaming, but it does not specify a QR overlay size.
If a long video or playlist forms the background, its encoding and scaling affect the appearance of both content and overlay. The guidance on encoding a 4K video for a live loop without oversized files is relevant to the source video, though no video setting substitutes for checking the actual QR in the outgoing preview.
Check the outgoing preview with a second device
Before going live, open the outgoing preview using a second device, such as a phone that is not running the encoder. View the stream as a viewer would, at the intended orientation and a typical size. This is a practical check, not a claim that the test proves every viewer will be able to scan: screens, connections, camera focus and viewing distance vary.
First confirm the basic picture. Is the QR visible in the outgoing feed, rather than only in the encoder canvas? Is its edge intact, its contrast clear, and the whole code inside the frame? Does it remain clear when the scene changes? If the image is too small or blends into the background, adjust its size or backing, then inspect the outgoing preview again.
Next, use a second phone or a trusted payment app to scan from the preview device’s screen, if you can do so without initiating a payment. Check that the scan resolves to the intended payee or receiving account. If the app requires you to continue to a payment screen, stop before authorising anything. Do not make a test payment merely to prove that the overlay works; if you need to confirm account operation, follow the provider’s official guidance for a safe test.
Use a separate device for this check because the phone showing the stream cannot easily scan its own display. A screenshot can help you inspect a frozen frame, but it does not show whether a code remains visible during transitions or whether the live player is scaling the image differently. The outgoing preview is the relevant view because it reflects what has made it through the broadcast path.
If the preview is not available yet, do not treat that as evidence that the code works. Resolve the encoder or YouTube preview issue, or postpone displaying a payment request until you can see the outgoing result. YouTube documents encoder streaming as a method for broadcasting; it does not verify the merchant QR or the receiving account for you.
Confirm the receiving destination before going live
A readable code can still point to the wrong destination. Compare the identity shown after scanning with the payee or account you recorded when retrieving the QR. Check the spelling and relevant account details presented by the payment app before proceeding. If the details do not match, remove the overlay and return to the official merchant account to obtain the correct current code.
This check matters when several people share access to a channel or when assets have been reused from an earlier broadcast. A QR file in a shared graphics folder could belong to an old campaign, a different branch or a former receiving account. Keep a clear process for who confirms the destination, particularly if someone else schedules the stream while you manage the payment account.
The QR check does not confirm that a particular payment will be accepted, credited or settled. Those outcomes depend on the payment service, account status, payer’s app and transaction conditions. If a viewer reports a problem, direct them to the official payment provider’s support route and avoid asking them to post transaction credentials or private account information in public chat.
YouTube’s external-links policy applies to livestreams and prohibits links that direct users to prohibited destinations, including phishing sites. The policy is about links and destinations; the cited material does not make a specific determination about every ordinary payment QR overlay. Do not claim YouTube has approved your QR. Review the current YouTube external links policy and other applicable rules, and represent the payment request plainly rather than impersonating YouTube or a third party.
Some viewers may prefer YouTube’s own earning features where they are available. YouTube lists ads, Super Chat and Super Stickers, and channel memberships as live-stream earning options, subject to eligibility and settings. These are not equivalent to direct UPI payments, and availability should be checked in the channel’s current tools. A description or chat link can also be useful, but YouTube says links are clickable in horizontal live chat and non-clickable in the vertical live feed in the mobile app; check its live-chat link guidance before relying on a link as an alternative.
Review QR visibility during the broadcast
Once live, check the stream from a viewer-facing device again. A pre-broadcast check confirms the starting composition, but a later scene change, reconnect or manual adjustment can alter what viewers see. Keep the preview device available and make a quick visual check after you change scenes or replace the underlying video.
If the QR is intended to remain on screen, confirm it is still present and unobstructed. If it is meant to appear only during a particular segment, make sure it is hidden at other times and that the transition does not leave it stuck over content where it is confusing. Avoid repeatedly changing its size or position while viewers are trying to scan; a stable code is easier to frame with a camera.
For a 24/7 channel, a computer-based encoder may require your computer and streaming setup to remain available. If that is the part of the workflow that has failed you overnight, StreamNeo removes the need to leave your own computer running for a file-based YouTube broadcast, while you still need to supply and verify the QR image and check what viewers receive. It does not validate payment details, and the broadcast remains YouTube-only.
Keep a simple record of which QR image is active and who confirmed the receiving destination. When the merchant account changes, replace the image, repeat the scan check from the outgoing preview and update any related labels. Do not assume that a code which scanned correctly in an earlier broadcast remains current indefinitely.
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
Can I display a BharatPe or PhonePe QR directly in YouTube?
YouTube’s help documents encoder-based livestreaming and overlays generally, not a payment-QR setup. For an encoder stream, add the merchant QR as an image source and verify the outgoing preview; do not describe this as a YouTube-specific QR feature.
Where do I download the QR from BharatPe or PhonePe?
Use the current official merchant account or app instructions for the receiving account. The provider-specific export navigation was not established by the sources used here, so avoid relying on guessed menu names or outdated screenshots.
Does a visible QR guarantee that viewers can pay?
No. A visible, scan-readable code does not guarantee that a payment will be accepted or credited. Check the payee shown after scanning, and let viewers complete payment only in their trusted payment app without sharing a PIN, OTP or banking credentials.
Can viewers scan the QR from any screen?
It depends on the viewer’s device, stream display size, image clarity and payment app. Test from a second device against the outgoing preview, but treat that as a practical check rather than a guarantee for every viewer.