You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Where can I find a list of available merge tags for WooCommerce, to use in the payment/transaction description?
[…] For the custom payment description I'm now looking for the merge tags for 'single product name' and 'customer name', to make each transaction/payment from WooCommerce more recognizable, both in the Mollie dashboard and in the bank account.
[…] Are there any ready-made merge tags available for this? Or can you help me with a code-snippet to add these in the functions.php of the active theme, to make them available for use in these settings?
We have a few tags available (and mentioned) for use in the WooCommerce payment method description setting: {order_number}, {order_date}, {blogname}.
Specifically for Mollie, there's also a filter pronamic_pay_mollie_payment_description:
However, we could also add some kind of merge tag controller which allows for payment data being used through tags in the payment description in all supported plugin integrations. For example:
From customer:
We have a few tags available (and mentioned) for use in the WooCommerce payment method description setting:
{order_number}
,{order_date}
,{blogname}
.Specifically for Mollie, there's also a filter
pronamic_pay_mollie_payment_description
:Custom tag replacements can also be added by hooking into the
pronamic_pay_pre_create_payment
action:I've created a Gist for customer and item names tags, using this action:
However, we could also add some kind of merge tag controller which allows for payment data being used through tags in the payment description in all supported plugin integrations. For example:
{site_title}
{user:name}
{customer:name}
{customer:first_name}
{items}
payment lines namesInternal Help Scout ticket: https://secure.helpscout.net/conversation/2239610520/25619
The text was updated successfully, but these errors were encountered: