#cristiancalara_docs
silent masonBOT
👋 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/1283054480270692465
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
fresh siren
Can you confirm you've not built your integration yet, as it you currently have no payment flow?
desert bridge
We do already have this in production. It's just that now we need to implement the feature of updating the fee based on the payment method
fresh siren
What payment flow are you used today (in terms of payment element and intent sequencing)?
You can create an opportunity to inspect the payment method selected using our two-step flows with confirmation tokens.
Either client side: https://docs.stripe.com/payments/build-a-two-step-confirmation#create-ct
Or server side: https://docs.stripe.com/payments/finalize-payments-on-the-server?platform=web&type=payment#create-ct
desert bridge
We are actually using both checkout sessions and terminal payments. We can probably move from checkout sessions to the above. But not really sure how to tackle terminal payments
fresh siren
Checkout does not currently allow you to do this, there is no means to intercept the flow to inspect the PM and modify fees.
Genrally our guidance is to set your fees high enough to cover costs (plus your margin) for all payment methods offered
desert bridge
Yeah but for Klarna which is 6% that really doesn't work that well
fresh siren
For Terminal payments, can you clarify the scenario your trying to handle? Since klarna doesnt apply
desert bridge
Yeah so the feature was to also update the fees based on the card type. As Stripe also charges us based on if international card or not (and again, the difference is quite a bit, I think it was 1% difference)
fresh siren
You might want to consider the collect and confirm flow described here (but its beta and you need to request access):
https://docs.stripe.com/terminal/payments/collect-card-payment?terminal-sdk-platform=server-driven&process=inspect#process-payment
At this point, you can access attributes like card brand, funding, and other useful data from the PaymentMethod.
desert bridge
Okay, I see, yeah that might work. We might do the update to handle the Klarna use case and then wait for this to get out of Beta (or request access to beta) as the feature based on card types was lower prio.
Thanks a lot for the help, really appreciated
fresh siren
NP! Hope that helps 🙂