#lynn_connect-3ds

1 messages ¡ Page 1 of 1 (latest)

gleaming walrusBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1482036496683896954

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

clever ice
#

Hello, looking in to this. I see that this is a direct charge, the most common source of this error for direct charges is forgetting the Stripe-Account header when making the later calls. So it sounds like your stripe instance may not be setting this setting to specify which connected accounts you are making calls for

static aspen
#

i can see the account in the dashboard paymemnt intent log. Stripe-Account
acct_1QiJqn00hi7eYUa5

#

so are you saying i need to add the account code to the requestOptions PaymentIntentService.Get(string id, [PaymentIntentGetOptions options = null], [RequestOptions requestOptions = null])

clever ice
#

Yes exactly. The payment intent exists on your connected account. Without that setting, Stripe will only look for payment intents with that ID on your platform account, but then there aren't any so that error is thrown.

static aspen
#

ok that makes sense but how do i test a 3D secure transaction through a connected account?

#

i have been testing 3D secure though the sandbox account which works. can i add a connected test account?

clever ice
#

It should be the same API calls as testing with any other account. You just need to make sure to consistently pass that Stripe-Account setting on your server when making server-side calls and pass it to Stripe.js when initializing it on the client

static aspen
#

yes i understand that but i would like to actually test it. i dont have a foreign credit card

#

can i get the transaction id (ch_xx) from the stripe checkout library?

gleaming walrusBOT
clever ice
#

Apologies for missing this question. We reccommend against testing payments in live mode. If 3DS works in your sandbox app with your connect setup, it will work when 3DS is required for live payments with the same code.

static aspen
#

that is my point i only have a basic sandbox account without a connected account code so i dont know how i can test 3DS with a connected account

gleaming spade
#

Hi Lynn, i'll be taking over for Pompey as they need to head out.

You can create and onboard connected accounts within your sandbox account. Should allow you to test the full range of connect payment flows.

static aspen
#

ok can you point me to any documentation on how to do that?

gleaming spade
static aspen
#

yes i use the test card number for 3d secure . i just need to know how to test with a connected account.

gleaming spade
#

The first doc should have you covered then. Just swap out and use your sandbox / test-mode keys while going through.

static aspen
#

can i add a connected account to my test account in the dashboard or do i have do it in code?

gleaming spade
#

Our documentation doesn't really cover account creation via the Dashboard, mostly just follow the flow after clicking create.

static aspen
#

the dashboard wants me to activate my test account which doesnt make sense

gleaming spade
#

Can you clarify what you mean by activate? We're predominately focused on API integrations, most of our team makes very minimal use of the Dashboard.

static aspen
#

i see the create button but

gleaming spade
#

Are you sure you are in test mode? or a sandbox? This seems to suggest your in live mode.

#

Also the text is cut off so I can't see the full context.

static aspen
#

i clicked test mode. now i get

#

my test account is really old.

gleaming spade
#

I'd recommend getting a sandbox going then, test-mode accounts share a lot of settings with their live counterparts.

static aspen
#

so create a new sandbox?

gleaming spade
#

If you already have a sandbox account you can use that, but if you've only used test-mode before, (its not the same as a sandbox) I'd recommend creating a sandbox.

#

The nice thing about sandboxes as you can make as many as you need, where test-mode you only get the one per account and it's closely tied to the live account it's based off of sharing a lot of the same settings.

static aspen
#

ok thank you. i will thry that. 1 more question. is it possible that the system could sometimes find the payment intent if the account code isnt specified?

gleaming spade
#

It depends on the type of connect charge relationship you are using.

https://docs.stripe.com/connect/charges

Direct Charges: (the charge takes place directly on the Connected account), there is no record of the Payment Intents existence at the platform level. It exists only on the Connected account and to access it you must specify the account-header for the Connected account.

Destination Charges: The charge takes place on the Platform, the relationship is inverted, the Connect account has no record of the transaction, the funds are then sent to the Connected account from the Platform.

Separate Charges and Transfers: Same as above but instead you can transfer the funds to multiple Connected accounts instead of just one.

static aspen
#

pretty sure its a direct charge. i see the transactions in the connected account

gleaming spade
#

If you have the request ID I can confirm for you but if you specified an account-header it was a direct-charge, and if you see it on the connect account, another indicator it was a Direct Charge.

static aspen
#

ok that means 3D secure never worked correctly on my connected accounts which is hard for me to accept!! i hope that means we dont get very many of them!

#

thank you for your help

gleaming spade
#

Of course.

gleaming walrusBOT