I have created braintree sandbox test account.I want to use Braintree MarketPlace feature, In Order to user that functionality account must created US account. How to check and change my account to Us, or i have to create new one ?
Full disclosure: I work at Braintree. If you have any further questions, feel free to contact
support.
You cannot change the country associated with a Braintree Sandbox. If you would like to test the Marketplace functionality within a Sandbox, though, you'll have to sign up for a new Sandbox account, this time ensuring that you choose the United States for your country.
Related
I created a new google developer account as a organization type for our company.
When I paid $25 to create account, a new payment profile was automatically created as a individual.
In order for me to upload the app to the store, I need to authenticate myself, but they required for my personal information, not my company's information.
I think it's because my payment profile that I paid $25 to create developer account is a individual type.
I contacted the Google payment team.
But they said you can create a new payment profile on the play console.
I said I knew that, and I wanted to know how to identify our company on this account.
Then, they say it's not our job and they transfer this issue to the team.
I've been repeating this for two weeks.
How can I create a payment profile a business type when I create developer account?
Google play console is requesting to verify my identity.
The problem is that the verification form is asking for an organization info and docs while the account is for individual and that is provided in the account details screen.
So what am I missing? Where to go? Or how to contact google support?
I had this after emailing googleplay-developer-support#google.com. Solution: Your payment profile shouldn't be set as organization if your developer profile is set to individual and vice-versa.
Per checking, the payments profile associated with your account is set as an organization. You may choose to verify your account as an organization with the following documents that our system accepts: Certificate of Organization, and a valid ID of the organization's Official Representative.
If you would like to verify as an individual and change the entity type on your payments profile, you would have to create a new account in order to change from organization to individual. You may view your payments profile via pay.google.com
To change the entity type on your Payment Profile, it would need to be deleted and created again. Since a Play Console account can only be associated with one Payment Profile, it will need to be deleted and recreated as well.
To resolve the issue, we can close your Play Console account and refund the registration fee. Then, you can delete your payment profile at pay.google.com before you sign-up for a new Play Developer account. To proceed, please provide confirmation by responding with “I confirm to have my Play Console Developer account closed and have its registration fee refunded.” Also, please remove the existing draft app from the Developer account
I had this issue recently and it turned out it was because I had an old Payment Profile with Account Type of 'Organisation'.
You need to go here: https://pay.google.com/gp/w/u/0/home/settings
Personally, I had two payment profiles; one was for an Individual and one was for an Organisation. Maybe the Organisation one was the default or whatever.
In the end I managed to close that payment profile and create a new developer account after having the first one refunded.
There were a few emails to Google Support going back and forth but that solved it in the end and now I have an app on the Play Store.
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.
We are currently attempting to publish an App on the Google Marketplace (aka Chrome Web Store).
My boss has paid the $5 developer fee using his Gsuite account, and when I log in to publish the app, it keeps requesting the $5 fee to be paid. We are both part of the same GSuite domain (rulerr.com). I'm guessing this means the payment is tied to his account specifically? Is there any way to get this tied to our Gsuite domain?
As a result of the way this works, if I end up publishing using my account can anyone delegated from my domain modify it? If I was to go on vacation/sick leave/move on to another company then noone in my organization would be able to modify the App details?
Would adding a shared mailbox account specifically for marketplace registration alleviate this issue?
Laurie,
You can create a Google Group and use that as the owner of your app.
https://developer.chrome.com/webstore/publish#set-up-group-publishing
Any member of that group will then be able to publish. (when they have paid the 5$ fee)
To be able test any implementation of Android Market licensing (e.g. LVL, In-app Billing), Google advises to create a Google Checkout test account, since the developer cannot buy from himself using his own Google Checkout account.
Sounds great except that the test account must use a real credit card.
Which begs the question: How is this different from a normal account? What is the advantage of a test account over a normal account?
The test account does not have to be associated with the google checkout account. The publisher can have his/her google checkout account set up against the android market account. And as a developer, you can have a test account created.
Test account holders can test the application for LVL and in-app purchasing, etc only if the application is uploaded on the developer console. It does not have to published. But it has to uploaded and activated and saved.
So, it's not true that the test account holder has to have his/her financial details registered with the Google servers. Only the publisher has to do that. And the publisher can add as many test account holders as he/she desires. The publisher will provide a publishing key and that's all the developers need to implement/test their code.
Look for documentation on Google developer site. It explains well.
HTH.
You don't need a separate test account. That's only if you want to include others as testers. Your own publisher account is just fine. If you set the LVL response in your developer account to, say "UNLICENSED" for testing purposes, then only the devices that are set up with that Google account will get this test response.