Design your Rewards Program UX

Below are the minimum requirements (information and display) for a standard program.

Kard’s API-first technology means that you can design your user experience in the way that best suits the needs of your rewards program. The Kard network serves both national and local card linked offers to our issuer partners, and local offers have their own additional requirements. Be sure to refer to the section on requirements for local offers if you plan to have them enabled on your platform.

Note: For the majority of Kard partners, opting into rewards is part of the general enrollment process. If that is not the case, an additional screen is required to opt-in cardholders to the rewards program.

Available Offers

Your “Rewards” screen is a chance to invite your cardholders to see the benefits associated with your card and program. This will show all CLOs available to the cardholders and is typically filtered on a number of criteria, such as online versus in-store offers. 

In combination with emails marketing specific brands to your cardholders, this screen increases the likelihood that a cardholder will seek out the brands that reward for their loyalty.

Offer Details

Kard works with brands to display accurate terms and offer qualifications. A screen to show the offer details allows a cardholder to know exactly what to expect from an offer and mitigates confusion in the user experience. The full set of required offer details is:

  • Merchant name
  • Merchant logo
  • Cashback amount or percent
  • Terms and conditions
  • Channel type (online or in-store)

Redemption Notification

Sending a notification to your cardholders upon a successful offer redemption is crucial to the consumer linking the benefit to having used your card. Providing a notification to the end user within 24 hours after the purchase is required, but we recommend serving it in near real-time, to provide the cardholder instant feedback.

Impression Reports

Building your offer impression reporting infrastructure is one of the most powerful ways to measure and enhance the success of your rewards program. Kard’s existing API does not include an impression reporting module. The most common solution for impression reporting is to programmatically insert a tracking pixel into the logo images of each offer you run. Impression reporting is only a Kard requirement for local offers, but best practice is to integrate this type of reporting into all of your offer infrastructure.

Requirements to use local offers

Here's the checklist of items our team  needs  in order to get you set up with Local offers. For creative items that require approval, you have the option to  share screenshots, a video recording highlighting below or provide a test user account for Kard to access.  Typical runway, including approval, is about 30 days after the below steps are completed. Make sure you are following these requirements for National. The list below contains additional requirements needed for local offers.

  1. Quarterly Acknowledgement

For programs already live with CLO/National offers, our partner requires the end users to acknowledge local offers quarterly. While we do not require end users to opt-in/activate individual offers, we do need some type of opt-in related to local offers. This can be in the form of an email or in-app notification. The following language needs to be included:

  • Local dining and restaurants (language can be flexible as long as it recognizes local dining/restaurant offers)

Action Needed: Screenshot, Video Recording, or test user account for Kard to access of acknowledgement


  1. Onboarding Walkthrough for Local Offers

Users should be given a walkthrough so long as the onboarding of the card/program walks cardholders through:

  • How to discover and use rewards at “Local dining and restaurants” merchants
  • Calls out “Local dining  and restaurants” offers specifically and ensures offers are easy to find (language can be flexible as long as it recognizes local dining/restaurant offers)

Action Needed: Screenshots, Video Recording, or test user account for Kard to access of onboarding/education process 


  1. Transaction Data Requirements: 

In addition to the standard set of required items for National offers, we ask that you pass along the MID and merchant address.

  • MID (Merchant ID:) Kard cannot enable Local offers without the MID
  • Merchant Address: good to have in cases where the MID does not match what is on file for the merchant

Action Needed: Test Transactions in Sandbox and confirm with Kard team 

  1. Full UX/UI

We would love to see how your team will display the trail of the local offers in the app. (Ex: Geolocation, Categories, etc.)

  • “Local dining and restaurants” section in the app and/ or website
  • A Local offer (Logo/Image, Description, Reward Amount, Terms & Conditions)
  • 24-hour earned reward notification (standard reward requirement)

Action Needed: Screenshots, Video Recording, or test user account for Kard to access of above mentioned items

  1. Local Survey/ Post Dine Notification

The survey is passed with the earned webhook notification that Kard sends to you. Please note that in the sandbox environment, the URL will not actually populate. The end user is required to be  presented with the survey. 
Best Practices:

  • Option 1: “Local dining and restaurants” survey is shared and sent along with the 24 hour earned reward notification as a link.
  • Option 2: Users can be directed to take the “Local dining and restaurants” survey either in the app or shared via  email

Action Needed: Screenshots, Video Recording, or test user account for Kard to access of above mentioned items

Example: (Email)     Example: (In-app)

  1.  Marketing Requirements

At a minimum, marketing should be sent out at least once a month highlighting at least 5 “Local dining and Restaurants” merchants based on the end user's location. This can be shared with end users through the following channels:

  • Email
  • Push Notifications
  • SMS Text
  • Mobile App Display

Partners can:  

  • Use the merchant logo, description, and banner provided through the API to market the offer
  • Feature/highlight any merchant of your choosing that is part of the program
  • Send out communications targeting certain users to promote offers

However, we prohibit:

  • Using any unapproved items to describe the merchant or offer, including images, logos, or other marketing materials. Please only use what we provide through our API.
  • Tagging merchants in your own social media posts
  • Using any of the following language: "This post was sponsored by...," "we have partnered with...," or "in collaboration with..."

Marketing to your users outside of the environment with information not shared through the API does require merchant approval, which can take up to two business days. Merchants will want to ensure that their name, message, logo, and anything else associated with them are in alignment with their brand guidelines.  

To submit the creative for approval, please email your Account Manager with the creative assets and anticipated date of launch. If you would like to collaborate with one of our merchants directly, reach out to your Account Manager. 

Action Needed: To Launch, a mock up from at least one of the following channels via  Screenshots, Video Recording or test user account for Kard to access of above mentioned items




  1. Impression Reports, Directions HERE

When a merchant runs an offer through Kard's network, there are a few metrics that help them understand the efficacy of their campaign. At a high level, we typically report on the following:

  • Number of redemptions
  • Repeat visits
  • Average order value

However, these metrics can only show whether a cardholder chose to take action on a particular offer and aren't good leading indicators.

In order to provide merchants data on the cardholders who didn't take an action, we use impression reports. These are a measure of the number of times the particular offer was loaded, viewed in the environment, and clicked.

By providing merchants with this information, we are able to help them determine how to make their campaigns more effective. If we notice a high number of impressions for a particular offer without a correspondingly high count of actions taken (using the offer, activating the offer, etc.), it could be because the cardholder didn't find the offer compelling enough to take an action. This helps us make recommendations for instigating action and establishing loyalty for that particular merchant.

When to Submit Impression Reports

Impression files are collected on a weekly basis every Monday before 5 pm EST and should include data from the previous Monday through Sunday (7 calendar days).

After approval of format, files should be submitted as CSVs to

Naming should follow impressions_PartnerName_YYYYMMDD.csv

Format, Sample HERE

Submitted impression reports should be submitted as CSV files and include the following data, where each row represents a single unique impression. (See attached for example)

  • Partner name
  • Date (MM/DD/YYYY)
  • Timestamp (HH:MM AM/PM)
  • Kard merchant ID
  • Channel (where the impression occurred)
  • Event (what triggered the impression)
  • Shared user ID (referring partner ID)

Action Needed: Sample Report for Kard’s approval via your Account Manager, then weekly submission to the email 

Events Tracked in Impression Reports

  • Delivered: E-mail featuring a merchant is delivered to consumer
  • Open: E-mail is opened featuring merchant by the consumer
  • View: Web page (or app page) or web content featuring merchant is viewed by the consumer
  • Click: Consumer clicks on a URL or E-mail featuring merchant content
  • Offer: Consumer activates/or clicks into a specific offer for a merchant (not required) / could also be clicking into the offer to learn more information
  • Search: Consumer performs a search (web page or mobile app) and merchant is listed on the search results