Quickbooky

Accounting News

Payments

QuickBooks Payments link to QuickBooks Online resets apps and ends old refunds

Users connecting an existing QuickBooks Payments account to QuickBooks Online lose app settings and can't refund older charges, so prepare first.

COMMUNITY ISSUESQUICKBOOKY

QuickBooks Online users who bring a payments account over from another Intuit product are finding that the link is not a quiet settings change. Connecting resets the mobile app, removes its transaction history, and closes the refund window on older transactions. The accepted guidance leads with preparation rather than repair, and the software itself warns you before the final click.

Who needs the manual connection?

Sign up for QuickBooks Payments inside QuickBooks Online and the software links the two automatically. Manual connection exists for everyone else. If your payments account came from a different QuickBooks product, most often the GoPayment mobile app, you connect it by hand from account settings. That handwork is where the surprises live, and several of them are permanent.

No. This is the constraint to understand before anything else. Transactions made before the connection cannot be refunded afterward, so any open amounts need attention while the accounts are still separate. The accepted guidance says it plainly: refund open transactions first, then connect. Once linked, that door stays shut. If you owe a customer a credit on an older charge, issue it before you begin.

Do recurring payments survive the switch?

They do not. You are instructed to remove them yourself: sign in to your Merchant Services account on the web and turn off any recurring payment schedules before starting. Nothing migrates on its own. The replacement arrives after the link, when you rebuild those schedules as memorized sales receipts inside QuickBooks Online. Anyone billing customers on a monthly cycle should treat that rebuild as part of the move, not as cleanup afterward.

What happens to the GoPayment app?

The app resets. Its transaction history and your receipt customizations disappear from the app itself, though both remain viewable in your Merchant Services account on the web. Nothing is destroyed, but the app comes back empty.

Items and descriptions move in one direction. QuickBooks replaces the copies held in the app with the ones from QuickBooks Online, to keep the two sides consistent. If you customized item names on the phone, expect the online list to win.

Customer records can lose ground too. Where GoPayment holds multiple customers, the connection may remove some of their IDs. QuickBooks Online also carries its own limits on users, which is worth checking before you link accounts on a busy team.

The steps that complete the connection

An administrator handles this from account settings, and the sequence is short. Work through it in order.

  1. Sign in to QuickBooks Online as an admin.
  2. Open Settings, marked with a gear icon, and select Account and settings.
  3. Select the Payments tab, then choose the option to connect your QuickBooks Payments account.
  4. Pick the payments account you intend to link.
  5. Select the accounts where customer payments should deposit. You can change these later if needed.
  6. Select Connect. A warning window appears, titled “Changes you might not expect”. Confirm it by selecting Yes, I understand.
  7. Sign out, then sign back in to finish.

One more swap after you sign back in

User identities change hands as well. When the connection completes, your QuickBooks Payments user IDs replace your QuickBooks Online user IDs. Teams that kept separate logins for each service lose that separation in a single step. Decide in advance who needs access, because the payments credentials take over. Anyone managing staff accounts should map this out before the link goes live, not after logins start behaving differently.

The short version

The connection itself takes minutes. Preparation is the real work. Refund what is open, turn off what recurs, note your receipt customizations, and accept that the mobile app returns empty. Users who skip those steps meet the one-way parts afterward, which is the wrong direction to learn them from. The final dialog asks whether you understand the changes. Read it, then answer.

← Back to Community Issues