When a user wants to add a new Merchant ID in SedonaOffice, this is a potentially complex task. The basic steps to add the Merchant ID are detailed below, but some pitfalls can arise. The largest of these is that payment methods are tokenized in our database. We do not store the payment information, and tokens are stored in Forte’s database as part of the Merchant ID. If they were to change their branch to the new Merchant ID, any payment methods that are tokenized on the original MID will stop working. Depending on the number of tokens, they can either go through and remove the payment methods and re-tokenize them via manual entry, or a data project can be undertaken to migrate the tokens onto the new MID.
To perform a token migration the customer should first reach out to Forte and request that Forte move the tokens to the new MID. After Forte has made the change the customer can add the new MID to SedonaOffice following the steps below. Finally, SedonaOffice support can migrate the tokens from the old MID to the new MID. All three of those steps must be completed for the migrated tokens to function.
Steps to add a new MID
- Go to Sedona Office EFT Setup.
- Select NEW.
- Enter the information into the corresponding field for the new MID, its Secure Key, API ID, and Organization ID. This information is available in the DEX portal.
- Apply the changes and you’ll have added a new MID to SedonaOffice.
Potential issue
When you add the new MID, it may not be PCI compliant by default. If not, you will receive the following message when logging into Sedona Office. This can be corrected with the PCI Compliance tool, however, the effects of running the tool on a database in motion after the upgrade from 5 to 6 are not well documented. If you receive the message, escalate the case to Data so the X in the AR_ACH_Direct table can be updated to C for compliant after it is verified they have no un-tokenized payment methods.
