Plugin does not interpret mlang/multilang tags when sending data to Stripe

[Raymond Frangie]

Hi,

When creating a new enrolment method, the data sent to Stripe as a product contains the full course name including the tags, and does not interpret the tags properly. There is also no field in the Enrolment Method to customise or name the product for Stripe and respective invoicing.

For example, in our course name, this is the text:

{mlang en}CCP0001.3 – Cybersecurity Bootcamp Program{mlang}{mlang ar}برنامج المعسكر التدريبي للأمن السيبراني – رقم ٠٠٠١.٣{mlang}

In Stripe, the product appears exactly like that with the {mlang} tags, not interpreting the language used. This now adds this full text, including the tags, onto the Stripe invoice.

It appears we can change the name (in test mode) in Stripe so that it reflects a better name, but how does this affect the enrolment method?

Can we somehow how a dedicated naming field in the enrolment method so that we don’t have to go log into Stripe and make product name changes?

Cheers,
Ray

[dualcube]

Hello Ray, Thanks for pointing this out.

You’re right, the plugin currently sends the full course name (including {mlang} tags) to Stripe, which results in raw tags appearing in the product name and invoice. At the moment, there’s no field to customize the Stripe product name directly from the enrolment method.

We agree that adding a custom name field would be a valuable improvement. Our development team will review this and get back to you with an update soon.

In the meantime, renaming the product manually in Stripe (especially in Test Mode) is safe, as long as the product ID and pricing remain unchanged.

Thanks again for your feedback!

[Raymond Frangie]

Hi,

Great, thanks! I look forward to an updated plugin that resolves this 🙂

Cheers,
Ray

[dualcube]

Hi Ray,

You’re most welcome! We’ll keep you posted as soon as the updated plugin is ready. Thanks again for your patience and valuable input.

[Author]

Posts