Confirmed above!
HN user
amfeng
Builds things at @Stripe. Passionate about bagels and usually eats too many vita-gummies.
I'm @amfeng on Twitter. (:
Hi there! There is no minimum spend requirement to take advantage of the AWS credits. They are promotional credits and will eventually expire; see Amazon's terms: https://aws.amazon.com/awscredits/.
We're working on it! (;
We love the idea of having roles for spending controls. It's not currently part of the product, but we're planning to work on this very soon!
Thank you! Fixed. (:
Your business doesn't need to be incorporated to apply. Sole props are welcome! It's worth noting that the personal liability changes, though: the individual behind the sole prop will be personally responsible for charges on their account.
(Amber from Stripe here. For folks following along, we're talking about the "Additional Benefits" section on the page.)
Anything that says "cash back" is automatically applied to your card spending and for both new and existing customers. For everything else, we'll give you a discount code to type into the partner's site directly!
We love working with you. <3
Right now, you pay through a linked bank account. We are planning to let you pay from your balance in the future, though. (Most of our early users preferred the former.)
(Amber from Stripe here.) We're definitely planning to expand to other countries—this is just the start.
Hi! OP here.
This actually works out okay for most of our libraries. For the ones that can support it (Ruby, Python, etc), we don't hardcode the properties for any resources and instead generate objects on-the-fly when you make an API request.
In the $1 example, the libraries will just construct a Charge object without the `amount` property, since it wasn't returned in the API response.
You're right that it isn't perfect for other languages, though. We're working on making our versioning story better in our docs, libraries, webhooks, etc. (:
Hi! We only prefill your email address if you're logged into your Stripe account while looking at that page. Hope that clarifies things.
My favorite explanation of DF:
(Sorry about the late reply!)
Not generally, but we'd definitely be willing to take a look if you want to send something in! (:
Stripe! We're hiring engineers in San Francisco and remotely within US timezones. REMOTE and H1B welcome.
We're increasing online commerce by making payments (and building an online business generally) way easier.
See [1] for an overview of the challenges we're working on, or check out [2] for a description of our interview process. Apply by following the instructions on our jobs page [3] (please indicate that you saw this post).
Also feel free to ping me at amber@stripe.com if you're thinking about applying but have any questions!
[1] http://www.quora.com/Stripe-company/What-engineering-problem... [2] http://www.quora.com/Stripe-company/What-is-the-engineering-... [3] https://stripe.com/jobs
We've actually got a private beta in the works. (:
I'm happy to give you access if you'd like to try it out -- just email me at amber@stripe.com.
We're working on it (multiple subscriptions)! (:
Cake in the office is a great thing to be distracted by. (:
Right -- those are per-charge, not per-day.
Hey, charge responses now return a reference to a balance transaction (which represents what you'll actually be paid in).
You can auto expand the balance transaction upon charge creation by passing expand[]=balance_transaction, or you can retrieve the balance transaction directly: https://stripe.com/docs/api#retrieve_balance_transaction.
Makes sense.
What would the ideal behavior be if your customer updates their default card? Should the recurring billing continue chugging along with the card it was created with, or use the new card instead?
You can use your default card for once-off charges as well (just don't specify a card ID when making a charge with a customer).
You're right that you can't use a separate card for subscriptions yet -- we just use the customer's default card. We'd love to hear your feedback on this though (feel free to ping me at amber@stripe.com)!
Hm, that's interesting.
What OS/browser are you on? (Feel free to email me at amber@stripe.com as well.)
If our current payouts schedule isn't working for you, we'd be happy to help out. Feel free to ping me at amber@stripe.com.
Yep -- this is something we're really interested in doing as well.
Which parts of the dashboard in particular? Would love to hear your feedback at amber@stripe.com!
Your business name, along with the transfer statement descriptor you specify (though this varies by bank).
It's a test-mode API call, so I'm sadly not getting any money from this. (:
1) You should be able to pass in "disputed=true" to the charge listing call: GET https://api.stripe.com/v1/charges?disputed=true
2) Definitely. We'll keep that in mind!