How can charge additional variable amount to subscription any time on authorize.net?
Through subscription, fixed amount can be charged to user subscription, whether there is a way, we can charge variable amount to subscription at any day until subscription is active?
Suppose I set amount $20 on every 10th of month to be charged from customer through recurring billing. Suppose, now I want $10 to be charged to customer on 2nd of month for other reason through his subscription, whether there is API available for that additional money to be charged?
There is no way to do this with their ARB subscription API. You would need to combine CIM, which let's you create payment accounts on Authorize.Net's server, with your own payment engine. Then you can charge someone whatever you want, whenever you want, all while reducing your PCI scope.
Related
So I am using multiple resources in AWS. The charges make sense for most services. however, at every first day of the month, I am getting charged more than I should.
For example; charges for services such as, Aws active directory service, EC2, step function, the elastic search is normal throughout the day. as I can drill down daily charges for these services. but every first day of the month, AWS charging more than what it usually charges. For example; if the average charge for EC2 instances for the day is $5 then at every 1st date(let's say 1st January) of the month, the charges end up for EC2 instance somewhere around $15 and again on 2nd January charges would back normal to $5.
also, for the AWS Contact center telecommunication service, my usual charges for the day would be around $10. but again on the first day of the month, I am getting charged around $150. This is way more than what it charges on regular days.
I don't get this behavior. is it done on purpose or am I missing something?
Thanks.
This is Tax, which appears on the very first day of each month.
AWS is sending an invoice at the end of each month with the price of the EC2 instance and the number of used hours. Since the price fluctuates, which price is taken to compute the bill? The price at the end of the month, at the beginning of the month or the real price for each used hour?
Thanks
If you are using on-demand EC2 instances, the prices don't fluctuate. When AWS does reduce prices, the new pricing takes effect on a specific date and your bill should reflect the reduced prices as of that date.
There are some complexities in billing when you have credits or Reserved Instances, especially when you use multiple accounts with Organizations or Consolidated billing.
There are some products that have thresholds - for example, S3 standard storage gets cheaper the more you use - the first 50TB are $0.023/GB, the next 450 TB are $0.022/GB, etc.
I currently have an account with AWS and I am using the free tier which lasts for 12 months, and then all usage after this 12 month period on this account will be billed at the standard rate.
However I am still in initial testing with AWS so is it possible to create a new account and receive the 12 month free tier again or is it some how tied to the credit card/personal information so that a single user cannot receive it more than once?
Yes, it is possible to create a new account but not with the free benefits they will be able to track it via the Credit card and your Machine ID
To quote the AWS Policy it says
"You will not be eligible for the Offer if you or your organization create(s) more than one account to receive additional benefits under the Offer,You will be charged standard rates for use of AWS services if we determine that you are not eligible for the Offer."
All the information
https://aws.amazon.com/free/terms/
Therefore, you can only receive the AWS free tier once per your registered card , email address and MAC Address
They say there is always a monthly fee. But does it get charged as the month progresses or right away?
Amazon WorkSpaces is charged on a pro-rata basis.
So, if you run one for one week and turn it off, you'll be charged approximately one quarter of the monthly fee.
The first month's fee and the last month's fee are similarly pro-rated, based upon how long the WorkSpace was running.
There is no charge for creating a WorkSpace.
I am developing an architecture for push notifications using AWS SNS with APNS and GCM. The model that I am following is
Each user (not device) will have an SNS topic corresponding to it
Each user can have multiple devices
Create an platform application endpoint for each device
Subscribe the platform application endpoint to the topic belonging to the device's user
This way, when we have to send a notification to all the devices of a user, we need to call the publish method using the user's topicArn and all its devices should get the message.
However, by default AWS has a limit of 100,000 topics. If we are anticipating higher number of users like 1 million or say 10 million to be optimistic, is there any workaround for this approach?
Should I ask AWS to raise the limit beforehand? Do they raise limit to a number like 100 million easily? Is there any cost implication of most of them are not used in the beginning few months?
disclosure: I used to work on Amazon SNS
The architecture you propose is a common pattern within Amazon SNS and is sound.
You should ask for a topic limit increase. There is no cost implication for having a higher topic limit, even if you create the topics and don't use them. However, you will pay $0.50/million requests for each CreateTopic call, with the first 1 million requests being free per month.
When you submit the support ticket, please document your use case. It helps the team expedite your limit increase request.
We followed a similar model to OP's with one exception - as the number of users grew, so did the number of dead accounts. Face it, user retention poses a challenge. So you may want to come up with a topic recycling strategy. Hint: Don't permanently bind a topic to a user but allow ARNs to expire, similar to a DHCP lease. Your app may periodically ask your web service what ARN it needs to subscribe to and expect to be re-assigned. If you build this into the client protocol early on, you won't need as many ARNs. After all, 100k active users is entirely different than 100k enrolled users :)
With Amazon SNS, there is no minimum fee and you pay only for what you use. Users pay $0.50 per 1 million Amazon SNS Requests, $0.06 per 100,000 Notification deliveries over HTTP, $0.75 per 100 Notification deliveries over SMS and $2.00 per 100,000 Notification deliveries over Email.
Amazon SNS also includes a Free Tier, where users can get started with Amazon SNS for free. Each month, Amazon SNS customers pay no charges for the first 1 million Amazon SNS Requests, no charges for the first 100,000 Notifications over HTTP, no charges for the first 100 Notifications over SMS and no charges for the first 1,000 Notifications over Email.
So I will suggest increase the limit before hand if that is anticipated by you. you don't get charged for increasing the limits. They will definitely increase to 100 Million.