Requirements:
Checkout Champ Konnektive Attestation of Compliance (This will be located in the Zip file)
Checkout Champ Konnektive PGP Key (They will require this key in order to encrypt and send files to us)
Server Credentials (This is the server that your processor will export files to)
host: 23.253.42.24
username: storm_media
password: 8xWPZ4Wq
Import File (The file you will provide to us for import into the CRM. The base file will be provided to you in the Zip)
...
Make the request for an export with your processor. Provide them the server credentials, PGP Key and AOC. Once their requirements for an export have been met they will send the data to the server credentials you provided to them.
Inform us through the Checkout Champ Concierge ticket that the export was completed. We will then decrypt and tokenize the file and provide it to you through the ticket.
Map the export files fields to the Import file. The legacy Data import PDF will provide the field definitions and required columns.
merchantId: Located here: https://crm.konnektive.com/merchants/mids/ Listed under the ID column, this is the merchant future rebills will be processed on.
campaignId: Located here:https://crm.konnektive.com/crm/campaigns/ This the campaign your imported customers will be assigned to.
productId: also known as campaignProductId. Located under the ID column in the Campaign Products Section of the campaign. (Note) This is different from the base productId. Verify that the products you assign are configured correctly ie: One Time or Recurring.
isActiveRecurring: needs to be set to 1 if the product is an Active Subscription.
nextBillDate: is required for active subscriptions and must be in this format
date (YYYY-MM-DD)
phoneNumber should be formatted like this 5551112222. Do not include parentheses or dashes
You will the other required fields in the Legacy Import PDF or in the Import File CSV which contains all the required columns.
Send us the completed file through the Concierge ticket
We will import a sample of the completed file
Verify the sample. You will want to review the customers, verify the rebills and refunds work. If there are any issues let us know.
If the samples pass the test we will import the rest of the data.
...
What is the merchantTxnId?
This is the processors Transaction Id
(Stripe) What is the externalToken?
Typically in the Stripe file there will be a column with values that look like this (pm_1K9aRtKXsXQBYaESfe5508if) Put those values under externalToken. This is required for rebills and without them your subscriptions will fail.
(Stripe) What is authCode?
Typically in the Stripe file there will be a column with values that look like this (cus_Kmqdn9Nr2wO1MH) Put those values under authCode. This is required for rebills and without them your subscriptions will fail.
Can I put any date in the import file?
No, the dateCreated requires this specific format datetime (YYYY-MMDD HH:MM:SS)
The nextBillDate requires this specific format date (YYYYMM-DD) and is required for Active subscriptions
What if a required field is missing?
In some cases you can use dummy data. For example phoneNumber can replaced with 1111111111 (No dashes or parentheses)
You will need to check with your processor if they will accept the rebill without it. If they will then you should use A token identifying the customer payment source at the 3rd party gateway. This is commonly used to run existing rebills when the full card numbers are unavailable and when gateway-supported. -note: if provided, cardNumber column may be masked with either x's or asterisks.
3. What if I don’t have a required column?
a. In some cases you can substitute with dummy data. EG. phoneNumber can be supplied with 1111111111. You will have to check with the processor you will be transacting with (NMI, Stripe, Auth.net) whether they will allow the subscriptions without the field or will allow dummy data.