---
title: "Switch payment providers"
description: "Move your clients from one payment processor to another without stopping their autopay, then retire and delete the old provider."
url: "https://support.outpostplatform.com/client-payments/switch-providers/"
product: "depot"
type: "how-to"
status: "draft"
ai_summary: "MSP plan. Cutover: connect the new provider and Make primary; the old one is Draining and keeps charging its saved methods while clients are asked to set up again every few days. A Moving off card lists clients left, with Remind. Retire keeps keys for refunds; Retire anyway stops remaining methods and autopay. Delete wipes keys, ending refunds through Outpost."
availability:
  plans: ["msp"]
  permission: "psa:payments"
  preview: false
source: "https://gitlab.com/outpostplatform/docs/-/edit/main/src/content/docs/client-payments/switch-providers.md"
license: "CC BY 4.0"
---

# Switch payment providers

Saved cards and bank accounts belong to the processor they were saved with,
so they cannot be copied to a new one. A cutover moves your clients over
gradually instead: the old provider keeps charging the methods saved on it
while each client sets up again on the new one. This page takes you from two
providers to one.

## Before you begin

- You need `psa:payments`.
- Connect and test the new provider first. See
  [Connect a payment provider](/client-payments/connect-a-provider/).
- Deleting the old provider at the end is permanent. Payments it took can no
  longer be refunded through Outpost after that.

## Make the new provider primary

1. Select **Client billing** > **Payments**.
2. On the new provider's row, select **Make primary**, then confirm with
   **Make primary**.

The new provider shows **Primary**. The old one shows **Draining**, with the
date it started. From now on:

- New payments, new saved methods, and new autopay authorizations go to the
  new provider, or to a client's own provider if their billing profile names
  one.
- Methods saved on the old provider keep charging there, including autopay.
- Each client with a method on the old provider is emailed a link to set up
  payment again, and reminded every few days until they do. Set the interval
  in **Remind to set up again every**. See
  [Payment settings and emails](/client-payments/payment-settings/).

When a client sets up again, the new authorization replaces the old one and
the old method is removed.

## Follow the cutover

A **Moving off** card appears on **Payments** for each draining provider. It
lists the clients who still pay through it, with their saved methods and
whether their autopay is on. Select **Remind** to email one of them now.

When the last client has moved, the card says **Every client has moved.**
Outpost also raises an alert in your own workspace when a draining provider
has no saved methods left.

## Retire the old provider

Retire the old provider once its last payments have settled.

1. On the old provider's row, select **Retire**, then confirm with **Retire**.
2. If clients still pay through it, Outpost asks again. Select **Retire
   anyway** to go ahead. Their saved methods stop working, their autopay is
   suspended, and each client is emailed to set up payment again.

A retired provider takes no new payments. It keeps its keys, so you can still
refund payments it took, and late updates from the processor are still
recorded.

You cannot retire the primary provider. Make another one primary first.

## Delete the old provider

1. On the retired provider's row, select **Delete**.
2. Confirm with **Delete**.

This wipes its keys. Payments it took can then never be refunded through
Outpost. Refund them in the processor's own dashboard instead.

## Verify

- The old provider shows **Retired**, or is gone after you delete it.
- On each client's **Billing profile**, **Saved methods** lists methods on the
  new provider only.

## Next steps

- [Set up autopay for a client](/client-payments/autopay/)
- [Refund a payment](/client-payments/refunds/)
