4ian

[vivid furnace]

Do you have a specific API request example that failed because of the cross-border restriction?

[wispy bough]

Well that's what was surprising, from what I remember we got a Stripe error displayed to the customer in the checkout page, when clicking on the buy button. I'll try to find this again (sadly because of this we decided not to support non-EU sellers for the time being).

[vivid furnace]

But yes, generally EU platforms cannot transfer funds outside of 'SEPA region' (i.e. to US)

[wispy bough]

There you go.

(I know this is a bit fuzzy but hopefully this can help you tell me if it's normal or not)

[vivid furnace]

Can't speak to your founder friend examples unfortunately

[vivid furnace]

Do you happen to have the cs_xxx ID for this page? It'll be in the URL

[wispy bough]

Sure, I will dig a bit more with him about their exact set up.

[wispy bough]

It was a long time ago, but I might find the date of this screenshot and find maybe on the Stripe dashboard the checkout session (is there on Stripe a list of all checkout sessions?)

(so far the only info I can get was that this was on January 11, 2023 around 2:40 PM)

[vivid furnace]

Oh a year ago?

[wispy bough]

This is my understanding. This being said, we were at the time very surprised to see what I included in my screenshot - because this means that we were able to properly generate a checkout session using the Stripe API without any error, and this error message was then displayed when the end user was trying to pay.

[wispy bough]

Correct

(we set up our marketplace around a year ago, and we decided not to work with non EU sellers for this reason - but I'm getting back to you today to see if we did not miss something :))

I've actually found the payment_intent.payment_failed event at this time 🙂

[vivid furnace]

Agreed, that is not desirable. I'll look into this

[wispy bough]

https://dashboard.stripe.com/events/evt_3MP4X846T03ISJOc1vaByE1d
https://dashboard.stripe.com/payments/pi_3MP4X846T03ISJOc12PjHqrV

[vivid furnace]

Perfect, thanks! I'll look at those IDs soon

Agreed that the session creation here should of errored because of the cross-border restriction: https://dashboard.stripe.com/logs/req_u5oJAhNtrLoANI

[wispy bough]

Many thanks!

Note that as you can see on my previous screenshot, the first call to create the checkout session (https://dashboard.stripe.com/logs/req_u5oJAhNtrLoANI) returned a 200 OK. This is the one we issue from our API.

I can look at the request body (see first screenshot of this message) and properly see that the customer is one of our team member, and we want to do a transfer to a seller acct_1MCV7kQRJK7reiuY. I've checked this connected account and it seems to work.

The checkout session is created (second screenshot) without issue.

[wispy bough]

Would be better indeed!

[vivid furnace]

I'll talk with Checkout team about the API behaviour here as I agree it is not optimal. Re: cross-border restrcitions, I expect you'll need a US entity/account to be able to have US connected accounts

[wispy bough]

Thanks for your confirmation! I'll double check with my friend what's their set up. I guess they might not be using Stripe Connect or maybe not doing transfer like this.

[vivid furnace]

Yep, hard to comment without specific examples

[wispy bough]

Sure. If the checkout team could checkout the API behaviour, this can maybe save a few hours/days of work to some people thinking that it will work ("yay, the session worked, we're good!") despite it not working when trying to pay 🙂

On our side, we'll continue working with either EU sellers only, and use other payment providers to work with non EU sellers or buyers.

[vivid furnace]

Thanks for the feedback! Will share with the team