Here is how you would setup the Payment Processed so it does not allow double points.
Setup the same rule as you had before on Payment Processed but add this Custom Constraint:
{STATE:Loyalty} Not Equals True
Then add an Update Ticket State action that uses State Name: Loyalty
State: True
It might look like this.
Remember you would have your Create Account Transaction action in it as well.
So this rule would check if Ticket State Loyalty is anything but true and then execute if it is. If Loyalty is True it wont execute… if executed it sets state to True.
@alex1 its best to use payment processed so its based off amount spent. If you do it on order updated… then if order is cancelled and another order added it wont cancel your points…leading to abuse.
Instead of Ticket Total we could use ProcessedAmount and add points based off amount processed. If you do this then you might not need the constraint. Syntax would be like:
[=TN('[:ProcessedAmount]') * 5/100]
This tells it to do 5% for amount processed instead of ticket total. Meaning it wouldnt matter if you did two payment types and you could ignore the constraint i just told you about.
@alex1 this shows you two possible routes you can take with Payment Processed event. Using the last one is preferred as its the simplest all you would do is change the expression.