t4k4

Hi there,

I see that the thread was marked as resolved (maybe by mistake).
Did you release a fix for this?
I don’t see anything about it in the changelog.

Sure, here’s how it looks like:

curl -X POST https://example.com/wp-json/wc-shipment-tracking/v3/orders/645/shipment-trackings \
    -u consumer_key:consumer_secret \
    -H "Content-Type: application/json" \
    -d '{
  "custom_tracking_provider": "Custom",
  "custom_tracking_link": "https://example.com?q=%1$s",
  "tracking_number": "12345678"
}'

Actually, we don’t really “use” them at the same time and only one of the two is either available on the checkout page.
We are basically hooking into the ‘woocommerce_available_payment_gateways’ filter and unset the one that is not required. Is there a better way to achieve this without creating a conflict?

Payment gateways are usually charging a % + a flat transaction fee.

When a customer is paying via Stripe, we can see how much Stripe charged us to process the payment on the edit order page.
For a recent order below the order subtotal we can see the following…
Paid: $136.01
May 10, 2021 via Card
Stripe Fee: -$4.24
Stripe Payout: $131.77`

Stripe is creating using the “_stripe_fee” custom meta key while PayPal is using “PayPal Transaction Fee”.

Solved!
The issue was actually coming from the currency rate from WooCommerce EU VAT Assistant

Hi @gambitph

Is it at least possible to get the build files? ??