TOPIC: Problems with DTRegister and PayPal

On a client website the company I work services, we've noticed that if a customer leaves before paying in paypal the customer registration record is lost and is not posted to the DT Register admin. Is there a way to show all records whether they finish paying or not?

Hello. This means you don't have PayPal IPN setup correctly as noted in the instructions. IPN is needed so when payment is made, DT Register continues and creates the record whether the user returns to your site or not.
- IPN must be enabled in your paypal account
- sending of IPN messages must be enabled (in personal accounts)
- Auto-return must be OFF in the account
- Permissions must be correct on your site (755 for directories and 644 for files)

Thanks.

Thanks for the reply. This has nothing to do with IPN. If the user clicks pay with PayPal and something happens(loss of internet, user error, lost password..) the record is lost. Our client deals with customers that are not particularly computer savvy and there are time when problems arise. Or a customer may have second thoughts and end the process. Our client needs the ability to check in with potential customers as well as customers with failed transactions. The record should be entered into the database as a 'Payment Pending' status when the 'Pay with PayPal' button is clicked.
Thanks for your help in this matter,
-DCJ

This is the exact issue I alluded to in my thread - you gave me the same IPN troubleshooting steps. This is not the issue - the issue is that NO record is being created! The second they hit the submit button after the confirmation of data entered, it should be saved to the database! THEN worry about the paypal transaction.

Agreed, then there is a record of the registration attempt whether or not the payment goes through.

This can often help signify payment problems that we can trouble shot before they become a larger issue. Without this, we have no way of knowing how many people have filled out the form and not been able, or chosen not, to pay.

Will there be any response to this issue? I really like some of the features of this component, but I have a website to get running and I don't have time to wait an extended period of time for a response to SUCH a critical issue.

You can close my other thread as this is the same issue, and requires the same bugfix (and yes, it IS a bug - it may be operating the way you designed it, but that just means it is a design/logic bug)