#ryan.badger-Connect

1 messages ยท Page 1 of 1 (latest)

magic badge
valid olive
#

hi

magic badge
#

Hi

#

I am a bit confused. Test keys are always for Test mode, and Live keys are always for Live mode.

#

So if you initiate test mode checkouts you should always use Test keys

#

Btw you shouldn't use your sellers bearer token. It's a discourage pattern. You should only use the Stripe Account header

valid olive
#

ok thanks - so how would we setup a "test mode" payment for our connected users?

#

to clarify - my question is, if we are creating checkout session for our connect accounts, should the payment mode (test/live) be the same for our account AND the connect account?

#

or should we use our (the platform) live keys, but pass a "test mode" flag to the checkout for the connect account?

magic badge
#

There is nothing like Live keys with a Test mode flag

#

Connected Account are connected to your account in either Test mode or Live mode. That's called Test mode connection vs. Live mode connection.

valid olive
#

hmm even if its via a connect account?

#

that doesnt sound right... we only ask users to connect their account once

#

and from that, we're able to setup live AND test checkouts for them

#

we dont ask them to connect their test and account and also connect live account

magic badge
#

Can you give an example account id?

#

I think that's live mode connection ๐Ÿค”

valid olive
#

sure 1 moment

#

our account ID (the connect platform) is: acct_1rwXb2g6DPIN2kjmBVca

#

and here's an account ID for a stripe account that just connected to us acct_1A073vFVnyJMda5n

magic badge
#

Okie, I can confirm that's a live mode connection

valid olive
#

OK - so can we not setup test mode checkouts for them?

magic badge
#

Your platform has a really old API version, but let's put it aside

valid olive
#

yeh we've been trying to upgrade it

#

but doesnt seem possible via the dash

magic badge
#

Which API are you using to create Checkout session?

#

I expect either Destination Charge or Direct Charge? Or Separated Charge and Transfer

valid olive
#

we're using direct charge

#

we dont touch the money at all

#

we dont take a %

#

we just create the checkout session via THEIR stripe account

#

but we've found it really difficult to find docs on connect - and asking the support chat usually ends in them replying with generic advice about standard stripe accounts, not connect

magic badge
#

Ok, I am assuming you are using this flow

#

but instead of using the Stripe Account header, you use their bearer token directly?

#

that bearer token could be either Test mode or Live mode, isn't it?

valid olive
#

let me double check

#

it looks like this

#

so we pass in the 'stripe_account'

magic badge
#

that looks good actually, that's the stripe account header

#

not the bearer token

valid olive
#

ah ok

#

we pass in the account ID...but we used the name "gateway_token"

#

E.G - acct_1A073vFVnyJMda5n

magic badge
#

Can I have a sample request id? From your dashboard

valid olive
#

where would I find that?

magic badge
valid olive
#

try this?

#

req_LABqXWhw0Uz77G

#

its a live checkout session request

magic badge
#

Yeah that's a Live one, using Stripe account header that I can confirm again. What if you use a Test key to initialize the same request?

#

same Account of acct_1K6GkjHHw6jzoQ33

valid olive
#

let me check

#

i'll try with another account

#

OK the accountis: acct_1A073vFVnyJMda5n

#

OK here's the checkout session in test mode

magic badge
#

Perfect!

valid olive
#

so it looks right?

magic badge
#

So the secret key you used, determine which mode it's in

#

Yes it looks right

valid olive
#

ok

magic badge
#

So I am confident that your integration looks good. Coming back to your question, it's the secret key you used that decides which mode that transaction is

valid olive
#

so its right that to create a checkout for a connected account in TEST mode, we also use OUR test keys?

magic badge
#

Yes

valid olive
#

i see

#

and we only ask our users to connect once

#

we dont ask them to connect test AND live accounts separatley

#

is that also right?

magic badge
#

Yes that works. Just alternatively you can also create test-mode accounts only, and perform any test you want, separately to your users

valid olive
#

i think we want to keep the "connect your account" to 1 action

#

so they connect once, then we can create both test and live checkouts for them

#

one other issue we've been having, is that we were told payment methods are automatic now

#

but our connect account ONLY see card at checkout

#

regardless of what methods they have enabled in their Stripe account

#

E.G - a stripe account has alipay and klarna enabled, they connect to our platform, we generate the checkout session on their behalf, and set the 'payment_method_types' flag to 'auto'

#

but only card is shown at checkout

magic badge
#

That feature hasn't published for Connect yet

#

I suggest to write to Support and they might give you in a Beta

valid olive
#

ah

#

you wont believe how many convos I've had with support about it ๐Ÿ˜…

#

they kept just telling me i was doing ti wrong

magic badge
#

But it could be hard with your old API version

valid olive
#

and that I had to first enable the methods in our dash

#

they dont seem to be able to help with connect queries...

magic badge
#

If you have a specific thread chatting with them about that, give me your email and the thread title, I will flag it internally

valid olive
#

it was all on your website support chat

magic badge
#

I know, I just need to find the convo from our internal system

valid olive
#

try that

magic badge
#

Can you paste here your email?

valid olive
#

then i got this reply

magic badge
#

Ok I see that convo, but it's closed from Mar 4 because they didn't have another reply from you

valid olive
#

i mean it was a futile conversation ๐Ÿ˜…

magic badge
valid olive
#

ok

#

hows this?

magic badge
#

Yeah, just send it and I will be able to find

valid olive
#

thanks

#

sent

magic badge
#

Just put a comment there.

#

TBH it will depends on account conditions etc, but my comment should put it in right direction , at least from the first place

valid olive
#

thanks!

#

what sort of account conditions?

magic badge
#

I honestly can't tell. It depends on each feature/beta. Generally it could be difficult with your old API version

valid olive
#

i think we're ready to upgrade that

#

but we need stripe to do it for us apparently

#

can you do it?

magic badge
#

I don't think I can. Is there a conversation already?

#

Like, are you sure your system can handle all the API changes from 2013 to 2020?

valid olive
#

there was an email chain yes

#

I can just reply to that and ask them to do it

#

and no...im not sure our platform can handle the changes tbh

#

but it's been so difficult getting information on how things are supposed to be done...

#

i think we're just going to have to bite the bullet and upgrade, then fix any issues that arise

magic badge
#

It's safer to test it IMO. Like your temporary use the newer API version in each part of your system, and testing if things are ok

#

You can specify API version in request level

valid olive
#

yeh i think we're doing that...

#

at least we tried

magic badge
#

๐Ÿ‘‹ I am stepping down for the day. If you come back feel free to open another thread. Good luck!