#stripe

yes I followed , but am getting following error.

Unhandled rejection Error: The provided key 'sk_test_********************D6QM' does not have the required permissions for this endpoi nt on account 'acct_1AID84GxZPrWcX71'. Having more permission would allow this request to continue.

don't know whether I have missed any steps before creating charges

koopajah: Oh, what about for events greater than 30 days?

smcguinness : right now they are still available though it might not be true in the future

koopajah: Ok perfect! Thanks for the help!

rajagopal : that account does not look to be connected. Also it's your own platform account. you need to go through the OAuth flow with a *completely different* account

@koopajah - I could see the account is connected with my platform account

var stripe = require("stripe")("sk_test_pcBLCW8IK3BayTeW07yeD6QM"); stripe.charges.create({ amount: 1000, currency: "usd", source: "tok_visa", }, { stripe_account: "acct_1AaMksKjE0dffP0R", }).then(function(charge) { console.log('charge'+charge); });

rajagopal : sorry it's a bit hard to say just without more details. Really you want to 1/ connect a completely different account, this one is your own, it's wrong. 2/ connect with read-write

also please never share your API key here, this is logged publicly, make sure to roll it right now

I'm using auth and capture for my payment processing which means that I have to first create a charge, passing capture=false as an argument, and then call that charge with capture set to true when I want to process the payment. The problem is that my charge authorization and charge processing are on different api endpoints (authorize_charge() and process_charge()) - does anyone know what the best practice is for retaining

my charge object? I know I can declare it as a global object or maybe store the returned id on the client side but neither of those seem secure.

nikola : you can save it in the session for example on in your database and pass a unique id to your front-end

I was considering that but I wasn't sure how secure storing the id in a session/cookie would be. If a user has cookies disabled, or closes the browser that charge object is lost.

hmmm I don't think that's true, there'd be a sessionid in the URL or something similar no? I'm a bit confused as to why you need to do this. But passing the charge_id client-side sounds safe to me. As long as you can verify the customer doing this owns the charge (which means you have a login/password logic for their account)

"I'm a bit confused as to why you need to do this." So am I, I feel like I'm misunderstanding something important and working from that faulty premise.

How is auth and capture normally designed? I know a lot of sites use something similar where first the credit bard is authorized and only charged when they submit/confirm the order - that's what I'm trying to accomplish. So I have a authorize_charge() api endpoint that my frontend submits the tokenized charge to, it's authorized and returns a json object with the status. But I'm unsure how to recapture that charge object

because if I have the logic to process the charge in another function I don't have access to the charge object any longer.

I don't think that's how it works no. In my mind, auth and capture is here to let you, the business owner, only capture when you're ready, not the customer. So the customer pays, you take an auth, and 2 days later when the product is ready to ship you capture yourself

Oh okay, someone mentioned in this channel that I could use auth and capture for different steps in the checkout process. Is there a better way to implement something like this then because I've seen it used in a number of apps?

I'm not sure, I don't really understand why you would create an auth now and capture it 5 seconds later, I don't see the benefits

Because I don't want a user to be able to advance in the checkout process until they've submitted a valid credit card. I want then to submit payment information, then select continue, and be taken to a final confirmation page, and only once that final confirm order button has been clicked is when I want the charge to be processed.

You might misunderstand waht auth and capture means. What's the point of "authorizing $10" and not capturing if that's what you will charge in the end? I don't follow your needs I'm sorry

Because an auth is not a charge, a user can authorize $10 and then decide they don't want to go through with the order and close the page. If I just do a capture when they initially input their credit card information than that's it - they've already been charged.

Whereas if I use auth first and they neg on the order in a week's time the auth is closed and they haven't been charged.

sure but that's a failing of your integration if someone can create an auth, leave and still have their funds blocked for 7 days without you even releasing the funds

and you'll get a ton of unhappy customers if you do that

I wasn't aware that the funds were unavailable, I thought auth was just the bank confirming "this is a valid cc account and they have the requested amount in the account".

no an auth holds the funds

So how could I implement something like this, where the payment information is validated before the order is submit? I know a lot of companies follow this process?

you can save the card on a customer, this runs a $0/$1 auth with the bank. But there's no guarantee that they have enough funds to pay. But that's what every website has to deal with

I want to avoid the credit card information touching my server even if its tokenized

you're misunderstanding what a token is I think.

A token is just an id tok_XXXX that represents the card details in Stripe, you never touch the card details

hey guys, when i try to connect stripe to my app firebase says "Billing account not configured. External network is not accessible and quotas are severely limited. Configure billing account to remove these restrictions" but i already upgraded my aacccount

LordKratos : that looks like a question for Firebase here, not us

Okay, and what information do I have access to with the token? I mean if I the cc information is saved and represented as a token, when a user returns to make another payment can I ask them do you want to checkout with cc ending in these four digits?

nikola : you can but it's completely unrelated to the token. Tokens are one-time use. You collect card details, you get a token, you send it to your server, you save the card on a customer (cus_XXXX and card_XXXX) and those informations are saved in Stripe and you can re-use those

Hello - Is it possible, through Stripe's Java API, to modify what appears on a bank statement when Stripe makes a transfer?

hi

but when you say "you save the card" don't you mean I save the card token?

hi

hi

i have done settings like retry payments for 3 times after that cancel subscription .. on this cancellation.. why subscription cancellation event not generated

nikola : no I don't. I mean you create a customer and pass the token id in the `source` parameter and the card is saved. You might want to take a step back here and take some time to red through all our docs. That would help you better understand the bigger picture of Stripe, our API and how everything fits together

?

can any one help ? Thanks

TheNewbie : that depends what you mean by that really. Can you clarify?

lokanath : likely because not all retries happened or a new billing cycle started before all the retries were exhausted

Okay will do, thanks for being so patient with me, I appreciate you taking the time!

no all retries happened .. but no subscription cancel event is generated .. for this i need do any external settings ?

lokanath : did a new invoice happen before all retries?

yes

then it's expected. Since a new invoice happened it "resets" the failure counter and it would never cancel

Hey guys, any idea why I'm getting Test webhook error: 302 when trying to test? I'm using Azure, everything is built, deployed and published correctly...

I am hitting the controller, I would be getting 404 otherwise

cajun : hard to say unfortunately but 302 is usually a redirect server-side. Have you checked if you're hitting the HTTPS url or similar?

Is there a resource to learn more about "unlinked transfers"? We received an email yesterday about this, which coincided with payouts being disabled for all our Stripe Connect accounts. (Waiting for support to reply) The email stated: "We were excited to see that your platform started to use the Connect feature 'unlinked transfer'." -- But we have no idea how or when we did this ?

I think it means https://stripe.com/docs/connect/charges#chargin...

@koopajah ok .. other wise it will generate subscription cancel request ?

lokanath : yes

ok thanks a lot .. :)

of course :)

koopajah: yep ok i know what i did wrong, thanks

i see; we've been doing that all along... so i'm not sure why we're suddenly getting that email, and why payouts has been completely disabled. Is there any way we can escalate our ticket with support? We're on 18 hours now that we haven't been able to pay anyone. We have 250+ managed accounts. We're starting to panic. :/ I have 2 emails into general support, and an email in to our contact at Stripe and haven't heard back

from anyone yet.

drewjoh : those take time as we need to investigate on our end. If you give me your email address in private I can ping the team

sure thing

I'm looking into doing the Stripe transfers programmatically, through the API (Java). I'd like to do (2) transfers per day - one for the credit card monies and the other for the ACH. On our bank statement, when Stripe does a transfer, it displays "STRIPE TRANSFER XWF..." Is there a way to change that transaction description so that one can be identified with our credit card transfer, and the other with the ACH?

TheNewbie : https://stripe.com/docs/api#create_payout-state...

Thank you sir.

Follow-up question: If I'm doing the payouts through the API, will I need to calculate the Stripe fee and subtract that from the amount?

I'm not sure I understand what you mean by that. You have $X available and you decide what you want to payout

Hi, can anyone answer a question about "separate charges and transfers"?

stripe888 : depends on the question, what's up?

thanks! Ok

I am planning to do a charge first, with an additional stripe_account param

then I do another transfer to a second stripe account

if you create a charge with `stripe_account` param, the charge is on that account already, it's a direct charge: https://stripe.com/docs/connect/direct-charges

both are standalone. How can I prevent the first account to refund the charge on their behalf?

I think you're misunderstanding something in the flow here

Let me explain

it's a 3 parties flow

if you create a direct charge for $100 and take $10 as an app fee, the Standard account gers $90. If they refund, they refund $100, they lose $10

Let me give an example

product sells for 200. seller gets 20 via the stripe_account param in charge, so it's a charge in their account.

However, the seller can opt in to have us produce and ship also

you just said 200 and 20, which is correct?

In which case, our platform transfers 100 to the manufacturer in a separate transfer

I.e numbers: customer pays 200, seller gets 20, manufacturer gets 100

I don't think you should do things this way unfortunately. I would highly recommend that you talk to support: https://support.stripe.com/email and describe your business model in details. This means 4/5 paragraphs, not 2 sentences. This ensures our support team has all they need to guide you

ok I will do. thanks.

@koopajah Would you mind me asking where to find more documentation on how refunds are handled in the charge with stripe_account param?

that was *fast* thx

what it doesn't say there but surely elsewhere: can the connected standalone acc trigger a refund for a charge I issued to their account, or only my platform can do this?

if it's a direct charge they can refund

OK, and can I set the amount of application_fee that's refunded in such a case?

no, application fee is never refunded in that case. The owner of the account pays for the *full amount*. Which is clearly not what you want here and why I say that direct charges is likely the wrong approach.

Thx. and yes, I'll reach out to support, but from what you say it's not that bad. My intention is that they don't refund any of the charge that I spend in a subsequent transfer.

And I had planned to subtract the amount needed for the subseq transfer by increasing the application_fee

So a seller would need to ask me to reverse a transfer and cannot accidentally pay back money that we have already spent.