How to track (off-line) deposit payments?

Hi,

Sorry, I've searched around but couldn't find anything on this.

EB 2.14.5, deposit feature activated.
Situation: Registrant making off-line deposit payment (e.g. bank transfer).

Question: How can an admin track this in the system?

In the backend -> registrant record, I have only

• "Payment Status" set to "Partial Payment" (which is certainly correct)
• "Status" set to "Pending" (which seems also correct)

What to do to mark the record as "deposit paid, waiting for remainder payment"? And however I'd do this, how to notify the user that deposit was received?
Leaving "Payment Status" at "Partial Payment" but setting "Status" to "Paid" (which feels sort of logical) is not it: the user gets approval confirmation and ticket (as if he's paid in full already).

I can't verify right now what happens in case of on-line deposit payments, but there seems to be at least an EB email notification to user (and admin, which of course not possible with off-line methods), and maybe some "marking" of the registrant record as well?

So, what's the equivalent for manual action by the admin, how can he track deposits paid off-line?

Thanks in advance for some enlightenment.

Hi Thomas

At the moment, unfortunately, there is not an option to track it. Guess we can add a new status called deposit paid, waiting for remainder payment like you suggest. That can be implemented and I can try to implement it on Monday and send the updated package for you

For sending email when status changed to deposit paid, waiting for remainder payment, I will have to leave it for future development.

Regards,

Tuan

Thanks for another very quick reply, Tuan.

Adding such status ("Deposit paid" would do for a name, I'd say, because the rest is clear) would be a great first step.

Other than helping admins to keep the overview, registrants generally love and deserve to see if payments have been received, especially since off-line payments are mostly for larger amounts.
I can see that adding an email notification is more hassle. What would make sense anyway and should help until email were available, in case of deposit feature active, is a column added to users' registration history table in between "Amount" and "Due amount": <th>Deposit (or Deposit Amount)</th>
The <td></td> may contain either "Pending" or "Paid", depending on status and unless I'm overlooking something
However, if you don't have the time for modding the table, it won't be hard to add it in the view for anyone who needs it quickly once the new status exists.

OK. Sent version which allow admin to set Deposit Paid payment status if someone uses offline payment for making deposit payment. Should be OK now. Please test it one more time and update me with the result

Tuan

Thank you, Tuan!

Sorry Tuan, one more question - because for the foreseeable future I can't complete an on-line payment on my dev site.

After a deposit got paid on-line, e.g. with PayPal, what are the resulting statuses for

• Payment Status
• (Registration) Status

in the registrant record?

Same for the remaining (= "due") amount: after paid on-line, what are the resulting statuses then?

Thanks for letting me know.

1. Payment Status: Partial Payment

2. Registration Status: Paid

3. After paid deposit payment, the due amount should be 0.

If you don't have PayPal account, you can test it using Authorize.net test mode:

API Logi: 2Sht9m67PD

Transaction Key: 35J2rq5d6LtJ2Yg6
(enter above information into plugin parameters)

Then make payment using test credit card 4111111111111111

Thanks Tuan,

The Authorize.net credentials are very helpful.

However, now I figure that, with only deposit paid on-line, the registration is treated almost the same as a fully paid one:

1. Status goes to "Paid".
2. Worst, ticket PDF gets mailed to registrant and is downloadable in his registration history.

That second point (ticket mailed) is a strict no-no for obvious reasons.How to stop that from happening, so it's emailed only once the registration is fully paid?

In the backend the only difference in between deposit and fully paid is the payment status: first "partial", then "full". I hope that'l do for the client...

In the users' registration history the ticket column can eventually be hidden with s "better" PHP condition... I guess it'll also cost my time, eh?

BTW, if both PayPal and Authorise are published, I'm getting an error when clicking "Make payment" in registration history. Should be reproducible for you, too? Not a lasting issue here as there'll be only one on-line payment method here... but still saying.

Tuan, and @jkosick in case he's reading, with the many hours - no, days! - spent on figuring these things out, discussing them and eventually adding workarounds etc, I would have happily rather paid $200 for this extension with all working as advertised and expected, indeed.
Not to mention the language (even URL!) which keeps referring to "deposit" when it's really about remainder payments.

I would have happily rather paid $200 for this extension with all working as advertised and expected, indeed

I don't think I even advertise that the extension support payment processing fee for payment plugins. And there are many other features which support by the extension even not being advertising, too.

It is easy to build something only for yourself and have it works as expected. But for an extension which is built for many different use-cases, it is hard to make it perfect. I have to balance between the perfect thing and how many customers actual need it. As I mentioned before, the way payment processing fee is calculated for deposit payment, only pointed out by two customers so far. I know it is not perfect, but since most of customers don't need it, I spend my time to work on other more useful features instead

Tuan Pham Ngoc wrote: 3. After paid deposit payment, the due amount should be 0.

Tuan, just for information, due amount doesn't go to 0 after completion payment has been made.