-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show rate on transaction details page if a fee was subject to a currency exchange rate #1342
Comments
Marking as blocked until its relevance is clarified with David. |
Removing blocked label, since decision from product team is needed. Moving to product review queue. |
hey @vbelolapotkov ! just wanted to check if there's been any update on this? |
@rogermattic, no progress I'm aware off. I see it's been relabeled for Gamma, so tagging @mjdeacon and @deepakpathania to provide any further updates. |
No updates from us, was added to our backlog based on the |
Not at all! But I was wondering if I could help extracting and adding a solution here based on my design explorations in this P2 post: p6riRB-9T6 |
Thank you @rogermattic for the exploration and suggested designs. There was a missing piece of information about the fee conversion rate, which was not available for the timeline. It will be added on the server side. |
Awesome! As mentioned on Slack I noticed the P2 and design reference was outdated here so I wanted to update it here:
Let's keep the conversation going here! |
The currency of the fee charged for a transaction is based on the store's location (to be precise, the location specified in the Stripe on-boarding when setting up the WooCommerce Payments account).
If a transaction is made in a different currency, we have to convert the fee into the same currency. This will use an exchange rate determined by WooCommerce Payments, which may be different to the exchange rate used by Stripe for the transaction itself.
To avoid confusion, all this information needs to be accessible in the transaction details page.
Details: paJDYF-13A-p2
The text was updated successfully, but these errors were encountered: