July 30, 2026
Release 2026.15.2 moves Go Method's payment processing to Vanco's new AbundantConnect platform and continues Reserved Seating stabilization with corrections to seat transfers, seat assignments for minors, administrator permissions, background check fees, and pre-approval reviews. Reserved seats are also easier to find on the My Events page.
For more detailed help, see Reserved Seats.
Updated Payment Processing
This change only affects organizations that use Vanco Payments as one of their payment merchant.
Go Method now processes payments through Vanco's AbundantConnect platform, replacing the older service Vanco is retiring. Everything about how you and your registrants pay stays the same — this update changes only the connection Go Method uses behind the scenes.
- Payments keep working without interruption, so registrations, deposits, and fees continue to process as usual.
- Saved payment methods, past transactions, and scheduled payments carry over. Nobody needs to re-enter card or bank information.
- Registrants see the same checkout experience, so there's nothing new to explain to the people signing up for your trips.
- Go Method stays current with Vanco's platform, which is where future payment improvements will be delivered.
Reserved Seats are Easier to Find
Reserved seat owners with unassigned seats now have better visibility. On the My Events page, the Your Reserved Seats row moves to the top, and the entire event section and row are clickable — not just the link. This makes it easier to see and assign any remaining seats.
Reserved Seating and Pre-approval Corrections
| Issue | What was corrected |
|---|---|
| Event administrators could manage reserved seats without full trip permissions | Event administrators who didn't have access to all trip information could still grant, transfer, and release reserved seats. These actions are now limited to administrators with access to all trip information. |
| Seat owners couldn't transfer a seat to someone who already had a login | When a seat owner transferred a reserved seat to a person who already had a login, the transfer failed with the message “The email address already exists under the name…” Go Method now matches that person to their existing profile and completes the transfer. |
| Records corrected for seat owners who received seats by transfer | Seat owners who received reserved seats through a transfer before this release could have incomplete records. Those records have been corrected so their seats and trip access appear correctly. |
| Assigning a seat to a minor required an email address | When a seat owner assigned a reserved seat to a minor, they couldn't continue without entering an email address for the minor, and clicking into the email field cleared the guardian information already entered. Assigning a seat to a minor now works the same way as registering a minor: no email address is required, and guardian information stays in place. |
| Seat owners received an error when paying a background check fee | When a seat owner assigned a seat to a group member whose member type required a paid background check, the payment screen returned an error and the assignment couldn't be finished. Seat owners can now pay the fee and complete the assignment. |
| Background check fee charged twice | When a seat owner paid the background check fee while assigning a seat, the person who received that seat was asked to pay the same fee again when resolving their background check requirement. The seat owner's payment now satisfies the requirement, so the fee is charged only once. |
| Background check fee charged for people who already had a valid check | When a seat owner assigned seats, the payment screen asked them to pay a background check fee for group members who already had a valid background check on file. Go Method now recognizes an existing background check, so the fee isn't charged again. |
| Administrators could bypass pre-approval without the right role | Administrators who weren't responsible for reviewing pre-approval saw the Actions button for applicants still held in a pre-approval step, which allowed them to bypass it. Only administrators assigned to review that step can act on those applicants. |
| Bypass pre-approval alert appeared for applicants who had finished pre-approval | When administrators accepted an applicant who had completed every pre-approval step, an alert warned that accepting would bypass pre-approval. That alert now appears only when pre-approval steps are actually incomplete. |
| Pre-approval steps, notifications, and decisions aligned to roles | Each pre-approval step now stops applicants at the right point, notifies the administrators assigned to that step, and limits approve and reject decisions to those administrators. |
| Event codes weren't searchable in the new view | Searching by event code returned results in the classic view but not in the new view. Event codes are now searchable in both views. |