Only successful event bookings show up under Records
Hi @saguaros,
Well, that's hard to say. As you can see, DT Register seems to not pass any info to Mollie in these cases. So as you can see, we see only the amount that the customer was willing to pay. We don't see who the customer was or what event he wanted to book.
So, these bookings are all not confirmed; the customer got as far as the checkout and for some reason got stuck (or decided not to book after all).
???
- Edited
Hi!
Sorry for the delay, but I have checked with mollie. This is what they told me:
I have checked the transactions and see that the payments that we have made have successfully invoked the webhook. Below I will mention the transaction ID of a number of random moments with the time at which we called the webhook.
- tr_wHacdhD8uN - Wed 15 Jan 2020 20:46:13
- tr_rp4u2Ag3Hs - Tue 21 Jan 2020 22:09:10
- tr_DTkkdBh8ya - Thu 23 Jan 2020 21:23:09
- tr_AgrbBhwSKz - Sat 25 Jan 2020 11:46:07
- tr_pbRhwPzg2c - Wed 29 Jan 2020 02:56:09
- tr_fn9h9mVjye - Wed 29 Jan 2020 14:54:11
- tr_6TmCNUKHuM - Thu 30 Jan 2020 15:45:07
- tr_P6k9WUUnmg - Tue 4 Feb 2020 11:51:15
- tr_wHDvNQvKBW - Tue 4 Feb 2020 13:01:12
The transactions mentioned are all expired payments. We call your webhook at the time of expiration. This has been successful every time (we receive 'OK 200' from your server).
We therefore advise you to view the log files of the above moments. That way you can find out what happens on the server. The idea is that the database will be updated when we call on the webhook.
So please, check why DT Register does not update the database as this should be possible according to Mollie.
Please strongly consider to make expired
payments visible in administrator. We do not want our client to access database tables for obvious reasons.
Thanks for the suggestion. But I think it is even easier for DTH Development to include the filter option 'Expired' and show the expired records.