#stripe

/

      • hpar
        which will send money to your bank account for that currency
      • just remove the "recipient=self" and yes that's exactly what you want
      • passing {stripe_account: "acct_123"} creates the payout on "acct_123"
      • Guest3904 has quit
      • koopajah has quit
      • tonybeninate has quit
      • pOe[ joined the channel
      • pOe[ has quit
      • Luke joined the channel
      • orbyt_ joined the channel
      • Guest95115 joined the channel
      • Guest3904 joined the channel
      • flipdiggity has quit
      • stripe956 joined the channel
      • hi stripe956, what's up?
      • stripe956 has quit
      • Luke has quit
      • Luke joined the channel
      • rajesh_ has quit
      • rajesh joined the channel
      • johnzhuangmiao joined the channel
      • Luke has quit
      • johnzhuangmiao has quit
      • grimecho joined the channel
      • nexie has quit
      • grimecho
        When editing the quantity for an existing subscription, the documentaion only gives a brief sentence or two on how pro-rated billing works. I'm looking for some clarification on the following scenario. I have a monthly plan that charges $x / user. A customer purchases the plan and has a single user. She is charged $x. Halfway through the month, the customer adds a second user. What is the default outcome of this on the next billing
      • cycle?
      • Luke joined the channel
      • mattwc
        the default is that it is prorated, so if half way through she adds a second user, her next bill will included the prorated cost of a user for half a month
      • hpar
        right, one sec
      • Guest3904 has left the channel
      • grimecho
        Cool, that's that I though. Is there a way to change this, so that she is only for the new user at the start of the cycle. E.g, first month = $10 for one user, next month $15 for two users, even if the user was added halfway through?
      • I mean $20 for two users, not $15
      • mattwc
        so you want it to not be prorated then?
      • grimecho
        correct
      • mattwc
        I believe prorate=false is an option
      • hpar
        yep in that case you would want prorate=false
      • otherwise Stripe computes an exact proration (down to the sec) of difference between the price at the old rate and the price at the new rate for the remaining time in the month
      • grimecho
        Ok, thanks. Found the documention in the API. The info on prorate seems a bit ambiguious, which is why I think I missed it the first time.
      • "Boolean (defaults to true) telling us whether to credit for unused time when the billing cycle changes (e.g. when switching plans, resetting billing_cycle_anchor=now, or starting a trial). If false, the anchor period will be free (similar to a trial) and no proration adjustments will be created. "
      • Thanks for the help. First time I've been in any IRC channel is 15 years. Glad to see there's still active communities.
      • grimecho has quit
      • tonybeninate joined the channel
      • orbyt_ joined the channel
      • hpar
      • Xionkana joined the channel
      • > If no destination is supplied, the default external account for the specified currency will be used.
      • Warped26 joined the channel
      • Xionkana has quit
      • koopajah joined the channel
      • rdymac joined the channel
      • tonybeninate has quit
      • elios21 joined the channel
      • nickkcin joined the channel
      • tuxd00d joined the channel
      • kambiz4 has quit
      • koopajah
        you'd have to create 2 separate charges in that case, one in each account
      • Luke has quit
      • yes they would. There's no real good way to do this otherwise. I'd recommend discussing your business model with our support team though: https://support.stripe.com/email
      • there is but not without holding the liability that's why I would recommend talking to our support team instead
      • Luke joined the channel
      • snipecode joined the channel
      • that looks more like a connection issue on your end
      • KanerixWolfe joined the channel
      • nickkcin has quit
      • korben
        Hello!
      • snipecode: Yep.
      • snipecode: Well, we'd rate limit you. We likely wouldn't block you.
      • koopajah has quit
      • root____ joined the channel
      • Hrmm. Let me see.
      • root____: Do you have an example charge?
      • snipecode: I believe this is a private (for some reason) attribute.
      • snipecode: Meaning, it's not visible in the API.
      • Oops. Wrong person.
      • root____: ^^
      • root____: You can file a feature request @ https://support.stripe.com/email though.
      • root____: Just be sure to outline your use case.
      • root____: If I'm not mistaken, I think you need to do some magic with webhooks to associate payouts w/ charges.
      • root____: There isn't a direct link, afaik.
      • snipecode: It seems to think your DNS is borked. You could try using https://github.com/stripe/stripe-reachability on the web server to see if it can identify the problem.
      • snipecode: It's unlikely, as we would have almost definitely had an issue arise.
      • snipecode: We have thousands and thousands of requests per second coming in all the time.
      • dms joined the channel
      • snipecode: We don't rate limit long term. We just rate limit in 5-second bursts-ish.
      • snipecode: Is it a dev server? Maybe try running the same requests from a dev machine and see if that works?
      • snipecode: Or if it's a dev machine, maybe try tethering it to your phone or another network to see if that changes it?
      • Xionkana joined the channel
      • FCS joined the channel
      • Xionkana has quit
      • rajesh has quit
      • FCS: Mind sharing your Create Customer API Request code?
      • FCS: What's the resulting customer id?
      • FCS: (It's harmless to share the customer id. So no worries.)
      • FCS: cus_xxx
      • FCS: I need the actual id.
      • FCS: cus_xxx <-- that thing
      • Thank you.
      • orbyt_ has quit
      • FCS: It looks like the only field getting passed to Stripe is the description. We don't even see a `source`-argument as part of the request. Are you using NodeJS w/ Stripe-Node?
      • FCS: Is it possible that `attributeMap.cardToken.id` is `null` when this is executed? Have you tried dumping it to make sure it's valid?
      • FCS: To a log, I mean.
      • Numline13 joined the channel
      • FCS: Coolbeans. :)
      • FCS has left the channel
      • FCS joined the channel
      • snipecode has quit
      • Nightmare11 joined the channel
      • Ooookidokie.
      • Mmmmhmmm.
      • Okay.
      • Can you share the code you're using to create the customer + the resulting customer id?
      • acct_xxx too please.
      • darxun17 joined the channel
      • darxun17 has quit
      • Second.
      • Luke has quit
      • FCS: It looks like it was put on the correct account.
      • FCS: Are you toggled in your dashboard to look at test data? It's there.
      • tuxd00d has quit
      • It won't be there.
      • It'll be on the connected account.
      • Right. So it should be there. Open that link in the incognito mode browser.
      • Are you searching for it or something? Maybe indexing is slow?
      • wgma joined the channel
      • w00t
      • */cough* FCS: Are you toggled in your dashboard to look at test data? It's there. <-- message from earlier haha