Help
The short version: payment links are wallet to wallet; campaign pools and drop pots are held by a BegFi payout wallet until paid out; nothing here is a promise of a return.
Four ways to move crypto with a link: a beg page, a Pay Link for an exact amount, a campaign that pays people to post, and a drop (giveaway) with a fixed prize. One wallet, one username, one dashboard.
Depends on the product, and the difference matters. Beg pages, tips and Pay Links move money straight from the payer's wallet to the receiver's. BegFi never holds those funds and cannot reverse a transaction. Campaign pools and drop pots are different: they are sent to a BegFi payout wallet and stay there until they are paid out to earners and claimers.
The funder sends the pot to the BegFi payout wallet and registers the drop. A claim is accepted only if the pot still covers one whole prize and the cap has room. The claim takes a lease so it cannot be paid twice, and the prize is sent automatically after the transaction is sent. The claim page shows the transaction hash.
Three honest reasons: the cap was reached, the pot no longer covers a whole prize, or the drop was paused or ended. A fourth is operational: the payout wallet can be paused automatically when reconciliation finds it holds less than it owes. Transparency always shows that switch state.
It stays in the BegFi payout wallet. There is no automatic refund today, and no button that sends it back, so fund only what you intend to give away. This is a known limitation, stated on the drop page, the footer and in the docs rather than hidden behind a promise.
A campaign has a daily budget and a rule for a valid post. Qualifying submissions are paid automatically from the campaign's pool, once per wallet per campaign per day. A campaign pays in its own token, at its own decimals; the campaign page shows the pool remaining and who was paid.
Campaign and drop payouts are automatic, so they do not wait for a button. The Claim button exists for approved work in BegFi's original pool that has not been paid yet. The dashboard shows it only when there is something to claim.
One prize per wallet and one per verified X account, up to the cap, while the pot covers the prize. The site checks the wallet and, when a handle is verified, the X account. It does not use device fingerprinting: shared phones and shared networks were flagging honest people.
That the account on your profile proved it controls the handle by posting a one-use code from that account. The tick is tied to the handle it was proved against: change the handle and the tick goes with it.
No. $BEGFI is the token the site is named after, on Robinhood Chain. Beg pages, Pay Links and campaigns all work without holding it, and a campaign can pay in its own token. The address is pinned in the app so nobody has to trust a link.
Because the read failed. A zero would be a statement about your money; unavailable is a statement about the database. The site does not turn a failed read into a number.
Settings has a visibility switch. Hiding removes your profile page from public view and takes you off the leaderboards and the sitemap. Your pay links keep working; they stop showing your name and avatar. You can turn it back on at any time.
A payout that should have landed has a transaction hash on its page or in your dashboard. Include it when you report the problem: a hash can be checked against the chain, a description cannot. The public books show the payout wallet, what is owed and whether payouts are paused.
Check the books first — it answers most “why didn’t I get paid” questions.