#Charmon

1 messages · Page 1 of 1 (latest)

rugged hawkBOT
ruby jungle
#

Hey there

#

Do you have a request ID for the error?

mystic rivet
ruby jungle
#

Yes or you should see one returned with the error in your server logs

#

Are you a platform/using Connect?

mystic rivet
ruby jungle
mystic rivet
#

i got the req id

ruby jungle
#

Okay please share here

mystic rivet
#

I am using the header:

      const session = await stripe.checkout.sessions.create(
        {
          payment_method_types: ['card'],
          // billing_address_collection: 'required',
          customer,
          line_items: [
            {
              price: price.id,
              quantity
            }
          ],
          mode: 'subscription',
          allow_promotion_codes: true,
          subscription_data: {
            application_fee_percent: 10,
            metadata
          },
          success_url: `${getURL()}/account`,
          cancel_url: `${getURL()}/`
        },
        {
          stripeAccount: price.stripe_account_id!
        }
      );
ruby jungle
#

Oh okay well then the Customer ID is a Customer on the wrong account (likely your platform)

#

Yep

mystic rivet
ruby jungle
#

Just looked and the Customer is on your platform

#

Right so this won't work

#

The Customer has to be in the Connected Account

mystic rivet
# ruby jungle The Customer has to be in the Connected Account

Can this be done, by having customer on my platform only? I'm saying this, because there would be multiple connected accounts on my project (including my own), so it would be very difficult to manage multiple customers associated with single user

ruby jungle
#

No that's not possible

mystic rivet
#

For example 1 patreon customer, can subscribe to 100 patreon creators creating only 1 customer object

ruby jungle
#

If you create a Checkout Session on your Connected Account then the Customer has to be on that Connected Account

#

What type of Connected Accounts are you using?

mystic rivet
#

standard

ruby jungle
#

Gotcha.

#

Then yeah each time you are going to create a Direct Charge you are going to need to create the Customer on the Connected Account as well

#

There is really no other way around it.

#

You likely want to list Customers on that Account first as well to check if you already created the Customer on that Account

#

And then re-use that Customer if so.

mystic rivet
ruby jungle
#

Yes

mystic rivet
# ruby jungle Yes

I don't mind using different type of, charge as long as I know that stripe connected accounts are responsible for their own fees and refunds, is that possible with other charges?

ruby jungle
#

No that's only possible with Direct Charges

#

With Destination Charges you would be responsible as the platform

#

And we do not recommend Destination + Standard

mystic rivet
ruby jungle
#

Because you as the platform control everything here

#

So you don't want your Connected Accounts to have the ability to issue refunds for instance

#

As that would only return funds to your platform, not to the actual customer

mystic rivet
#

Ok, so platforms like patreon tend to use express?

ruby jungle
#

Yeah most likely. But really just depends on what control the platform wants

#

It will certainly make it easier on your integration here in terms of controlling everything (Customers/Products/Prices) from your platform.

mystic rivet
#

I want to use express, but the fact that platform would be liable for any type of fraud is off putting

ruby jungle
#

Yep there are certainly trade offs

mystic rivet
#

can stripe do anything to prevent it?

ruby jungle
#

To prevent fraud? Or liability?

mystic rivet
#

fraud

ruby jungle
#

Sure we have many fraud controls and prevention measures in place.

#

That said, we won't always catch 100% of fraud

#

And you are ultimately responsible for preventing fraud on your platform