#stripe

Mowee_ : we don't support payouts to credit cards. Only US-based debit cards are supported. But yes you can make "normal" payouts to debit cards

stripe050 : hello! Sure what do you need?

of course!

stripe050 : I am following I was just waiting for the rest :)

to test you just create a charge in Test mode and listen for the webhook

you can totally see the Connect dashboard. You just have to create a separate account with a different login/password so that when you connect you can log into the dashboard and view it (for example in a different browser)

Hello, is it possible to generate a 0 dollars charge using Stripe's JS component?

and you can read https://stripe.com/docs/connect/webhooks for webhooks

diegoaguilar : no, Stripe.js is used to collect card details securely. It does not create a charge. And we don't support $0 charges

yes all of this is correct. You don't need to store any API keys. You always should use your API key and the connected account id (acct_XXXXXX) in the header https://stripe.com/docs/connect/authentication#...

then it all sounds perfect

you don't really *have* to implement webhook since you create the charge, it's really up to you to decide if you want to do webhooks and if so to listen to all relevant events. So for example all `charge.*` would be useful to listen too

to*

You would just create a test charge and confirm you get the event to your endpoint, it's as simple as that. You can use ngrok https://ngrok.com if you want to receive those locally

you just need to add a Connect webhook endpoint to your account. It's all in the doc I gave you earlier: https://stripe.com/docs/connect/webhooks

You totally can, I explained how you can do that earlier. And you don't really need to. You just need to add an endpoint to *your platform* and then you will see events coming in

usch84 : hello!

usch84 : at the moment you can look at https://stripe.com/docs/billing/invoices/sending though only card would work for those customers I think.

StanislasP : hello!

StanislasP : not really, in that case you would just not use a plan and just do one one-time charge: https://stripe.com/docs/tutorials/charges

what do you mean?

a charge would be done by your code server-side though

not really, I mean there are metrics for all charges, but those are just one-time charges, so you would report all of them the same way based on your volume on the landing page in the dashboar

dashboard*

yep just store this information in your db I would say

sounds good!

stripe050 : description of what?

when you create a charge you get a charge object if it succeeds or an error if not. So there's no need for anything else. But you can always look at `paid` and `status`

the card object has a `country` property for this yes

same it's on the card token too since the card token describes the card too!

stripe050 : you don't need to create a card object but you do need to create a *Token* to know yes

stripe050 : sorry I crashed let me know if you had another question

Amplaffy : what do you need help with specifically?

https://stripe.com/docs/recipes/subscription-si... have you read this recipe?

Amplaffy1 : even though it uses PHP it's the same exact logic no matter which language you use. And data-amount is optional, you can just remove it if you don't want to display an amount

[10:43:02] <@koopajah>Amplaffy1 : even though it uses PHP it's the same exact logic no matter which language you use. And data-amount is optional, you can just remove it if you don't want to display an amount

yes you can build things any way you like, there are numerous approaches to this too

no all of this is something you would implement yourself as the developer

usually we recommend just causing those events in your own account but really each event describes the resource they are associated with

sure but you can trigger all of this in Test mode in your account

you don't really need to receive those per se, you can view events in the dashboard

Is there a smart way to injecting CONNECTED_STRIPE_ACCOUNT_IDs to the request headers with Stripe Ruby library? Need to do it apparently to send payouts correctly from connect accounts own balance iODnstead of platform accounts.

https://stripe.com/docs/connect/authentication#... is the correct way

oh wow, after reading that page I completely missed the "Other library support" section and thought there only was the CURL support. Thanks

and sry :)

no worries at all, glad it clarified things :)

PhamHanh: i would talk to https://support.stripe.com/email about disputes issues, they may be able to provide some feedback

PhamHanh do you have any indication from your customers why they might be disputing? Do you suspect fraud or simple confusion about the pricing/product/service you are offering? Unfortunately this channel is largely for coding help, but that's where i might start trying to understand the root reason customers are filing.

hi sher, what's up

What kind of error are you seeing?

sher ah, okay, you'll have to talk to https://support.stripe.com/email

https://support.stripe.com/contact is the only support available

for an issue like this

of course, have a nice day and best wishes!

zreitdl you can use the IBAN numbers here https://stripe.com/docs/connect/testing#payouts, I believe you can simply do CH89370400440532013000

hi ov, welcome. do you have a question?

ov the clients just need their card/payment source, but the account to pay out will need some personal information. it varies by country, see https://stripe.com/docs/connect/required-verifi...

ov: external account == bank account

so that's the iban number.

zreitdl hmm, you're using https://stripe.com/docs/stripe-js/elements/iban to generate a source/token?

it looks like it is validating the bank, and the only numbers that work for the form are those listed at https://stripe.com/docs/testing#sepa-direct-debit rather than the more permissive https://stripe.com/docs/connect/testing#account...

leolux you'd need to handle that on your side, stripe places no limitation there

perhaps you could have a db table with your own id, the stripe customer id and email address, before you create a new customer check there. provide your users with a membership management area where they can login, update their account, etc