Setting up Slate Payments in a new database is easy and straightforward.

In general, you can set up, begin testing, and move to production use without any Technolutions assistance. However, if you're currently accepting payments through another external provider, and want to migrate (fully or partially) to Slate Payments, please open a support ticket in the "Migrating to Slate Payments" category.

The migration process is usually quick, however, we will evaluate what work is required and discuss a suitable testing/go-live strategy in the support ticket as we review your particular existing setup and gather more context about the desired timing and required sequence of events.

Each external payment integration setup is different (even for a given payment processor). Deactivating your old custom payment integration (for testing purposes or production cut-over), or isolating its scope to certain payment accounts, may involve renaming files or deleting configuration sections from existing files.

Why Migrate to Slate Payments?

• With Slate Payments, payment widgets can collect payments directly on Slate forms and events

• Cost and transaction fees are highly competitive

• The Stripe payment element will automatically display all the acceptable/available/supported payment methods

• Refunds, payouts, and built-in reconciliation reporting can be managed in Slate

• Testing is self-service

• Tap-to-pay can be used for in-person payments

• More details

Preparing to Migrate

Before you submit your ticket to the Support Desk:

1. Review the Slate Payments - Setup article.

2. Determine which prompts are associated with the payment provider or providers you’re migrating from.

   • List the prompts in your ticket.

   • Not all prompts need to be migrated at once.

   • Slate Payments will coexist with any existing external payment processor integrations.

3. Set up the Deposit Accounts as explained in step 2 of Slate Payments - Setup.

4. Refresh your test environment.

5. Complete step 3 in your test environment, OR for a more convenient approach that may not work in every scenario:

   1. Create a separate test payment account prompt value (for example, "Test Fee")

   2. Link that prompt value to use Slate Payments (as per step 3).

   3. Leave the other provider live using the other existing prompt values, and then switch later when you're ready to go live with Slate Payments.