Migrating Tokens to ServiceMinder Pay
If you're switching your payment processing to ServiceMinder Pay, you may need to transfer existing card tokens from your current provider. The process varies depending on your current processor.
Before requesting a token transfer, please review your contract structure with your current payment provider to ensure you’re authorized to request token transfers for multiple organizations or locations at once.
TSYS
If your current provider is TSYS, serviceminder can assist with initiating the token migration process.
- Download Existing Tokens
- Visit this Card Tokens Report link to download and extract current tokens using the Contact ID.
- This ensures each token is correctly matched to the appropriate contact in your system.
- Submit a Support Ticket
- Email: support@serviceminder.zendesk.com
- Include the CSV file with token data from the report.
- ServiceMinder Support Coordinates With Processors
- Our team will contact TSYS to request the token extraction.
- Once received, our team will submit the file for re-tokenization.
Heartland
- Complete the attached Liability Waiver Form
- On the form, the Terminal ID Number field can be left blank.
- Send your completed form to wade.speelman@e-hps.com and let him know you are requesting token transfer from Heartland to Forward.
For All Other Payment Providers
If you're migrating from Authorize.net, QuickBooks Payments, or another provider, the merchant (you) must initiate the token transfer.
What You Need to Provide
Your processor should give you a file that matches our standard token import format:
Contact ID, New Profile ID, New Payment ID
Download your tokens from ServiceMinder to map them correctly to contacts.
If your file includes only old-to-new token mappings, use Excel's VLOOKUP to rebuild the file using your current token report to match tokens to contacts.
Token Migration Format Guide
| Column Name | Description |
|---|---|
| ContactId | Our contact Id -- available from the token download you used to initiate the token transfer. If not provided, the next two columns must be present. |
| OldProfileId | The existing Profile Id. Both Profile and Payment fields are required if contact Id is not present. If Contact Id is included, the existing Profile/Payment Ids are ignored. |
| OldPaymentId | The existing Payment Id |
| NewProfileId | The new contents for the Profile Id field (required) |
| NewPaymentId | The new contents for the Payment Id field (required) |
| ACH | 0 for card, 1 for ACH (so we know what type of token it is). If missing, we assume card. |
| Last4 | The last 4 digits of the account number, if missing, card numbers may not display depending on the gateway, but charges should still be able to run successfully. |
| Expiration | The expiration date in MM/YYYY or MM/DD/YYYY format |
| NameOnCard | The card holder's name |
Lossless Token Transfer
Lossless token transfer allows you to switch from your existing payment gateway to serviceminder|pay without losing saved payment methods or requiring customers to re-enter their card details.
This dual-path setup allows for a smooth, interruption-free transition, giving your business time to gradually shift everything to the new platform while maintaining payment continuity for existing customers.
How It Works
- When you enable serviceminder|pay, any existing payment tokens in your account are tagged as part of the old gateway
- These tokens continue to process transactions using your previous payment gateway, even after serviceminder|pay is active.
- New payment information captured after enabling serviceminder|pay will be processed through the new gateway (Forward).
- Both systems work in parallel—serviceminder|pay for new transactions, your old provider for legacy tokens.
What You Need to Do
- Keep your old gateway active to ensure existing tokens can still process payments.
- Don't delete or deactivate tokens in the serviceminder|pay system; they'll continue working as long as the old gateway account remains open.
- Over time, as customers update their card info or save new payment methods, these will automatically route through ServiceMinder Pay.
Important Caveats
- Refunds for transactions processed on the old gateway must still be handled through that provider.
- Reporting for old transactions will not appear in the serviceminder|pay dashboard, but will remain visible in your previous gateway’s reporting tools.
