#mattvb91
1 messages · Page 1 of 1 (latest)
Hello 👋
The dashboard uses different set of APIs than the ones we publicly support.
This could be one of the dashboard only features.
BalanceTransaction should have the fees that were charges for a payment
https://stripe.com/docs/expand/use-cases#stripe-fee-for-payment
Can you share the PaymentIntent ID you're looking at?
Thanks @buoyant zodiac . The id is: pi_3NdCEDPrr2bUx3UQ1glOJxCW in dev mode
The fees its showing me is "amount": 188.
However that is wrong because the amount captured was adjusted. (its correct on the frontend)
Ah so there was a processing fee refund. There should be a separate balance transaction object for it
basically what im trying to do is generate an invoice for the connect client that lists the stripe fees. Where is the best event to hook into to do that? Im trying to listen to payment_intent.succeeded and get it from there
actually, I don't see a separate balance transaction object for this
I don't see a specific type for stripe_fee_refund or something similar either
https://stripe.com/docs/api/balance_transactions/object#balance_transaction_object-type
maybe im using a wrong approach from the start. Basically my connect clients need to verify a payment method (card) works in order to start a process in the system. THen I need to charge based on useage after the end of the process.
The way I currently do that is to create a paymentIntent with amount (50 EURO) with capture_method: manual and then update the intent based on useage. Maybe theres a better way? So then it doesnt have to refund?
Typically, folks rely on using SetupIntents to validate and store PaymentMethods
ha! That might be the better way to go thanks ill take a look
We have a guide here 🙂
https://stripe.com/docs/payments/save-and-reuse?platform=web&ui=elements
Thank you appreciated!
NP! 🙂 Good luck
so this does look like it will work. However does that not expose my connect clients to issues where for example: I do a setupintent, they proceed with a process that is metered. Now at the end I charge the value that was metered and using the setupIntent it could potentially fail at this side and not capture anything?
Whereas the payment method manual means at the beginning it confirms that a payment can be made? Whereas its potentially exposing my connect clients to losses if at the end of the metered the intent fails (insufficient funds on card for example)
basically, kind of important to my process is this part:
"""
After a payment is authorized, the amount is guaranteed and held on the customer’s payment method.
"""
Which is not the case from my understanding using the setupIntent
Yeah, SetupIntents just save a PaymentMethod for future use, they don't place a hold on any funds.
I'm not fully clear on your usecase though unfortunately. Can you give me an example of how you would like to charge these users here?
Ah thats a pitty yea i definitely need that.
So basically I have the case where connect clients offer a metered physical service to their own customers. Thats why I need the hold confirmation because physical goods are exchanged.
I then need to generate an invoice for my connect clients that show the list of fees + the payout but I cant get the accurate fees at the moment
or even simpler. I need to show my connect clients what payout to expect from that payment intent id: pi_3NdCEDPrr2bUx3UQ1glOJxCW but at the moment I cant do that due to a refund value missing after adjusting the captured amount after the metered process was completed.
@ornate tinsel weirdly enough it lists the application_fee correctly from when I update the capture_amount. I instantiate it with 0 and then update once the metered value has been calculated. So its (half) working. Just not showing the stripe_fee correctly
So the last piece is still figuring out how to see the processing fee refund?
I am having trouble finding info on this. I will reach out to my colleagues for help looking in to how to acheive this
Just not showing the stripe_fee correctly
Hi there. Looking into this. Where exactly are we surfacing an incorrect fee?