tax | python code I wrote over a weekend to compute tax rates

Big thanks to @BernhardDöbler for getting me to look into where ChartData comes from. Since this was inherited code, I had to look into this. It turned out that ChartData was created with the following line of code.

You can specify for each column separately aggregate function in named aggregation:

So I was working with Stripe on this, and here is what they wrote:

I understand your point that tax amount should be left to the platform, while the rest is transferred to the connected account, however at its core, that is not how the Billing and Connect product operate.

When you create a subscription, the subscription object will generate invoices, which will generate payment_intents :

Subscription Invoice - Payment_intent

Invoice -Payment_intent

The payment_intent contains an array of properties, which include the amount, the currency, the customer if there is one, etc. However, it has no notion of products, discounts, or taxes, as these are properties of the subscription and invoice objects.

Connect charges (i.e. Direct, Destination and Separate charges and Transfers) are processed at payment_intent level, not subscription / invoice level. They too do not have a notion of products, discounts and taxes. When you set up a Connect process from the Checkout session

• in your case, with the subscription_data.transfer_data attributes, the amount_percent cannot relate to that of the subtotal, as this subtotal amount does not exist at payment_intent level.

And here is their suggested solution. I was able to implement this without too much trouble, so it works.

-Create a Checkout session without any Connect attribute. There is a transfer_group parameter that can be set for Checkout sessions, but it isn't available for subscriptions. Nevertheless, omitting it doesn't prevent you from handling SCT later on.

-Save the charge ID ch_xxx from your invoice's succeeded payment. You can receive this information from the charge.succeeded event or payment_intent.succeeded event. You may also want to listen for invoice.payment_succeeded or invoice.paid events to get the subtotal amount.

-Create a transfer, with the connected account's acct_id as destination, the invoice's subtotal as amount, and the charge's ch_id as source_transaction : https://stripe.com/docs/connect/charges-transfers#transfer-availability The source_transaction parameter is crucial here - it will link the transfer to the charge, which will ensure funds are transferred even if they aren't available to your balance yet, and will create the missing transfer_group automatically.

Your input() call returns a string, not an integer.

What you want is not a pivot, as pivot reshapes the data, while you here want to duplicate/shift it (you have more data cells after than before).

To take a simpler example, the goal is to go from something like this (6 values):

With your current code you can add a column between the existing columns, however:

• The woocommerce_my_account_my_orders_columns filter is deprecated since WooCommerce 2.6.0. and replaced with woocommerce_account_orders_columns
• The part to add content in the column is missing

To add content you can use the woocommerce_my_account_my_orders_column_{$column_id} hook, where $column_id need to be replaced by order-category in this particular case

So you get:

Consider the following changes.

Laravel upserts do a single query containing all the rows are made while using upsert which includes on duplicate key update in MySQL and on conflict ... do update set in Postgres. This command instructs database to update record if it already exists. You need to pass cart_id to MySQL tries do INSERT before get errors on duplicate.

https://laravelproject.com/laravel-upsert/

Begins tracking the given entity and entries reachable from the given entity using >the Modified state by default, but see below for cases when a different state will >be used.

Generally, no database interaction will be performed until SaveChanges() is called.

My guess is, that the Account is tracked until the changes are saved.