#borjapallasa-payment-links

1 messages ยท Page 1 of 1 (latest)

iron plankBOT
loud ferry
#

Hi, it sounds like you're trying to create a Payment Link with Connect: https://docs.stripe.com/connect/payment-links. However, it sounds like the payment method is not enabled on the Connected Account. Did you look in the Dashboard from the error and enable the payment method?

nimble gust
#

I'm just passing no payment methods as in documentation says that when no parameter is passed it will enable automatic payment methods

loud ferry
nimble gust
#

Sure

loud ferry
#

From the error, it sounds like whatever payment methods you've enabled, there is none that support that specific currency.

nimble gust
#

req_d1mRfKV7hGYmut

#

That's the ID of the request

#

It's USD

loud ferry
#

Taking a look

nimble gust
#

Thanks, I can provide Parent Account Id Account too

loud ferry
#

No need, I think I have everything I need

#

at this moment

nimble gust
#

Okay, thanks

loud ferry
#

Thank you for your patience, I'm still digging into this

nimble gust
#

All good, no problem at all

iron plankBOT
#

borjapallasa-payment-links

sage stone
#

@nimble gust I'm investigating, but you really shouldn't ever be using "Direct Charges" on an Express account so I want to flag that you also have an incorrect integration here

nimble gust
#

Oh okay, then what should I be using?

#

Thanks for pointing out

sage stone
#

All transactions should happen on your own platform account. You can configure the PaymentLink to send a portion of the funds to that connected account (both in the API and the Dashboard)

#

Still digging though, for some reason card isn't enabled for you and that's why it errors but I don't understand why yet

nimble gust
#

Okay, no problem so just for me to understand it properly what's the solution:

  1. Buyer makes the payment and goes to our connected account (so products & prices are indeed hosted in our main account, referencing to the account)
  2. We collect the payment
  3. We send the payment - fees to the connected account
#

Not necessarily solution for the problem, but the right procedure with Express Connected accounts

sage stone
#

yes, though all steps are done together

#

you don't get the money and then write code to send money to the right connected account, you can configure the PaymentLink to do all that automatically for you

nimble gust
#

Oh that's great, indeed we are having the problem with creating payment links on connected accounts, on our account it works

#

Can you illustrate a bit more on how to set the PaymentLink up?

#

So final set up would be:

  1. Create Product
  2. Create Price
  3. Create Payment Link with Reference to Express Connect Account so payment - fees is sent automatically to the Stripe Express Account
sage stone
#

correct!

#

Can I ask you to try a PaymentLink in your account quickly in the Dashboard?

#

I'm baffled why it errors

nimble gust
#

Yeah, for that I simply remove the header of the account on the API call, right?

sage stone
#

yes but pass a Price id on your own account too

nimble gust
#

Yeah I'll pass everything to my account

#

Check now

#

Product and Price were passed to my account

sage stone
#

And okay we figured out your issue: you seem to be creating accounts with only the transfers capability too

nimble gust
#

Actually then I even tried to fix the capabilities and weren't able to make it work

#

But as the issue is coming when we are creating products in the other accounts, I guess it won't be needed

#

"Actually then I even tried to fix the capabilities and weren't able to make it work"

I even made some tests enabling cards, transfers, probably the logs are somewhere around

sage stone
#

yeah overall that's the problem you had

#

basically if you do "transfers only" you can't use Direct Charges or On Behalf Of.

#

Lots of "flavours" of fund flows on Connect and crucial to pick the exact right one for your business

nimble gust
#

Okay all good, I guess the set up that you propose is just simpler, also it was something that was working previously

#

Sooo, getting back to it:

Can you illustrate a bit more on how to set the PaymentLink up?

sage stone
nimble gust
#

Okay, that's super clear

#

Stripe Connect documents drove me a bit crazy actually

sage stone
#

yeah I can understand that

nimble gust
#

Thanks I guess, problem solved!

sage stone
#

Awesome!

#

I flagged internally so that we can improve the error message in this flow!

nimble gust
#

No jokes I've been stucked with this two weeks, tried many different things and even hire an external person ๐Ÿ˜‚

#

Almost three weeks indeed

sage stone
#

I'm sorry, we do aim for this to take minutes to integrate ๐Ÿ˜ฆ

nimble gust
#

All good, now is clear and won't happen again

#

Thanks!

sage stone
#

that's the main doc that explains the differences and the code

nimble gust
#

Okay, just to clarify, that Stripe Account header is OUR stripe connect?

sage stone
#

no

#

That screenshot is for what you are doing right now that I told you was wrong

#

you are supposed to use Destination Charges so you want the next example

nimble gust
#

Sorry, this is the one I should use?

sage stone
#

yes

nimble gust
#

Yup, realized that

#

All good now, thanks

#

Fees / Amount transferred to destination should be passed as a parameter as well?

#

Basically this

sage stone
#

yes

#

if you haven't seen this, highly recommend. That video should make you go "ohhhhhhhhh I get it"

nimble gust
#

Yup pretty much clear, then I may ask:

In this use case, there's no real difference between using Standard account / Express account as the charges are getting done to the main account.

So offering standard account to the sellers will save us 2 bucks per month per seller + transfer fees

sage stone
#

ah yes but no ๐Ÿ™‚

#

If you use Standard accounts you should never use Destination Charges!

nimble gust
#

Hahaha okay I won't but why that?

sage stone
#

Standard -> Direct Charges
Express/Custom -> Destination Charges

#

it's all about who owns the risks/liability for negative balances

nimble gust
#

Ah okay

#

Understood

#

Thanks for all, really helpful and solved the issue