GetPaidX docs

The end-user manual for public and signed-in product features.

Search docs

Keyword search across docs titles, summaries, headings, and curated keywords.

Profiles and PresenceUpdated 2026-05-18

Profile Share, AI QR, and Gallery

How profile and workspace QR sharing works, how AI QR generation differs from classic QR output, and how profile/public gallery visibility behaves.

Profile Share, AI QR, and Gallery

Where you see this in the app

Profile sharing appears from profile and workspace share controls. The same share system is also reused by the /onboard/share flow for business-card and social-share QR artwork.

The most common entry points are:

Entry pointWhat it is for
Profile share dialogShare a GetPaidX profile, featured workspace, external website, or temporary custom URL
/onboard/shareGuided setup for profile or website QR assets
/o/shareShort public alias that redirects to /onboard/share while preserving referral and UTM params
Profile AI QR galleryShows successful QR artwork that the owner has not hidden

Share destinations

The profile share dialog can encode different destinations depending on the user goal.

DestinationBest use
GetPaidX profile URLSend people to your public identity and profile workspace
Workspace permalinkSend people directly toward the featured workspace route
External websiteUse a website already saved on your profile
Temporary custom URLCreate one share asset for a specific campaign without changing profile settings

The generated QR image can be used digitally or in print. For printed business cards, stickers, flyers, or thermal-printer labels, scan the exported image before distribution.

Classic QR vs AI QR

Classic QR output keeps the code visually direct and predictable. AI QR output makes a styled image while preserving the encoded destination.

The current AI modes are:

ModeWhat to expect
Art / ModernUses the built-in OpenAI QR-art template. The prompt field is optional and acts as one-time extra direction for that generation.
ControlNetUses the direct prompt-driven ControlNet flow and requires a meaningful prompt before generation.

Both modes keep the share destination underneath the artwork. Styling can change, but the encoded URL is still the important payload.

Reference images and prompts

AI QR generation can use an optional reference image.

Users can:

  • upload an image from the device,
  • use the browser camera/file picker when available,
  • paste a direct image URL.

GetPaidX treats reference images as generation inputs, not as profile media. Uploaded or captured images are used transiently for the provider request and are not saved as gallery items.

For Art / Modern, leaving the prompt blank is valid. Add text only when you want to steer the specific scene or style. For ControlNet, the prompt is the main instruction and cannot be empty.

Scan checks, credits, and status

AI QR generation uses AI credits when a generation succeeds.

The user-facing states usually mean:

StateMeaning
GeneratingThe provider accepted the request and the app is waiting for a result
QR scan check passedThe server-side scanability check recognized the intended payload
FailedThe provider or scan process could not produce a usable result
ExpiredA temporary or legacy image is no longer available

If a scan check fails, create a cleaner QR with stronger contrast, a larger code area, or less visual clutter around the code.

Successful AI QR generations can appear in the owner's profile gallery when they are public and not hidden.

Owners can hide or show generated items from the profile gallery controls. Public, non-hidden AI QR items can also appear in the recent cross-user gallery on /onboard/share.

The public gallery is for inspiration and proof of what the QR-art feature can produce. It is not a private archive of every generation.

Related docs

    Profile Share, AI QR, and Gallery | GetPaidX docs | GetPaidX