Adding WooPayments transaction id (txn_xxxx) into order meta

[geektzu]

Description

Currently, the WooPayment intent id is added to the order meta. When a merchant is integrated to NetSuite the payment intend id could be synchronized with the orders to NetSuite. However, the transaction id is not included as part of the order meta. It posts a challenge for a merchant who uses NetSuite for transaction reconciliation. They can get transaction ids (txn_xxxx) from the "Payments" -> "Transactions", however, txn_xxx were not synchronized over to NetSuite.

Acceptance criteria

Add a new meta field to register WooPayments transaction id. So a NetSuite connector such as In8Sync can pick and synchronize to NetSuite.

Designs

No UI required

Testing instructions

1. A new meta field must be present in Woo order after a payment is charged via WooPayments.
2. Use the Store Toolkit plug to inspect the order meta for transaction id (txn_xxxxxx). Go to WooCommerce -> Orders.

Dev notes

Additional context

P2: https://wp.me/pcJe93-3R9

[geektzu]

@souravdebnath1986

[RadoslavGeorgiev]

Asked for a responsible team in Slack: p1702301046121889-slack-C04DN7Q51KK

[geektzu]

The transaction id here in the meta should be of the "charge" transaction for WooPayments. As there is already a "_transaction_id" in the order meta to store the payment intent id that pays the order. Suggest to have another meta field such as "_charge_transaction_id" for transaction id (txn_XXXX) of charge transactions. @RadoslavGeorgiev @anu-rock

Also, when _charge_transaction_id will be added to order meta? Upon the order transited to "Processing"? We need to re-configure the in8Sync rule for Woo->NetSuite synchronization accordingly.

[geektzu]

@RadoslavGeorgiev @souravdebnath1986 @anu-rock let me know if there is more clarification needed. Wonder if it will be included in the next version of WooPayments? Any ETA we can anticipate?

[anu-rock]

@geektzu

Just to be sure: the attach_intent_info_to_order method currently saves the charge id (ch_xxx) to order meta. Seems like this is not sufficient and we'd like to also save the transaction id (txn_xxx), correct?

Wonder if it will be included in the next version of WooPayments? Any ETA we can anticipate?

Fusion will prioritize this issue in the current sprint. If all goes well, the change will be included in v7.0.0.

[geektzu]

@anu-rock yes. As the transaction ids (txn_xxxx) are the ones in WooPayments -> Transactions report.

[anu-rock]

@geektzu You can keep an eye on the implementation progress at #7945. Feel free to leave your comments there.

[dechov]

The charge ID mentioned by @anu-rock (ch_xxx) is also in the WooPayments -> Transactions report, and would potentially be more useful since a charge (and likewise, an order) can potentially have multiple "transactions" (charge, refund, dispute…) – at least in theory, not sure how this particular accounting integration is supposed to work. @geektzu Might the charge_id in the Transactions report be enough to associate with the _charge_id in order meta?