#jupiterdev-application-fee

1 messages · Page 1 of 1 (latest)

fathom blaze
#

Hello 👋
give me a moment to look into it

brave tree
#

thanks

fathom blaze
#

when you say

also sending money to user's account as well.
could you provide more context here?

brave tree
#

I mean connected stripe account.

#

so here's what we want.

#

our users are registered stripe customers.

#

and we want to get our application fees from customers through stripe.

#

does it make more sense?

fathom blaze
#

Yup that part makes sense.
I'm just confused about the concern you have about direct charges.
With direct charges, you can deduct the application fee according to your usecase.

brave tree
#

yes

#

so here's the code for direct charges.

  payment_method_types: ['card'],
  amount: 1000,
  currency: 'usd',
  application_fee_amount: 123,
}, {
  stripeAccount: '{{CONNECTED_STRIPE_ACCOUNT_ID}}',

});
#

and we want to get only application fee not sending to connected stripe account.

#

so here's more detailed working flow.

#

So we're Defi service providing users to be available to buy cryptocurrencies from their bank account.

#

and buying cryptos will be handled by Wyre not Stripe.

#

But we want to handle our service fee with Stripe.

#

only for our service fee.

#

hope this makes more sense to you.

fathom blaze
#

so if I understand correctly,
Lets say I bought $10 crypto as a customer

  • Application fee: $2 should go to your account
  • Rest of the money you'd want to send to wyre right?
brave tree
#

Yes

fathom blaze
#

You can add Wyre as a connected account

brave tree
#

hmm

#

that's not how it should work.

#

actually wyre is working independently.

#

Let's say user wants to buy $10 crypto.

#

$10 will be handled by Wyre side.

#

And then let's say calculated service fee is $1.

#

and we need to send $1 to our stripe account.

#

is there any way to send from customer's account to our account?

fathom blaze
#

Wyre will have to be connected to your account somehow in order for you to charge the application fee on the transaction
Unfortunately, there are no other way to charge application fee to a user.

brave tree
autumn fjord
#

@brave tree do you have more details about what's still blocking you?

brave tree
#

and I think we can handle our service fee with this api.

#

is it doable?

autumn fjord
brave tree
#

hmm, we don't use connect.

#

so just normal one time payment.

#

we can handle service fee as a normal one time payment.

#

I think.

autumn fjord
#

I don't follow you sorry.

#

You clearly seem to have 2 separate accounts: one for Wyre and one for your own business

#

So you usually use Connect for this, that's the way of doing this

brave tree
#

no

#

that's not.

autumn fjord
#

otherwise you have to collect 2 separate payments, one for Wyre and one for you

brave tree
#

We don't have account for Wyre.

#

we only have one account on Stripe.

#

And Wyre is independent payment flow.

#

as I mentioned earlier, Wyre is working independently.

#

And every Wyre transfer, we'll calculate our service fee and charge users for the calculated amount through stripe.

#

Does it make sense?

autumn fjord
#

Unfortunately no it does not

#

I know it's clear in your head, but it's not based on what you described and how you do that with one Stripe account and who gets what funds and who pays what and where

brave tree
autumn fjord
brave tree
#

what if we don't want to use stripe session?

#

but just want to stripe api.

autumn fjord
#

I have no idea what you call "stripe session"

brave tree
#

hmm

#

we have business account on stripe now.

autumn fjord
#

that is unrelated to what I said

brave tree
#

and we don't want to use any stripe UI or checkout.

#

we just want to use stripe on back end.

#

for creating charge for users.

autumn fjord
#

Are you PCI compliant? Do you understand what that entails for your entire business?

brave tree
#

Of course, I understand PCI compliant.

#

our users are already registered customer in stripe and have registered bank account through plaid as a payment method.

#

we don't need users fill out the card information.

autumn fjord
brave tree
#

What's the difference between payment_intents create and charge create ?

#

and which one is more appropriate?

autumn fjord
#

Both work, the latter has been deprecated since 2018 and we strongly recommend using PaymentIntent if you can. Though if you use ACH Plaid, then just ignore everything I said and stick with charges for now :p

brave tree
#

one last question.

#

because we'll charge through ACH, it will take several days?

#

if so, should we use web hook for track the status of charges or payment intents?

autumn fjord
#

yes

brave tree
#

Cool. thank you very much!

autumn fjord
#

it's still on Charges today unfortunately so that's why you're better off with the legacy integration based on what you described