I am implementing an Android app and I want to use the Directions API but I get this error when I try the HTTP GET Request:
{
"error_message" : "You must enable Billing on the Google Cloud Project at https://console.cloud.google.com/project/_/billing/enable Learn more at https://developers.google.com/maps/gmp-get-started",
"routes" : [],
"status" : "REQUEST_DENIED"
}
I know I have to enable billing, what I want to know is the limits. I am doing this app for student purposes so this app won't be used by any users but me. I wanna know If it's safe to put my credit card if there is a limit that you can use it for free. I know there is a free trial but after that any request, even one will cost me money??
Thank you.
If you are using the free GCP tier, the free trial ends when you use all of your credit, or after 3 months, whichever happens first.
At that time, the following conditions apply:
You must upgrade to a paid account to continue using Google Cloud.
All resources you created during the trial are stopped.
Any data you stored in Compute Engine is lost.
Your account enters a 30-day grace period, during which you can recover resources and data you stored in any Google Cloud services during the trial period.
You might receive a message stating that your account has been canceled, which only indicates that your account has been suspended to prevent charges.
If you want to manage your expenses you may set up budget alerts https://cloud.google.com/billing/docs/how-to/budgets#create-budget also you can set up capping usage for it https://cloud.google.com/apis/docs/capping-api-usage
Related
Testing out the platform I was running on both a developer account and a Trial Business Pro account until I purchased a standard plan.
Up until I purchased the standard plan, envelope statuses would update by the second and the functionality built with the Apex Toolkit was working well.
Once changing to the standard paid plan, envelopes statuses take 10-15 minutes to update and some functionality is not working.
My question is:
Do the different plans have different status updating times in Salesforce?
Is functionality of the Apex Toolkit limited between the different plans?
Does the Connect option (which is missing now) have anything to do with the above?
Thanks!
They do not. Writeback to Salesforce takes place via DocuSign Connect. Some plans don't support Connect out of the box but the actual writeback times / delays do not differ between account plan types.
Indirectly, the only way that a plan type can interfere with an API call that worked on another plan type is if it had entitlement to a feature that your new plan does not, IE: The ability to allow Comments, to set recipient signing language, to set envelopeID Stamp Control, etc...
I would highly suspect that it does -- in fact I'm a little surprised that your writebacks are happening at all if you don't have Connect enabled. Salesforce adds an object reference IE: Opportunity / AccountIds to the envelope's custom fields on send. When Connect sees these fields, it knows to write back to that specific object. Without Connect enabled and configured it shouldn't be able to process these writebacks at all.
I think you should have a conversation with your Account Rep first regarding Connect entitlement, then you can reconnect your Salesforce instances to the updated DocuSign account which is something that we can help you with.
Regards,
Matt
To implement a free plan for a subscription, I have created a plan with a monthly charge of $0.
Is this the correct way to subscribe users to a free plan so that they don't have to pay?
Will users still get invoices when they are subscribed to a free plan? If so, how can I avoid sending invoices to those subscribed to the free plan?
Stripe Subscriptions are designed to manage billing and payments, rather than "tracking who is using a product". An "active" Subscription in Stripe is one that is being paid for, rather than one that is "being actively used".
You could conceivably set up a Subscription with an indefinite free trial, but really, you're doing a bunch of work to keep updating it to "remain free". I'd suggest taking a look at what you are actually trying to accomplish, because you're probably trying to track a user of your services, rather than track that a user doesn't pay you anything.
If you want to track a subscription with a zero plan on Stripe it will of course work. I use zero plans all the time.
All the invoices will be generated each month but will have a zero value which means they will automatically be marked as paid.
Invoice was finalized and automatically marked as paid because the amount due was 0.00kr
I am using custom accounts with custom integration so there is no automatic email going out from stripe for me, but I do receive the entire stack of events like I would any normal invoice which i have to deal with.
The event progression is: Invoice created -> finalized -> paid -> changed. Although instant the webhook events all come in.
There is no issue with zero plans, everything shows up in the Stripe admin and works just like any subscription. You can start out with a free plan and upgrade them later - the payment information is gathered and can be charged later so it is all good.
I am using Azure AD Graph API and Microsoft Graph API to communicate the Azure Active Directory . My code parses response received from API and compares error message in some specific error scenarios . Recently I observed one my scenario was failing due to change in response message from the API. I am just curios how these changes are pushed by Microsoft . Are customers notified for these changes ? Are changes released region wise or customer wise ? My code is being used by mates in other geographic reason also , they have not reported any failure till now.
For Example. Previously Error message for expired password was "Forced Password Change" now message is "Password is expired"
Are customers notified for changes ?
Once the service update is applied by Microsoft you will receive a notification if the update was successful or if it was not able to be applied. When any maintenance plan to happen all the partners and user receives notification about that. You could find here
Are changes released region wise or customer wise ?
Usually changes made on regionally. But sometimes data center wise also. But its very rare pointing to specific customer. Some small enhancement take place (Like yours) that's impact less on application and partner as well. In that case you may not receive any notification for that. Other then you would definitely receive mail concerning the issue. For more details you could take look on service life cycle policy
Currently our Trial Period is being handled in the back-end of our application and not handled by Stripe. Our devs are telling us this is because the Trial period can be abused by users by changing their subscription plan just before their trial runs out which allows them to restart their plan.
Is this possible?
That depends on your backend. At the beginning of the very first trial, the user can be marked by a "tiral_used" (or whatever) boolean field. Thus, even if they change their plan right before the end of the trial, your backend will check if this user has used the trial or not and it won't start another trial again.
Stripe handles the trial pretty good also.
I am trying to call the Azure billing rate card api. The call is happening successfully after the authentication because the status code is OK. But though I have a vm in the corresponding resource group and subscription, always getting response as:
{"value":[]}
Same is happening in case of azure billing usage api. I had seen one question asked for billing usage api but I have tried all the options mentioned like keep the duration for 3 months, don’t keep future date etc, yet there is no response”:
{"value":[],
nextLink:”https://….”}
Please let me know the issue could be abd because of which both rate card and usage api are not returning right data.
Thanks
You were right, I had the same problem and i resolved it on giving 'reader' persmission on my servie account in my subscription .
Thx a lot !