Introduction

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 payment integration (for testing purposes or production cutover), or isolating its scope to certain payment accounts, may involve renaming files or deleting configuration sections from existing files.

Before moving forward

You may start and proceed to set up your Slate Payments Deposit Account as explained in Step-2 of the Setup article before you are opening the support ticket.

Planning for testing

For testing you can start thinking about the following approaches:

1. Set up the Deposit Accounts as explained in Step-2 of the Setup article, refresh your test environment, and then complete Step-3 in your test environment,
   or else

2. Create a separate test payment account prompt value (e.g. "Test Fee"), link that prompt value to use Slate Payments (as per Step-3) while leaving the other provider live using the other/existing prompt values, and then switch later when you're ready to go live with Slate Payments. This approach is more convenient and ‘preferred’ in many ways, but may not work in all scenarios.