mefm247 | Stripe Developers | Page 1

torn wolfBOT May 30, 2023, 5:44 PM

#

frosty haven May 30, 2023, 5:46 PM

#

Do you have an example Payment Intent ID I can look at that's charging the full amount and doing the refund?

rain meadow May 30, 2023, 5:52 PM

#

Hi @frosty haven Thank you for the help, I really appreciate it.

#

This is a real intent: pi_3N8TS0GjuHEuu14r1iMYWOQX

#

FYI, we use a different Stripe account for testing.

frosty haven May 30, 2023, 5:56 PM

#

👍 give me a few minutes to take a look

rain meadow May 30, 2023, 5:57 PM

#

Thank you.

frosty haven May 30, 2023, 5:58 PM

#

The reason you're seeing a refund is because you're doing a partial capture - we need to do the refund to return the extra funds

rain meadow May 30, 2023, 5:58 PM

#

Yes, that bit I understood. I guess my question is how we should have implemented this, so it's not treated like a refund.

#

And thank you for the response.

#

I.e. we tell the client that it will cost 100 usd, but that we need to take a 50 usd deposit on top of it, which is partially refunded at the end or fully refunded if needed.

#

We don't know the full amount until the service is done by our team.

#

But we don't want to be left with unpaid extras.

#

i.e. If we only bill 100 usd, and try to bill another 20 usd, 4 days later when the service is done, but the card payment fails.

#

I was under the assumption that a hold, did NOT charge the card, but merely blocked the funds, and then we could capture the correct amount later.

frosty haven May 30, 2023, 6:04 PM

#

Let me clarify - in Stripe it's being modeled as a full charge + a refund, but to the customer it should still just appear as a hold until the capture occurs

rain meadow May 30, 2023, 6:06 PM

#

That's what I thought but that's not what clients are reporting and what we saw when we tested. It showed the full charge.

frosty haven May 30, 2023, 6:07 PM

#

Is it showing as a full charge even before the capture has happened?

rain meadow May 30, 2023, 6:07 PM

#

Yes

#

It did on one of my test cards (it's a real card but it was a test)

frosty haven May 30, 2023, 6:14 PM

#

Hmmm... this may just be an issue with your specific bank/card issuer representing the auth differently (we call out in our docs https://stripe.com/docs/payments/place-a-hold-on-a-payment-method at the bottom that some issuers don't distinguish between authorized/captured charges)

Place a hold on a payment method

Separate payment authorization and capture to create a charge now, but capture funds later.

rain meadow May 30, 2023, 6:14 PM

#

Ok, that could be the case indeed.

#

Here's an example I just created:

#

I'll delete the screenshot afterwards.

#

Payment intent: pi_3NDX34GjuHEuu14r15tYdQIz

frosty haven May 30, 2023, 6:16 PM

#

(I deleted the screenshot after seeing it)

#

Yeah, this is likely an issue with the specific UI you're looking at / your card issuer

#

As far as I can tell - this is definitely an uncaptured payment right now on Stripe's end

rain meadow May 30, 2023, 6:18 PM

#

Are there any other solutions that we can try?

#

Or best practices that other clients use?

#

i.e. 2 payment intents, with one fully captured and the second being captured later?

#

Some clients get scared when they see the extra charge and are cancelling their requests.

frosty haven May 30, 2023, 6:20 PM

#

It really depends on what your business model is like - I wouldn't recommend splitting them out unless these are actually two separate charges/fees

rain meadow May 30, 2023, 6:21 PM

#

It's an Uber like model, where we estimate upfront and then charge the correct value at the end once the trip has already taken place.

frosty haven May 30, 2023, 6:22 PM

#

Yeah I'd just stick to the single price then

rain meadow May 30, 2023, 6:23 PM

#

Got it. Thank you.

#

I'll ping back once I speak with my client, but I really appreciate your help today. ❤️

#

Hope you have an amazing week.

#mefm247