#smiley717

1 messages · Page 1 of 1 (latest)

dry nimbusBOT
magic karma
#

You should test this out to inform you on how to work with different products. I'm not sure I understand your question

potent token
magic karma
#

Did you read the docs I sent you?

potent token
#

Yep, I have already worked on stripe connect accounts for invoice feature, we can only use one stripe connect account at a time?

#

If products are coming from several vendors, then how can we map products to specific vendors? also wondering if we can set multi connect accounts on the code.

# 
async function createPaymentLink() {
  const params = {
    line_items: [{price: '{PRICE_ID}', quantity: 1}],
    payment_method_types: ['card'],
    mode: 'payment',
    success_url: 'https://example.com/success',
    cancel_url: 'https://example.com/cancel',
  };
  
  // Set the Stripe version and account for this request
  const requestOptions = {
    stripeAccount: '{CONNECTED_STRIPE_ACCOUNT_ID}',
    stripeVersion: '2020-08-27',
  };

  const paymentLink = await stripe.checkout.sessions.create(params, requestOptions);
  return paymentLink;
}
#

If all products are from CONNECTED_STRIPE_ACCOUNT_ID, it works, but product1 is for CONNECTED_STRIPE_ACCOUNT_ID and product2 is for CONNECTED_STRIPE_ACCOUNT_ID2 , and then how can we handle this case?

magic karma
potent token
#

I need to implement once I confirm it.

magic karma
#

I don't understand what you mean.

potent token
#

When customers make purchases from our platform, we prefer to directly charge the sellers deduct application fees,

# 
const params = {
    line_items: [{price: '{PRICE_ID}', quantity: 1}],
    payment_method_types: ['card'],
    mode: 'payment',
    success_url: 'https://example.com/success',
    cancel_url: 'https://example.com/cancel',
  };
  
  // Set the Stripe version and account for this request
  const requestOptions = {
    stripeAccount: '{CONNECTED_STRIPE_ACCOUNT_ID}',
    stripeVersion: '2020-08-27',
  };

  const paymentLink = await stripe.checkout.sessions.create(params, requestOptions);

If I create paymentLink with above code, the payment will be directly sent to CONNECTED_STRIPE_ACCOUNT_ID instead of having our balance. right?

magic karma
#

Correct

potent token
#

Lets assume that.

PRICE_ID -> CONNECTED_STRIPE_ACCOUNT_ID
PRICE_ID1 -> CONNECTED_STRIPE_ACCOUNT_ID1 (different supplier)

If products are from different suppliers, I need to determine where products come from and separate the payment as well.

#

For example, PRICE_ID means vegetable from Vendor 1 (connect account) and PRICE_ID1 means fruit form Vendor2. How can we automatically charge to connect accounts when user pay?

magic karma
#

So you're using Stripe Checkout product to do that?

potent token
#

Yes, I am going to use it for now

magic karma
#

So you would need to know the account's ID before you create the Checkout Session, right?

potent token
#

I have stored connect account id's for vendors on our database.

#

When I create payment link, I can get their account's IDs.

magic karma
#

Okay, so if you know the account ID already, then what's the issue? Can't you simply store the price ID in your database alonside the Account ID?

potent token
#

personally think it's not possible, my question again like this....

// Set the Stripe version and account for this request
  const requestOptions = {
    stripeAccount: ['{CONNECTED_STRIPE_ACCOUNT_ID1}', '{CONNECTED_STRIPE_ACCOUNT_ID2}'],
    stripeVersion: '2020-08-27',
  };
magic karma
#

You can't set the accounts like that

#

You would need to set the account at the request level

#

Not at the top level

potent token
#

I wanna send CONNECTED_STRIPE_ACCOUNT_ID1 for price1, and CONNECTED_STRIPE_ACCOUNT_ID2 for price2 just take out application feee.

magic karma
#

I still don't understand what you're asking

#

You need to store the Price ID alongside the Account ID in your database if you want to be able to do a quick lookup and send both when you create the Payment LInk

potent token
#

As a marketplace platform, we are not only working with one vendor, multi vendors. my concern is how the payment is automatically separated to account ID by price Id.

price2 is not associated to CONNECTED_STRIPE_ACCOUNT_ID1 for example, it should be sent to CONNECTED_STRIPE_ACCOUNT_ID2

magic karma
#

You could just create Price1 on Account1 and then later on create Price2 on Account2. It's really not as complicated as you seem to think it is

potent token
#

Ahhhhh, Yessss

#

😄 then I don't need to add CONNECT_STRIPE_ACCOUNT for creating payment link?

#

because there are two prices for two connects accounts for the link. not sure which connect_account_id used?

potent token
magic karma
#

Again, you do need to pass the account header. And you do need to store the price id alongside the account id so that you can look them up when you create the payment link

potent token
#

I am so sorry for bothering you...

# 
const params = {
    line_items: [{price: '{PRICE_ID1}', quantity: 1}, {price: '{PRICE_ID2}', quantity: 1}],
  };
  const requestOptions = {
    stripeAccount: '{CONNECTED_STRIPE_ACCOUNT_ID1}',
    stripeVersion: '2020-08-27',
  };
  const paymentLink = await stripe.checkout.sessions.create(params, requestOptions);

Please see above code, Where do you think the payment go? CONNECTED_STRIPE_ACCOUNT_ID1

magic karma
#

It's alright, I just think you may need more help than I can give you. Are you a web developer?

potent token
#

Yes

#

I love working with stripe payment gateway system for many websites, but always need to make sure it's working well.

#

@magic karma thank you for you time today and I do appreciate it. let me figure it out a little more and will get back to you once I try your approaches.

magic karma
#

Sounds good. Best of luck