Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The idea here is to work on #542
So I added some elements in the blade StripeSCA config blade to be able to define:
When computing the fee to pass to the transfer account, I sum the Booking fees and the fee defined before. Why? Because when you're doing a connect payment, the main account is supporting the Stripe fee, not the destination account. So I use the Booking fee to cover Stripe's fee and add the custom fixed amount fee.
That's indeed questionable. It works for me, it wouldn't work for everyone. Would be better, probably, to have all of this configured into the Stripe SCA blade under a Stripe Connect Section.
I would be glad to get your feedbacks.