Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. 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.

  2. Inform us through the Checkout Champ Concierge ticket that the export was completed.

  3. We will then decrypt and tokenize the file and provide it decrypt the file, tokenize the card numbers, and send the file back to you through the Concierge ticket.

  4. Map the export files fields to the Import You then build our Legacy Data Import file using the decrypted file. The legacy Legacy Data import PDF will provide the field definitions and required columns.

    1. merchantId: Located here: Listed under the ID column, this is the merchant account future rebills will be processed on.

    2. campaignId: Located here: This the campaign your imported customers will be assigned to.

    3. 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.

    4. isActiveRecurring: needs to be set to 1 if the product is an Active Subscription.

    5. nextBillDate: is required for active subscriptions and must be in this format

      date (YYYY-MM-DD)

    6. phoneNumber should be formatted like this 5551112222. Do not include parentheses or dashes

    7. You will find the other required fields in the Legacy Import PDF or in the Import File CSV which contains all the required columns.

  5. Send us the completed file through the Concierge ticket

  6. We will import a sample of the completed file

  7. Verify the sample. You will want to review the customers, verify the rebills and refunds work. If there are any issues let us know.

  8. If the samples pass the test we will import the rest of the data.


  1. What is the merchantTxnId?

    1. This is the processors processor's Transaction Id

  2. What is the externalToken?

    1. A token identifying the customer payment source at the 3rd party gateway. This is commonly sometimes 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 asterisksprocess existing subscription billings without a full card number.

3. What if I don’t have a required column?