September 9, 2026
Release 2026.19.1 returns a released seat's payment to trip funding, completes ACH payments that had settled but still showed as pending, restores the reconnect option for Docusign integrations that used the authentication method Docusign retired, and improves page load times.
Payments, Integrations, and Performance
| Issue | What was corrected |
|---|---|
| Releasing a reserved seat left its deposit out of trip funding | When an administrator released a reserved seat that had been paid for, the deposit went missing instead of returning to the trip's Funding tab. Releasing a seat now returns its payment to the trip's funding, and deposits left out of funding by this issue have been returned to the trips they belong to. |
| ACH payments stayed pending after they had settled | An ACH payment that had already settled kept showing as "Pending Complete" in a participant's funding, so it never counted toward the amount they had raised. Go Method now completes these payments as they settle, and payments left pending by this issue are being corrected. |
| There was no way to reconnect a Docusign integration | Docusign retired the authentication method that older integrations used. If your saved Docusign credentials used that method, the Turn on Docusign Integration button never appeared, leaving no way to reconnect. Your digital signature settings now show your saved user name along with a notice that Docusign has retired the method, and a Reconnect Docusign Integration button that reconnects your account using OAuth 2.0. |
| Integrations that connect through the API stopped working | Starting September 2, an application that connects to Go Method through its API could not sign in. API connections have been restored. |
| Pages could take a long time to load | Pages throughout Go Method could take longer than usual to load. Page loads are now improved. |