#mrcoles
1 messages · Page 1 of 1 (latest)
WHat exactly are you trying to do, and whats the unexpected result you're seeing? Can you show me an example in test mode?
But, yes, the application_fee_amount will be based on the "main" currency of the payment.
Are you saying that the same numerical amount is applied for other currencies where that amount value might not be appropriate?
Ah, yes
Automatic currency conversion doesn’t apply for any Sessions with multi-currency prices, subscriptions, or the following integrations:
Checkout Sessions using Connect parameters (for example, application_fee_amount, on_behalf_of, and transfer_data). These are the most common Connect integrations.
The only workaround here would be to manual transfer an appropriate amount after the payment succeeds, for example using separate charge & transfer: https://stripe.com/docs/connect/charges-transfers
This is more complex, but would allow you to transfer any exact amount you like to the connected account.
Oh interesting—does the fact that I’m doing direct charges (not destination) impact this in any way?
Hmm yes, it would. Since that's then not really an option.
(It would be very different to collect the payment via your platform first, not recommend to do that flow for standard accounts)
The workaround then would be collecting application fees outside of the checkout/payment, say by getting a payment method from the account holder and charge them appropriate fees on some basis (daily, weekly, monthly, etc)
Ok, I guess the only other approach is I just figure out the currency ahead of time and set that manually?
Does Stripe expose the API that guesses the customer’s currency?
No, that's driven by IP geolocation though so you can perform a similar check if you like, or ask the customer ahead of time what currency they'd like to pay in