What is the best way to create "Referral program" in Metaplex storefront?
A referral program works by inviting customers to become brand ambassadors. They join the referral marketing program and get a unique code or link to share with their network. so the referral program tracks the activity of a customers’ code or link. If someone purchases using it, the referrer will earn a reward.
Most likely you'll have to implement this yourself in a traditional web2 way with a database and backend with a login system.
When a user makes a purchase via web3 you could modify the purchase function to then also store a referer in your database upon purchase confirmation.
Then when a user logs in you could then refer to the database to see how many referals the user has generated for you and show them on a form of dashboard for them to see.
Unfortuantely do the to broad question in general I can't really give you much more of an elaborate answer than that currently.
Related
I have implemented a login feature in my app where a user can pay for subscription and have that subscription tied to their in-app login account by using the setObfuscatedAccoundId() method. However, in a scenario where the current user(user_A) makes a purchase, logs out of the app and a different user_B logs in, user_B is unable to purchase the same subscription as it has already been bought by user_A (as they share the same underlying Google Play account) even though I DON'T want these in-app accounts to be related at all. Currently, what happens is user_B gets a responses that states "You already own this item". So that makes me wonder:
Can we actually possibly use a single/the same underlying Play Store account to purchase the same subscription while logging in to an app with different user accounts?
Also, what would be an ideal design approach for a problem like this considering the limitation?
I am still a beginner at this and would really appreciate your inputs!
I'm beginner at this like you and may I was wrong but I think you can not do that because the subscriptions are saved in your google account and you can not buy same subscription you owned already.
An Customer ask me to implement it at his Webpage, because he don't have the technical Skills to do so.
I wonder, what's the right way to do this.
On other Google-Services (like Google Search Console) the User can sign into his account and grant me permissions as Guest (he invite me as guest to his account and gave me permissions).
This is a clean way to do, because If I stop working for this customer, he can easily remove the permissions of my login and all is fine.
But how does it work at Google ReCaptcha?
Looking forward to hear, how you solve this.
it better to use the user's credentials for this purpose, just take client's primary or secondary email (or create a email for the project) and make it base for everything that's needed for your project like recatcha, search-console etc. you can use it as long as you are working, and client can simply change n give the credentials to next developer and he can continue.
i am web developer and i face this situation many times, this is best solution in my opinion.
I’m trying to create a wallet for a user in Stripe. Other uses can donate into another user’s wallet and that user can withdraw the funds into their account. This account should remain untouched by the account owner and controlled by the software.
This will need to be seperate from the primary account which holds funds for subscriptions from users which the Stripe account owner can withdraw (income).
Is this possible with Stripe/Stripe Connect and can anyone point me in the right direction?
You'd indeed need to use Stripe Connect for this.
This isn't really a programming question so you likely won't find much help here. You should reach out Stripe's support directly at https://support.stripe.com/email and explain your business model with as much details as you can (who you are, who your users will be, where are you and they located, what would a sample transaction look like, etc.). They will be able to guide you and help you design your payment flow using Stripe's API.
You can create a wallet by using charge feature of stripe i.e. for nodeJs it is stripe.charges.create({}) function.
It may vary depending upon your language of choice. You can prompt the user to recharge his wallet and create a charge through which you can transfer the amount to the admin account use a parameter in your db to store the user's current wallet balance for each payment deduct the required amount from the said user's account and add it to the other user's account.
Click here for more details !
Cheers!
I have integrated Google sign-in in our application, I need to check whether the logged in user is a teacher or student ,Organisation(school) name and Grade... Is there any API to get these details from Google and how to get the details form Google.
Regarding whether a user is a student or a teacher, see this answer.
It's not possible to determine the grade or school name via the Classroom API. (Please add a feature request for this so we can judge whether it's something a lot of developers would find useful!)
My web app is helping small businesses create content for their business pages.
I want to add the ability for my users to promote their posts.
most of my users don't have an ads account.
I can think of two options:
ask them to create an ads account
ask them to give my user an advertiser privilege for their page and use my own ads account
is there a better, more automated solution than these two options? if not, which one is preferred?
You should ask them to create their own ad account.
Shared ad account owned by you woud make it impossible for your customers to choose different payment methods, currency, contact info and other. They also wouldn't be able to generate invoices, which may be crucial for business customers.
Also you won't need to handle your customers' expenses. On a shared account I can easily imagine a case where a customer is boosting posts using your app, but doesn't pay for it. In that case you would be the one to pay the Facebook, since you'd own a shared account and you couldn't leave it without money because of other customers using it.