#idhruv-schedule

1 messages · Page 1 of 1 (latest)

empty vine
#

hi! not much I can suggest here ,you just can't use those parameters together on that API, it's a limitation of that API

#

usually you don't use application fees and transfer_data[amount], you use one or the other.

#

i.e. you either take an application fee directly with application_fee_percent, OR you use transfer_data to transfer less than the payment and the difference is your 'fee'. So you wouldn't use both, and that API doesn't support using both.

jolly badger
#

okay, however my problem is that i would like to happen that simultaneously. So, application fees is for us as a company and transfer_data is for the hosts towards whom our customers paid

#

so whenever a subscription is active, we would first want our users to get charged per month, and whatever amount is charged we would like to earn a 10% commission on that amount and rest 90% goes to host connected accounts

#

is there a way to achieve this?

robust sentinel
#

So you're trying to facilitate transfers to 2 separate Stripe accounts from a single transaction?

jolly badger
#

yes kind of

#

otherwise we will not be able to track when subscription takes the cut, and when we should pay commission to ourselves and release the rest of the amount to our hosts

robust sentinel
#

That's not possible with destination charges like that, you'd need to use separate charges & transfers

jolly badger
#

alright, so is it possible to use separate charges and transfers with ongoing subscription? or maybe sync these extra charges along with the ongoing subscription

#

This is our ideal scenario:

We have built application in 3 stages. 1 - user 2 - our company and 3 - host

User pays for the spaces they book on the monthly bases and after they pay the amount, we should cut 10% commission and pass it in our company's stripe account, whereas the rest of the amount that user paid should go to host's stripe account

robust sentinel
#

alright, so is it possible to use separate charges and transfers with ongoing subscription? or maybe sync these extra charges along with the ongoing subscription
It should be yes, as you're facilitate the transfers yourself after payment (without passing application_fee_percent etc)

jolly badger
robust sentinel
jolly badger
#

okay. thanks for the document. Our problem is little complicated because if our customer subscribes to 12 months or more plan, and is willing to pay monthly, then we would like to automatically send this amount to our host's stripe id (ofcourse after cutting some commission for it) per monthly basis as soon as stripe's auto cut is triggered.

#

if not then what approach do you suggest to achieve this?

#

separate charges and transfers seems to be not supporting subscription schedules as per what I read

robust sentinel
jolly badger
#

okay

robust sentinel
#

and is willing to pay monthly, then we would like to automatically send this amount to our host's stripe id
You'd probably need to trigger a Transfer creation following the recurring payment success, using webhooks

jolly badger
#

https://stripe.com/docs/billing/subscriptions/connect

in the morning i tried with this api (normal subscription) and it had all the options to setup application fee as well as setting up connected account but then I was not able to configure start date for it. so do you think this has that support?

EDIT: because it has no start_date configuration support I left trying out using this method but I did read that there are these other things, still not sure if you can split using this method.

jolly badger
robust sentinel
#

Let's breakdown your model:

  • Platform X
  • Business Y
  • Customer Z

Customer Z has a subscription with Business Y that Platform X creates via Connect using destination charges. Assume $10 p/m, you want:

  • Platform X to receive $1 (10%)
  • Business Y to receive $9 (90%)
#

Is that right?

#

If that's the case, you just need to adjust your original code to:

default_settings: {
  application_fee_percent: 10,
  collection_method: "charge_automatically",
  default_payment_method: payload.cardId,
  transfer_data: {
    destination: "acct_1L84EtGg3F2IFWW1"
  }
},
#

This is a destination charge subscription: you (the platform) will keep 10% of each recurring payment (application_fee_percent) and the remaining amount will be transferred to transfer_data.destination (acct_1L84EtGg3F2IFWW1)

#

You don't need to specify your (platform) account ID for the 10% cut

jolly badger
#

okay let me try this and see how it goes, thanks a ton!