#morieeeenyo_best-practices
vocal anchorBOT
š Welcome to your new thread!
ā²ļø We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
ā±ļø We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
š This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1494222133012987936
š Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- morieeeenyo_api, 6 days ago, 8 messages
modest galleon
hello! gimme a while to go through what you said
Is it a common approach to manage multiple Payment Intents under a single order group and capture them separately with prorated amounts at the time of shipment? If there is a more recommended design pattern, we would appreciate your guidance.
It's fine to do so. There isn't a better or more recommended design pattern that I can think of.
We plan to call capture with amount_to_capture set to a value lower than the authorized amount, which will release the remainder. Is this the correct approach?
When you do a partial capture (i.e., amount_to_capture less than the authorized amount), the remaining funds are automatically released back to the cardholder. There's nothing extra you need to do on your end to release them.
stiff scroll
Thank you for your response!
One more question regarding the capture amount:
Payment Intent B was originally authorized for Ā„5,000 (the price of Order B). However, after merging,
Order B is soft-deleted and due to proration, only Ā„1,000 ends up being captured against Payment Intent
B.
Is it acceptable to capture a Payment Intent for an amount significantly different from what it was
originally authorized for? Are there any concerns from Stripe's perspective regarding this approach
(e.g., disputes, cardholder confusion)?
modest galleon
Is it acceptable to capture a Payment Intent for an amount significantly different from what it was originally authorized for? Are there any concerns from Stripe's perspective regarding this approach (e.g., disputes, cardholder confusion)?
Yes, this is acceptable and not uncommon at all. A good example would be when a customer places an order for multiple items, but some go out of stock before shipment. In that case, the merchant would only capture the amount for the items actually shipped, which could be significantly less than the original authorization.
From Stripe's side, there are no concerns with this approach. Regarding disputes and cardholder confusion, those are things you'll want to manage on your end. It's worth making sure your customers are informed about any changes to the charged amount e.g. what each amount was charged for, to help minimize any confusion or potential disputes.
stiff scroll
Thanks!
One more question regarding receipt issuance.
We currently issue receipts on our own (PDF + email) rather than using Stripe's automatic receipt
emails. Our current implementation issues one receipt per Purchase, using the tax_included_total_price
of that Purchase as the amount on the receipt.
After merging, the capture amounts on Stripe are prorated across two Payment Intents:
Payment Intent A ā captured Ā„20,000
Payment Intent B ā captured Ā„1,000 (Ā„4,000 released)
However, the receipt we issue to the customer would reflect the actual order amount of the merged
Purchase (e.g., Ā„21,000 total), which differs from the individual captured amounts per Payment Intent.
Is there any concern from Stripe's perspective about the receipt amount not matching the individual
charge amounts? Or since we're managing receipts independently of Stripe, is this entirely our own
responsibility to handle as we see fit?
modest galleon
Is there any concern from Stripe's perspective about the receipt amount not matching the individual
charge amounts? Or since we're managing receipts independently of Stripe, is this entirely our own
responsibility to handle as we see fit?
No issue from Stripe as you're managing receipts independently and you would be responsible for handling it as you see fit
stiff scroll
In our case, when multiple orders are merged into a single shipment, would you say it is common practice
to issue a single consolidated receipt to the customer rather than separate receipts per Payment
Intent? We are deciding how to handle this on our end and would appreciate any insight from what you
typically see with other merchants.
modest galleon
Honestly, this is a bit tricky for me to advise on directly. Every merchant handles things differently, and we don't really have visibility into how they'd choose to approach this.
What I can share, from my own experience as an online shopper, is that I've always received a receipt for each individual payment I've made. I can't recall a time where I made 5 separate payments and received just one consolidated receipt for all of them. It's also worth noting the distinction between a payment receipt and an order confirmation or shipping notification. A customer might receive 5 payment receipts, but still get a single email letting them know all 5 orders will be shipped together.
On top of that, receiving one receipt per payment likely makes it easier for customers to reconcile their transactions.
It might also be helpful to look at how large e-commerce retailers handle this kind of situation, as that could give some useful real-world context.
stiff scroll
Thank you.
I have another question:
When two Payment Intents are captured separately with prorated amounts, will the cardholder see two
separate charges on their card statement? Also, if the capture amount is less than the original
authorized amount, will the cardholder receive any additional notification?
modest galleon
Two separate Payment Intents captured separately
Yes, the cardholder will see two separate charges on their statement. Since each Payment Intent represents its own distinct charge, each capture will appear as an individual line item, which also makes it easier for the cardholder to reconcile their transactions.
Capture amount less than the original authorized amount
Stripe itself does not send any additional notification to the cardholder when the captured amount is lower than what was originally authorized. However, the cardholder may notice the difference depending on how their bank or card issuer handles it. Many banks show pending authorizations in their apps or statements, so the cardholder might initially see the higher authorized amount, which will then update to reflect the lower captured amount once it settles. Whether or not their bank proactively notifies them of this change is entirely up to the issuer, as that falls outside of Stripe's control.
stiff scroll
Thank you for all your help so far! I'd like to confirm our overall understanding before we proceed with
implementation.
Our planned approach:
- When multiple orders are merged into a single shipment, we keep the original Payment Intents as-is on
Stripe without any modification. - At the time of shipment, we capture each Payment Intent separately with prorated amounts (e.g.,
Payment Intent A captured in full at Ā„20,000, Payment Intent B partially captured at Ā„1,000 with Ā„4,000
released). - Receipts are issued independently by our application and are not tied to individual Stripe charge
amounts.
Our understanding based on your responses:
- Keeping multiple Payment Intents and capturing them separately with prorated amounts is an acceptable
and common approach ā - Using amount_to_capture lower than the authorized amount will automatically release the remainder ā no
additional action needed ā - Stripe does not send any notification when the captured amount differs from the authorized amount ā
any customer communication is our responsibility ā - The cardholder will see two separate charges on their statement, one per Payment Intent ā
- Receipt amounts do not need to match individual charge amounts since we manage receipts independently
ā - Issuing one receipt per Payment Intent (rather than a single consolidated receipt) is the more common
practice ā
Does this accurately reflect how Stripe works, and is there anything we may have misunderstood or
missed? Also, is there any additional advice or potential pitfalls we should be aware of before
implementing this approach?
modest galleon
What you have above looks correct! Any other questions or edge cases will likely surface naturally as you work through the integration. Nothing else specific comes to mind right now, but feel free to reach out as things come up and we'll be happy to help!