#stripe

Not that we're expecting fraud, but if fraudulent activity were to happen, it would be a massive blocker for us.

yep, with custom/managed accounts you are liable for any activity of those accounts

express is nice because Stripe handles the onboarding flow and identity verification

I assume you've read https://stripe.com/docs/connect/accounts

Yup that's right I've read through it

as far as fraud, the identity verification with custom or express both do a pretty good job of vetting users

but question, is there an Express type of option where we can still customize the onboarding flow within our app?

you're of course free to collect additional info, for example a copy of a state cosmetology license

Guest39137: no, express is pretty fixed. You can customize the color, and it's about it.

with custom you end up building UI components and views for collecting bank account info, etc

Ok, got it. Thanks.

With the Standard account, would have a barber have to go through Stripe to send over the payment request to their clients after an appointment?

well, no, that'd be through your app

The way we've built it now, the check-out/payment request is done within our app and we're hoping to leverage Stripe to collect/distribute the payment to the barber

once you're connected to their standard account you can do any action through the API that they can

and Stripe doesn't really have a "request a payment" flow, so that's something you'd still build

Oh ok perfect.

So with a Standard account, how is that normally done with a native app? Would we have to set it up where an separate window within our app opens up and takes the user to the Stripe website to create an account?

Also, sorry one last question. And thanks for taking the time btw. Knowing what you know, do you think a custom account would be a good fit for us? Or would you recommend that we start with a standard account (at least for our MVP launch)?

hm, yeah so if you create a "Connect with Stripe" button they're given the option to create an account

you can also prefill some info if you have it up front

Hi

fv

Hi

Can someone help me?

Guest39137: the onboarding can be a little harder to grok with standalone, but it's probably fine for an MVP

Hope you all are good. I am using Charge API and when i try to add metadata column in my Request the request fails

hey Aki Leif_, what's up?

what's the exact error message Aki ?

Thanks @hpar

you've been great

API exeception

Type: Stripe\Error\Api Message: An unknown error occurred Filename: C:\xampp\htdocs\give_portal\vendor\stripe\stripe-php\lib\ApiRequestor.php

File: C:\xampp\htdocs\give_portal\vendor\stripe\stripe-php\lib\ApiRequestor.php Line: 273 Function: handleApiError File: C:\xampp\htdocs\give_portal\vendor\stripe\stripe-php\lib\ApiRequestor.php Line: 65 Function: _interpretResponse

hmm, any errors in your stripe dashboard logs?

happy to help Guest39137!

nope

can you share the code where you're passing the metadata? and what version of the PHP library are you using?

$charge = \Stripe\Charge::create(array( "amount" => $amount*100, "currency" => "usd", "description" => $customID, "source" => $token, "metada" => $details ));

you misspelled metadata

I am using version 5

also $details should be an array with keys and values, make sure of that

it mistake in copy and paste

Yes its a key pair values

do you have a request ID for a successful request? do you have the ID of a request from your logs? it's req_XXX in the URL when you're looking at your dashboard logs

let me check

Hey guys, we truned off support for TLS 1.0 on our server and now we cannot communicate with stripe? Do you guys have any suggestions?

what do you mean "turned off support"

?

Disabled it

for PCI compliance

but for inbound requests to your server?

or for openssl requests to Stripe?

just in general, for IIS. We used IISCrypto to disable it

The PCI scan we run flagged us for having it enabled

ok, so that shouldn't have affected your outbound requests to Stripe. Stripe prefers TLS 1.2 for requests for PCI reasons, though older accounts can still use older TLS at least until the big deprecation deadline next year

We now get the error "The client and server cannot communicate, because they do not possess a common algorithm"

How sensitive are source ids like card_xxxx or ba_xxxx? They aren't inherently useful if you don't have access to my api keys and if you did you could only make charges into my account.

I'm not familiar with how this is set up on Windows, though, and why disabling TLS1 would affect your outbound communications

have you read https://support.stripe.com/questions/how-do-i-u... ?

no, but I will. Thank you

clerum: correct, not sensitive at all. they're just opaque IDs

I suppose the correct question is how sensitive does stripe consider id's from the api

k

thanks.

arelas: the question is, if you reenable that flag does it work as expected?

hpar, not sure...I need to reboot the server so I'll have to wait until a low usage time

hm, that's not fun

I'll try that and gather more information

you've still got TLS1.1 and TLS1.2 enabled, correct?

and all of the non-deprecated ciphers, etc

yes I do

My thinking is I might have to reboot as making this change might have things a little wacky until I do

hi

stripe300: hello. What can we help with?

i just want to know that it is possible to generate the token by card if the card is not correct.

like card is block by bank or other possible cases

Hello, is this the right place for Stripe technical questions?

i don't know if it is not the right place please direct me

stripe300: In certain circumstances we do run an auth on the card at the time of tokenization. In all cases however, unless the card was authed at the time of tokenization, we do run a $0 or $1 auth on the card when the `Token` is attached to a `Customer` or a `Charge` is attempted.

djmetzle: it is - what's up?

ftknox: we have an irrate user that wants to know why we have saved his card information.

stripe300: I should also note that if the card tokenizes, but the `Charge` attempt fails, we will return an error respond with as much detail about the failure as we can

djmetzle: Did your system create a `Customer` from his tokenized card info, or is he upset about the "Remember Me" functionality of Checkout?

ftknox: I've tried telling him that our company does not directly save the payment details, only the return token from Stripe. He says we've violated something.

I think our company saves the checkout token by default

djmetzle: You probably want to write in via https://support.stripe.com/email for help on this. I know that we have some roughly standard language that you can use

Okay thanks

That is fantastic

no issue

Is there a phone number for stripe at all?

i think no

where are you chatting from

?

Hawaii

is it country

?

USA

OK

I am from India

atort: not really. We've found that email is the best way to provide quick, efficient, and really top-notch support

atort: https://support.stripe.com/email is what you'll want to use to write in. You should get a response within 24hrs

Ok Thanks

by the way are you developer

?

I have a payout that is needing to go into my account for a payment and for some reason it seems to never get deposited.

No just looking at all their possible ways of reaching out to someone. :)

oooooooooooooooooooooook

Bye take care

atort: emailing https://support.stripe.com/email is the only way to get help with that. We shouldn't discuss private account details in this public channel

ftknox i am not the primary account holder for our company Stripe account, can i get the email address directly?

Ok thanks.

djmetzle: support@stripe.com

Thank you!

Aloha

djmetzle: you're welcome!

hi

#hi, I am trying to upgrade our stripe (gem) version from 1.18.0 to the latest - 2.12.0. However, I won't be able to use the test suite we have with stripe-ruby-mock because it's latest version - 2.4.1 is dependent on stripe gem version <= 1.58.0. Any suggestions?

hey stripe301 sounds like you'd need to maybe fork the library and upgrade its dependency, or work with the library author to get it upgraded

stripe301: Patch stripe-ruby-mock to support a newer stripe gem?