Checkout Champ

Need help with something?

Talk to data expert

Checkout Champ

The Checkout Champ connector allows you to ingest orders, purchases, transactions, and customer data from your Checkout Champ (Konnektive) data into your data warehouse via Daton. Data can be replicated into BigQuery, Snowflake, or Redshift for order analytics, subscription/recurring-billing reporting, chargeback and refund analysis, and customer lifetime-value modeling.

Note: Checkout Champ and Konnektive are the same underlying platform with two brand skins. If your account was set up as Konnektive, the API host and behavior described here still apply — only the branding differs.

About Checkout Champ

Checkout Champ is a shopping-cart, CRM, and order-management system (OMS) built for direct-to-consumer and subscription commerce. Its API exposes four query endpoints — Orders, Purchases, Transactions, and Customers — that this connector reads incrementally so your warehouse always reflects recently created and updated records.

Prerequisites

Before configuring the connector, ensure you have:

  • An active Checkout Champ (Konnektive) CRM account with API access enabled.
  • An API user created in the CRM (Admin → Users), with an API Access Level that grants access to the Orders, Purchases, Transactions, and Customers query endpoints.
  • The loginId and password of that API user.
  • The outbound IP address - 35.238.200.205 added to the API user's IP Whitelist. The whitelist is enforced per API user, not account-wide — if the calling IP is not listed, every request is rejected.
  • The time zone configured on your Checkout Champ account (needed so incremental date ranges align with how the CRM stores dateUpdated).

How to Obtain Your Credentials

Create the API user.

  • Log in to your Checkout Champ CRM as an Admin.
  • Navigate to Admin → Users.
  • Click the green + button to add a new user and set the API Access Level.
  • Grant access to the Order Query, Purchase Query, Transactions Query, and Customer Query endpoints.
  • Record the loginId and password — these are the credentials Daton will use.

Whitelist the connector's IP.

  • Still under Admin → Users, open the API user you just created.
  • Add the outbound IP address - 35.238.200.205 to that user's IP Whitelist and save.
  • Confirm the account time zone under your CRM settings so it can be entered during setup.

Steps to Integrate

Follow these steps to configure the connector in Daton:

  1. In Daton, navigate to Add Integration → Checkout Champ.
  2. Begin Setup – Enter Source Configuration Details.
  3. Integration Name: provide a descriptive name.
  4. Description (optional): e.g., "Checkout Champ – orders, purchases, transactions & customers".
  5. Replication Frequency: select how often to pull data (e.g., 6h, 12h, 24h). Daily is sufficient for most reporting; use a shorter interval for near-real-time needs.
  6. Replication Start Date: choose when to begin the historical extraction. This is the earliest updated data the connector will backfill from.
  7. Lookback Window: the connector applies a 1 hour on the incremental syncs to account for potential source delays. This ensures late-arriving/updated records are re-captured on the next run.
  8. Advanced Configuration Options: set Loading Mode (Append/Upsert) and Nested Object behavior. Note that nested arrays are delivered as stringified JSON columns (see Nested Fields below).
  9. Authenticate the Source:
    • Login ID: enter the API user's Login ID.
    • Password: enter the API user's Password.
    • Account Time Zone: enter your Checkout Champ account time zone, so date windows match the CRM.
  10. Click Authenticate – Daton validates the credentials against the Checkout Champ API.
  11. Select Tables for Replication: choose the tables to replicate — Orders, Purchases, Transactions, Customers (or a subset).
  12. Configure Schema / Columns: optionally select which columns to load, or choose Select All to load every column across all selected tables.
  13. Click Submit and connect your warehouse. Daton begins the initial historical load and then schedules incremental loads at the selected frequency.

Supported Tables

Table Name Purpose  
Orders Individual sales orders with line items, billing/shipping, card metadata, discounts, tax, upsell and click/browser attribution  
Purchases Product-level purchases including subscription/recurring-billing state (billing cycles, intervals, trials, next fulfillment)  
Transactions Individual payment transactions including amounts, merchant/gateway, billing cycle number, and chargeback status  
Customers Customer master records including blacklist flag, lifetime value, and purchase history  

All four tables are queried with dateRangeType=dateUpdated, so both newly created and subsequently modified records are re-synced.

Table Schemas

The connector auto-detects columns from the API response, so the schema evolves as Checkout Champ adds fields. The tables below list the key, explicitly typed fields for each entity.

Orders

Column Type Mode
orderId STRING NULLABLE
actualOrderId NUMERIC NULLABLE
externalOrderId STRING NULLABLE
clientOrderId STRING NULLABLE
dateCreated DATETIME NULLABLE
dateUpdated DATETIME NULLABLE
orderType STRING NULLABLE
orderStatus STRING NULLABLE
totalAmount STRING NULLABLE
refundRemaining STRING NULLABLE
cvvResponse STRING NULLABLE
campaignName STRING NULLABLE
campaignCategoryName STRING NULLABLE
customerId NUMERIC NULLABLE
name STRING NULLABLE
emailAddress STRING NULLABLE
phoneNumber STRING NULLABLE
firstName STRING NULLABLE
lastName STRING NULLABLE
address1 STRING NULLABLE
city STRING NULLABLE
state STRING NULLABLE
country STRING NULLABLE
postalCode STRING NULLABLE
shipFirstName STRING NULLABLE
shipLastName STRING NULLABLE
shipAddress1 STRING NULLABLE
shipCity STRING NULLABLE
shipState STRING NULLABLE
shipCountry STRING NULLABLE
shipPostalCode STRING NULLABLE
paySource STRING NULLABLE
cardType STRING NULLABLE
cardLast4 STRING NULLABLE
cardExpiryDate DATETIME NULLABLE
cardIsPrepaid NUMERIC NULLABLE
cardIsDebit NUMERIC NULLABLE
price STRING NULLABLE
baseShipping STRING NULLABLE
discountPrice STRING NULLABLE
salesTax STRING NULLABLE
shipUpcharge STRING NULLABLE
isDeclineSave NUMERIC NULLABLE
ipAddress STRING NULLABLE
salesUrl STRING NULLABLE
currencySymbol STRING NULLABLE
currencyCode STRING NULLABLE
campaignId NUMERIC NULLABLE
totalDiscount STRING NULLABLE
productCost STRING NULLABLE
shippingCost STRING NULLABLE
custom1 STRING NULLABLE
custom2 STRING NULLABLE
funnelReferenceId STRING NULLABLE
hasUpsell BOOLEAN NULLABLE
items RECORD REPEATED
customFields RECORD REPEATED
browserDetails RECORD REPEATED
fulfillments RECORD REPEATED
shipCarrier STRING NULLABLE
shipMethod STRING NULLABLE
address2 STRING NULLABLE
shipAddress2 STRING NULLABLE
avsResponse STRING NULLABLE
UTMCampaign STRING NULLABLE
agentUserId NUMERIC NULLABLE
agentName STRING NULLABLE

Enrichment flags sent on the request: showExternal=1, includeClicks=1, includeCustomFields=1, includeBrowserDetails=1 — so click attribution, custom fields, and browser details are included in the response.

Purchases

Column Type Mode
firstName STRING NULLABLE
lastName STRING NULLABLE
emailAddress STRING NULLABLE
address1 STRING NULLABLE
city STRING NULLABLE
state STRING NULLABLE
country STRING NULLABLE
postalCode STRING NULLABLE
shipFirstName STRING NULLABLE
shipLastName STRING NULLABLE
shipAddress1 STRING NULLABLE
shipCity STRING NULLABLE
shipState STRING NULLABLE
shipCountry STRING NULLABLE
shipPostalCode STRING NULLABLE
currencySymbol STRING NULLABLE
purchaseId STRING NULLABLE
campaignId NUMERIC NULLABLE
productId NUMERIC NULLABLE
actualProductId NUMERIC NULLABLE
customerId NUMERIC NULLABLE
displayName STRING NULLABLE
status STRING NULLABLE
cancelReason STRING NULLABLE
price STRING NULLABLE
shippingPrice STRING NULLABLE
billingCycleType STRING NULLABLE
billingIntervalDays NUMERIC NULLABLE
billingCycleNumber NUMERIC NULLABLE
finalBillingCycle NUMERIC NULLABLE
fulfillmentCycleNumber NUMERIC NULLABLE
recycleBillingNumber NUMERIC NULLABLE
productQty NUMERIC NULLABLE
dateUpdated DATETIME NULLABLE
dateCreated DATETIME NULLABLE
productName STRING NULLABLE
variantDetailId NUMERIC NULLABLE
variantName STRING NULLABLE
totalBilled STRING NULLABLE
totalRefunded STRING NULLABLE
orderId STRING NULLABLE
cancellationScheduled NUMERIC NULLABLE
pauseScheduled NUMERIC NULLABLE
currencyCode STRING NULLABLE
fixedBillingDay NUMERIC NULLABLE
merchantId STRING NULLABLE
merchant STRING NULLABLE
descriptor STRING NULLABLE
funnelReferenceId STRING NULLABLE
transactions RECORD REPEATED
actualPurchaseId NUMERIC NULLABLE
fulfillments RECORD REPEATED
nextFulfillmentDetails RECORD REPEATED
nextBillDate DATE NULLABLE
phoneNumber STRING NULLABLE
cardBin STRING NULLABLE
cardLast4 STRING NULLABLE
cardExpiryDate DATE NULLABLE

Request flag includeNextFulfillmentDetails is set, so the next scheduled fulfillment is included for subscription purchases.

Transactions

Column Type Mode
transactionId NUMERIC NULLABLE
parentTxnId NUMERIC NULLABLE
merchant STRING NULLABLE
merchantDescriptor STRING NULLABLE
merchantId NUMERIC NULLABLE
dateCreated DATETIME NULLABLE
dateUpdated DATETIME NULLABLE
txnType STRING NULLABLE
responseType STRING NULLABLE
responseText STRING NULLABLE
3DTxnResult STRING NULLABLE
merchantTxnId STRING NULLABLE
clientTxnId STRING NULLABLE
totalAmount STRING NULLABLE
surcharge STRING NULLABLE
orderId STRING NULLABLE
clientOrderId STRING NULLABLE
billingCycleNumber NUMERIC NULLABLE
campaignId STRING NULLABLE
campaignName STRING NULLABLE
campaignCategoryName STRING NULLABLE
firstName STRING NULLABLE
lastName STRING NULLABLE
orderType STRING NULLABLE
customerId NUMERIC NULLABLE
emailAddress STRING NULLABLE
phoneNumber STRING NULLABLE
address1 STRING NULLABLE
city STRING NULLABLE
state STRING NULLABLE
country STRING NULLABLE
postalCode STRING NULLABLE
ipAddress STRING NULLABLE
paySource STRING NULLABLE
cardBin STRING NULLABLE
cardLast4 STRING NULLABLE
cardType STRING NULLABLE
cardIsPrepaid NUMERIC NULLABLE
cardIsDebit NUMERIC NULLABLE
custom1 STRING NULLABLE
custom2 STRING NULLABLE
isChargedback NUMERIC NULLABLE
refundReason STRING NULLABLE
refundItemId NUMERIC NULLABLE
refundProductName STRING NULLABLE
currencyCode STRING NULLABLE
currencySymbol STRING NULLABLE
paySourceId STRING NULLABLE
funnelReferenceId STRING NULLABLE
items RECORD REPEATED
actualOrderId NUMERIC NULLABLE
midNumber STRING NULLABLE
authCode STRING NULLABLE
avsResponse STRING NULLABLE
cvvResponse STRING NULLABLE
address2 STRING NULLABLE
recycleNumber NUMERIC NULLABLE
cascadeId NUMERIC NULLABLE
UTMCampaign STRING NULLABLE
orderAgentName STRING NULLABLE

Customers

Column Type Mode
customerId NUMERIC NULLABLE
firstName STRING NULLABLE
lastName STRING NULLABLE
address1 STRING NULLABLE
city STRING NULLABLE
state STRING NULLABLE
country STRING NULLABLE
postalCode STRING NULLABLE
phoneNumber STRING NULLABLE
emailAddress STRING NULLABLE
billShipSame NUMERIC NULLABLE
shipFirstName STRING NULLABLE
shipLastName STRING NULLABLE
shipAddress1 STRING NULLABLE
shipCity STRING NULLABLE
shipState STRING NULLABLE
shipPostalCode STRING NULLABLE
shipCountry STRING NULLABLE
paySourceId NUMERIC NULLABLE
paySource STRING NULLABLE
cardType STRING NULLABLE
cardLast4 STRING NULLABLE
cardExpiryDate DATE NULLABLE
dateCreated DATETIME NULLABLE
dateUpdated DATETIME NULLABLE
mostRecentActivity DATETIME NULLABLE
eCommerceLogin STRING NULLABLE
campaignName STRING NULLABLE
campaignType STRING NULLABLE
custom1 STRING NULLABLE
custom2 STRING NULLABLE
contactOptIn NUMERIC NULLABLE
emailOptIn NUMERIC NULLABLE
isTaxExempt NUMERIC NULLABLE
ipAddress STRING NULLABLE
paySources RECORD REPEATED
customFields RECORD REPEATED
isBlacklisted NUMERIC NULLABLE
lifetimeValue STRING NULLABLE
creditAmount STRING NULLABLE
address2 STRING NULLABLE
shipAddress2 STRING NULLABLE
doNotSellName NUMERIC NULLABLE
notes RECORD REPEATED

Request flags includeBlacklist=1, includeLifetimeValue=1, and excludeHistory=0 are set, so blacklist status, lifetime value, and purchase history are returned.

Replication & Sync Behavior

  • Incremental sync field: dateUpdated (mapped to updated_at). Each table syncs the window of records updated since the last successful run.
  • Partitioning: the sync window is broken into 1-day partitions, processed newest-first, so recent data lands early in a backfill.
  • Settling lag: a 5-minute lag is applied to the upper bound of each window so in-flight writes settle before extraction.
  • Pagination: page-based, 200 records per page. The connector reads totalResults and resultsPerPage from the response to know when to stop.
  • Date format: the API expects MM/DD/YYYY dates and HH:MM:SS times; the connector derives these from the sync window automatically.
  • Empty ranges: when a date range has no matching records, Checkout Champ returns an error message ("no … matching those parameters could be found") instead of an empty list. The connector treats this as a clean zero-result window and moves on to the next range — this is not an error.
payment checkout

Related Articles

Table of Contents

About Checkout Champ Prerequisites How to Obtain Your Credentials Steps to Integrate Supported Tables Table Schemas Orders Purchases Transactions Customers Replication & Sync Behavior