Skip to main content

Compatability with legacy payments

Payments V2 includes a compatability layer with the legacy payments system which transfers any pending transactions across when generating account statements.

Transferring these pending transactions allows you to continue to use the legacy gala entry tools until you are ready to migrate to Competitions V2.

How payments will be transferred​

When you enable Payments V2:

  • On your statement generation day, the system will copy any transactions from the legacy system for that user in that month.
  • Copied transactions will be prefixed with [LG].
  • All payments in the legacy system will be marked as successful as soon as they're transferred over. From this point you can track payment status in the new system.
  • You can no longer see whether the user has an active direct debit instruction when charging or refunding gala entries. Transactions will be transferred to the new system on statement generation day regardless of the user's Direct Debit status.

Supported product areas​

Transactions from the following areas will be transferred to Payments V2:

  • Gala entries (Direct Debit payments and refunds)
  • Fees for bookable sessions

Transactions for all other product areas will always use Payments V2. These include:

  • Squad fees
  • Extra fees
  • Membership fees paid on account
note

Any pending transactions created before you migrate to Payments V2 will be transferred over on your first Payments V2 statement generation day.

This includes transactions added through Invoice Payments, which is replaced by manual payment entries in Payments V2.

Restrictions with legacy compatability​

While legacy compatability is available, you should keep your statement generation day as the first day of each month.

You should consider moving to the new competition entry tools at the first available opportunity.

Billing during the V2 rollout​

Payments V2 continues to work with the legacy payments system during the rollout. Switching to Competitions V2 does not prevent pending charges or refunds from the old system from being transferred to your members' accounts.

You do not need to run a separate calculation or re-enter these transactions. They will be included when account statements are generated. Once a transaction has transferred, use Payments V2 to track the amount owed and its payment status.

If an expected statement or legacy transaction is missing, contact support before adding a replacement charge, so we can check whether it is still waiting to transfer.