i’m trying to implement a surcharge for credit transactions. I’m using a surcharge transaction with a 1% fee.
The surcharge get applied correctly when i press the button and toggles off when i dont.
However i get weird behaviour when processing a payment with the surcharge on. The ticket itself doesn’t seem to close and it gets stuck in a loop where i can’t get back to the entity screen. My only way out is to kill samba and login again.
Any help would be appreciated. I’ve copied below the rules i think are relevant, but please let me know if you want to see more.
I think it might have to do with the remaining amount, but can’t work it out.
Hi @Jesse, to be honest, i think that’s because i was messing around with it.
When i close the ticket and then open it, the order does show submitted, but if i then go to settle with the CC surcharge, it does the same behaviour. I don’t think (i could be wrong) that this has something to do with the state as i haven’t had any issue with my state behaviour previously.
issue only occurs when the CC surcharge is added, otherwise everything works fine.
Below is another example where the issues manifests… note this time the orders are submitted and ticket state is unpaid. What is definitely not triggering is the rule noted above where it’s relaying on remaining amount to be 0 before closing the ticket.
See the screen shot below. After i process the payment, you can see that the balance is still showing as not being 0. I think this is where the issue lies. For some reason, having the credit card surcharge on there is stopping it processing the payment properly and so the rest of the ticket closure doesn’t fire.
So to follow up on this after checking your database…
You have a lot of custom automation in Ticket Closing rules, this is your constraint which is actually true most of the time and is a reason why your tickets never close properly.
I unmapped all of your ticket closing rules because I have no understanding on why you play with so many states in the same time. I am sure you tried to create something nice but from all the rules that play with statuses I would say you over thought it.
I am not sure what this is supposed to check as its not checking any payment processing, its just checking remaining amount = 0.
After unmapping most of your status changing automation it started to work fine - both statuses and payments.
You have constraints and rules in place that stop you from closing the ticket before it was paid
Your automation with statuses is not working properly as they are not being changed in right events, making it impossible to get out of the order/ticket screen.
There are many overlapping rules that are simultaneously breaking your own workflow - these were just the basic default ones and there are about dozen more you created.
Its really difficult to understand what you tried to do but I would suggest you to try again from the start and think your workflow through.