#theofenol_unexpected

1 messages · Page 1 of 1 (latest)

vapid mistBOT
#

👋 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/1293934301175484456

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

fierce anchor
#

Hello

proper pecan
#

hi

fierce anchor
#

How are you rendering Payment Element here exactly?

proper pecan
#

i want this link button to dissapear...

fierce anchor
#

Are you passing in the client secret to your elements object?

#

Or you are using the deferred approach?

proper pecan
#

stripeElements.value = stripe.value.elements({ clientSecret: paymentData.data.paymentIntent.client_secret })
paymentElement.value = stripeElements.value.create('payment')
paymentElement.value.mount('#payment-element')

#

client_secret

fierce anchor
#

Gotcha and that client secret is coming from an Invoice?

proper pecan
#

and client_secret is coming from the paymentIntent on an invoice

#

yeah

fierce anchor
#

Got it, can you share the Invoice ID that you are testing with?

proper pecan
#

yeah, just a sec 😄

#

in_1Q8Mk4Q6nkBOVeRX57U6LQwf

fierce anchor
#

Thanks, looking

proper pecan
#

this is the Manage Payments menu from my Invoices settings

fierce anchor
#

Ah you are creating this Invoice directly on an Express Connected Account

#

That is your issue

#

You can't control the Invoice Settings for an Express account and is one of the reasons we do not recommend using Direct Charges with Express

#

You should be creating the Invoice on your platform and using Destination Charges here

proper pecan
#

ayyyy

#

So, standard?

fierce anchor
#

Yes, or Standard accounts, but in that case the Connected Account user would have to set their Invoice Settings to have Link be off.

proper pecan
#

Nah, destination is not ok for me because my platform will have huge turnover and will result in large government tax

#

i m doing a ticketing platform where I get 2-3%

#

so if i do destination charges, I will end up paying more tax than profit

#

because there is some stupid law taxing based on turnover instead of profit

#

...

proper pecan
fierce anchor
#

I don't know anything about tax laws, but in that case it sounds like you want Standard, yes.

proper pecan
#

can't I (me, the platform) do it when i create their accounts or when I onboard them?

fierce anchor
#

No, for Standard accounts they have their own account and full Dashboard so they manage their account

#

What you can do is specify payment_settings.payment_method_types when you create your Invoice

#

And you can just specify card there

#

That will then not use the default Invoice Settings

proper pecan
#

yeah, but will Apple and Google still be available?

fierce anchor
#

Yes

#

Apple and Google Pay are card type payment methods

proper pecan
#

I;ll try, thanks!

#

should be ['card'], right?

fierce anchor
#

Yes

proper pecan
#

const invoice = await stripe.invoices.create({
customer: customer.id,
auto_advance: false,
application_fee_amount: req.finerFee,
payment_settings: {
payment_method_types: ['card'],
},
},
{
stripeAccount: req.connectedAccountId,
});

fierce anchor
#

Looks fine

proper pecan
#

confirm it works, thanks

#

i still need to figure out how to make things easier with standard 😦

fierce anchor
#

You should still use Standard Accounts here

proper pecan
#

yeah but...

#

see

#

the issue is that my customers are event organizers and restaurant owners

#

and i do not want to have a difficult onboarding process for them

fierce anchor
#

Up to you, but that is the recommendation

proper pecan
#

basically right now, they sign up on my platform and then i open the stripe onboarding page for them

#

and they just add everything there

fierce anchor
#

You do the same thing with Standard

proper pecan
#

yeah - but they will have to enter into the dashboard

fierce anchor
#

No

proper pecan
#

and enable apple pay, google pay and disable lin

#

link*

fierce anchor
#

And no, they won't have to enable/disable anything if you are specifying payment_settings.payment_method_types

proper pecan
#

so, basically, I can specify all their settings when onboarding them>?

fierce anchor
#

No you don't specify their settings, but you can control the payment method types shown, regardless of their settings, via payment_settings.payment_method_types

proper pecan
#

i ll try... thanks!

#

i thoguht about

#

invoices for example

#

if they are enabled by default or not

#

I want to avoid them having to use dashboard to enable invoices

fierce anchor
#

Invoices are enabled by default