We use PayJunction as our payment processor. They can accept transactions using their Authorize.net emulate. I had that all setup and it was working fine. It no longer works. I have a ticket in to them to see if they have made any changes. They do not recognize the username being passed to them ("The merchant API login ID is invalid ...").
In the interim, I decided to switch to PayPal since that always works. But PayPal doesn't work either. PayPal shows the error, "We cannot process this transaction because there is a problem with the PayPal email address supplied by the seller." PayPal was also working when I setup my events.
I was using DT Register version 2.8.2b, I upgraded to 2.8.4 without success.
Currently I cannot process payments with either of my processors. Credentials for two different processors are not being passed properly. I do not expect DT Register to fix the situation with PayJunction using their Authorize.net emulator. I do hope you have some experience with PayPal.
Where in the code is the username being passed to the payment processor. This is the area that seems to be broken.
I have done additional testing and narrowed down where the problem is. My scenario is that we take group camp registrations online charging a minimum deposit of $100 per member instructing registrants to come back later and pay the balance of their camp registrations later.
When a user registers a new camp registration, everything works as planned. All group information is recorded, deposit is calculated per group member and the payment is processed.
Without changing anything, the user goes back to manage registrations and clicks on the "Pay Now" link for the registratin already created. Regardless if they make another partial payment or pay the balance due, the process fails to connect to the payment processor. I'm guessing the login ID is null at this point. PayPal responds with a message that "there is a problem with the PayPal email address supplied", my production payment processor (PayJunction) sends message that "The merchant API login ID is invalid ..."
Can you replicate this scenario and can you provide a fix for this. Being able to collect the balance due on registrations is critical.