Hosted Payment Page - Account Creation's button isn't using metaData information
Hello, my email is [email blocked]
We have a problem and we propose a solution.
Is it an easy change or do you see another solution to our problem?
Problem: We want to send the welcoming mail in English or French depending on a field: $metaData.lang
but we're always sending mails in French.
The welcoming mail is the mail sent immediately after a customer is subscribed.
As our Hosted Payment Page - Account Creation creates a subscribed account, we can't update $metaData.lang
between the account creation and the hook sending the welcoming mail.
We tried to update metaData in the hook for the event "NewSubscription", but it's updating metaData
after the welcoming mail is sent.
We're sending the desired language as metaData
in the url for the Hosted Payment Page - Account Creation
For example https://360dev-eur.chargevault.com/create?code=558&planCode=BAS...
Suggestion: The page's button creates an account with the metaData
information in the url. Like that we can guarantee that the welcoming mail will employ the desired language.
Discussions are closed to public comments.
If you need help with Cheddar please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Matthew on 10 Sep, 2020 08:10 PM
Stephane,
Thanks for reaching out, I will bring this up to our engineers and let you know as soon as possible.
Support Staff 2 Posted by Matthew on 14 Sep, 2020 08:25 PM
Stephane,
Thanks again for reaching out and sorry for the slight delay in getting back, I have a few options for you. To answer your question, this is a known limitation of our Hosted Payment Page and would require us to edit the code for your request.
In order to do this, we have an accelerator discount program where our engineers would quote how much it would cost to implement your solution and you would pay half the cost if you'd like to proceed. This is option 1.
Alternatively, you could move your product to be integrated with the API. This would allow you more functionality and customization. This is the recommended option, but we're happy to help either way.
Let us know if you have any other questions or know what you want to do.
Thanks,
3 Posted by Stéphane Géraud on 17 Sep, 2020 03:33 PM
Thanks for your reply.
We found a workaround.
We can close this conversation.
Matthew closed this discussion on 17 Sep, 2020 06:52 PM.
Matthew closed this discussion on 21 Oct, 2020 03:51 PM.