Incase entries are added, old job must be deleted, and new job with all entries yet to be paid need to be created. (current waiting to be paid, and new submitted)

On show level new database field to say how many minutes they have to pay
0 = off, 20 minutes, 60 minutes, 120 minutes, 1440 minutes (1 day), 2880 minutes (2 days), 7200 minutes (5 days)

On meeting_entry

entries_to_pay: array of entry ID's

scheduled_check_payment_job: job_id

When job runs, delete submit status on all entries_to_pay (making them unsubmit)
When payments is finished, empty entries_to_pay & delete job

Thom's note, will not be taken in to account as of now. As rider will be able to resubmit their entries after payment succeeded. But will of course be put back in line.

Message from Addington:

Hey hey,

Super random one,

We are facing several issues linked to people being able to submit entries to standard everyday shows, without making payment (it’s not a problem for shows that close a week before the show starts)
I think it’s mostly because they don’t all understand that a submission of entry is not acceptance of those entries.

Is there any possibility of adding function entry.equipe
that would enable something to only allow them to submit entries if they have paid for everything they have selected.

We’ve had a couple of issues, some like this:

They Submit 5 stables
Don’t pay. we chase them for the payment up until the day before.

But If say our stables are capped at 75

They then have blocked 5stables for that time and then they go in and delete what they originally submited,

not paying a penny and leaving 5 stables then empty at close

I appreciate things like this are a big ask but we really need to find a solution going forward 😁

Hi

I have read this thread but I don’t understand if we can force payment with submission of entries. I to am getting quite frustrated with non payers because some don’t pay until the day and I’m trying to chase up payments when I’m trying to ride

We really need the ability to force payment at time of entry in Equipe, but only for selected shows in Australia.

At the moment, we’re seeing the same group of riders repeatedly submitting entries without completing payment. While I understand this has been raised before, the reality in Australia is that some riders are accustomed to entering without paying upfront, which creates a lot of follow-up work—particularly for smaller shows.

What would be ideal is a toggle option (on/off) at show level:

• Some shows (e.g. early entry or larger events) may not require upfront payment
• Others absolutely need to enforce payment immediately at entry

A few key requirements:

• If enabled, payment must be completed at time of entry
• This should also apply when riders make edits to their entries
• However, show secretaries must still be able to edit entries without triggering forced payment, so they can request payment separately if needed

The current setting option you are suggesting — “Payment in entry set as mandatory (shopping basket to be emptied after x minutes)” — doesn’t appear to be working as intended not the shows Ive been managing. Across multiple shows this year, unpaid entries are still sitting in the system and not being cleared unless we manually chse people up which is creating a lot of extra work.

Having a reliable, flexible option here would make a significant difference to workload and cash flow for many organisers.

thanks so much, cheers

wendy

I have scheduled the work for next week to layout the basics. Of course hope to have it finished within a few days. Otherwise I continue in the first week of June.

I have put some work in to this, and hope to bring this to staging tomorrow. To get feedback on.

Setting up on organizer:

After user submit, a flag is set on the MeetingEntry check_pay_status_after This is a timestamp created based on last submission + time set by organizer.
After submission of entries, the above will be sticky to the user interface. When the organizer accepts the entry, this value is cleared Or when the payment is done.

Incase payer doesnt pay, a cron job runs every 5 minutes, and unsubmitted entries that are not accepted(and still not paid). Also sends email to payer that those entries are unsubmitted.

It takes into account that if the rider is on the 'No payment required' required list this should not be removed?

Good one, I have implemented that incase payer is on this list, I don't set the check variabel

What yet needs to be worked out:
-> If person clicks pay, should I extent the period by 5 minutes, incase the remaining periode is less then 5 minutes?
-> Do I need to add time when new entry is added, or leave the set time already? (Current design gives person whole set time frame based on the last submit)

The only draw back of my current design:
-> In case rider submitmits and pays for 5 entries, but then also adds 2 more. And doesn't pay, he risks to lose all his spots. This because I dont track on entry level if its paid.

Picture from suggested mail:

The next items do I need to work out:
-> Incase everything is on waitinglist, I should not trigger this

Spent some more time on this, building on Nick's work. The flow already worked end to end, so most of this was polish and edge cases. Nice groundwork Nick, that made it a lot easier.

What changed:

• Riders who paid keep their spots. If someone pays for 5 entries and later adds 2 more without paying, only the 2 unpaid ones are removed. This was the drawback Nick pointed out above.
• If someone is in the middle of paying when the time runs out, we wait for the payment to finish before removing anything. So no one loses entries while they are paying. That also answers the question about extending the period.
• The timer only starts when there is actually something to pay and paying is possible. So payments need to be on, a Stripe account connected, and the payer not on the "No payment required" list. Putting someone on that list afterwards now also stops the removal, which was Thom's question.
• Entries are never removed after the show has closed for entry, since the rider would have no way to enter again.
• Entries on the waiting list cost nothing, so on their own they will not start the timer. That covers the last open point.
• The warning goes away as soon as it no longer applies. For example when entries are accepted or paid, or when the organizer turns the setting off.
• The shortest time option is now 30 minutes instead of 20, so a started payment always has time to finish.

We tested the whole flow in the browser and everything is covered by tests. The branch is ready for review.

This is deployed to staging now

I have tested myself the following:

Submit & pay = clears message
Submit & not pay = unsubmitted after time
Submit & pay & submit a bit more = only unsubmitted the entries made after the last payment.
Only waitinglist entries = No notification, all good
Adding "No payment required" = Clears message
Remove Pay Within = Clears message

----- Left to test -----
Grace period with payment. I check the code, that looks good