#morieeeenyo_api

1 messages · Page 1 of 1 (latest)

craggy dustBOT
#

👋 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/1491959915986817205

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

heady escarp
#

Definitely not 2. And I think 1 and 3 are quite similar in API perspective. What would you do differently in API perspective?

#

To me they are the same as you keep separate PaymentIntent and also capture separately

umbral shale
#

Thank you for clarifying — that makes sense.

To confirm our understanding: keeping both Payment Intents and capturing
them separately is acceptable, and the difference between Approach 1 and 3
is purely on our data model side, not on the Stripe API side.

With that in mind, we have two remaining questions:

  1. When the shipping fee changes after consolidation (e.g., combined
    shipping becomes ¥700 instead of ¥500 + ¥500), how should we decide the
    capture amount for each Payment Intent? Should we split it proportionally
    by product price, or is there a recommended approach?

  2. If the new capture amount still falls within the original authorized
    amount (which we set at 2x), can we simply capture the adjusted amount
    without re-authorizing?

heady escarp
#
  1. Totally up to you 🙂
  2. Yes you should be able to. Please test in Sandbox btw
umbral shale
#

Thank you so much! That's very helpful.

To summarize what we confirmed:

  • Keeping both Payment Intents and capturing them separately is fine.
  • The split of the capture amount is up to us.
  • As long as the new amount is within the originally authorized amount,
    no re-authorization is needed.

We will test this in Sandbox before moving to production.

Thanks again for the quick and clear responses!