Get started with Finfare Conne...

Payment-linked dining offers

26min

Finfare has access to payment-linked dining offers, known as the Dining Program, which can be added to a Publisher's rewards platform upon request. Publishers must meet and maintain adherence to specific requirements and go through an approval process to add the Dining Program. This topic provides an overview of the pre-launch and post-launch requirements.

Contact a Finfare Representative to learn more about adding the Dining Program to a rewards platform.



Configuration and Nuances

The dining program requires additional inputs, and further stipulations than other payment-linked offers.

Configuration

In order for users to qualify for rewards program, Publishers must supply additional information when registering a user that are conventionally optional.

  1. When registering a user, the end-user must supply their primary_zip_code which represents the home address, or the primary dining location of the consumer.
  2. If a Publisher uses their own instance of Plaid, they must fetch account type (credit card vs. other) from Plaid along with all of the required fields.

Nuances

  1. Eligible Account Types
    • Credit Accounts Only: Currently, the dining rewards program is limited to credit accounts. Non-credit accounts (such as checking or savings) are ineligible.
    • UI Recommendations: Consider making this distinction clear within your user interface. For example, you may disable or hide account types other than credit when users are linking an account.
  2. Transaction Eligibility
    • Linked Payment Method: If a user pays at a qualifying restaurant with any method other than the linked credit account, the transaction will not qualify for the reward.
    • Enforcing the Policy: Ensure your messaging and onboarding workflows emphasize that only purchases made with the registered credit account(s) are eligible.
  3. Identifying Dining Program Offers
    • offer_category = 'restaurants': You can determine whether an offer is part of the dining program by checking if this field is set to restaurants.
    • Limited Category: Only dining program offers will use this category, so be sure to reference it when filtering or displaying relevant rewards to end-users.

Pre-launch requirements

Publishers must provide the following checklists prior to gaining approval to launch the Dining Program:

Even if the criteria for implementing the Dining Program is met, there is no guarantee that the dinging program will be made available.



T-30 checklist

This checklist and information must be provided to Finfare a minimum of 30 days before the Publisher's Dining Program launch date.

Marketing for Publisher's rewards platform - This is how dining program offers plan to be shared to users, and all applicable methods:

Web

Email

Mobile

Target launch date - The timing of when the offers will go live, including details on stages of launch if applicable

Program Size or Estimated Size of card base - Anticipated size of audience offers will be available to including all applicable launch stages

Member Count with geographic distribution (concentrations) - For example, member distribution for “Publisher X” is evenly distributed nationwide, but there is a 5X concentration of Members in southern California

Member Zip Code - Must be provided as part of enrollment

Marketing of Dining Program content - Marketing shall consist of one or more of the following activities: promotion on Publisher’s website, email marketing to Publisher End-Users, and/or promotion on Publisher’s mobile application. Post-launch requirements

Commitment (No modification or misuse of content) - Confirm that the Dining Program content will be shared in accordance with agreement

Impression Data (monthly minimum) - Confirm that impression data at the publisher level will be shared with Finfare

Responsibility to provide awards - Confirm that the Publisher will award user for activity with Dining Program offers in conjunction with the agreement

Sending Benefit Confirmations - Publisher must confirm rewards to user

If yes, enter type & frequency of send - Confirm how benefit will be shared with user

Post dine reviews included - Confirm publisher will provide user option to complete review, and if no - provide a reason

Manual Card Enrollment (direct) - Confirm user will directly enroll card when opting into offers

If yes, note source - Confirm source



T-10 checklist

This checklist and information must be provided to Finfare a minumum of 10 days before the Publisher's Dining Program launch date.

UX examples with callouts to offer location - Share UX examples on how Dining Program offers are discovered

Confirm member award value - Confirm what benefit member will receive for Dining Program offers

Dine Review Creative Supplied to Finfare - Share creative elements to create post dine review

Launch date - Confirm official launch date, note phases if applicable

Launch roll-out plan and timeline - Share announcement plans  (program generally and dining offers specifically)

Marketing Audience Size at launch - Inform Finfare of audience size and timing no later than 10 days prior to that marketing. Publisher agrees to share marketing plans (size, timing) no later than 10 days before the marketing commences

Post-launch requirements

After the Dining Program has been added to a rewards platform, Publishers must provide the following:



Impression data

Publishers must track weekly impression data and sent it to Finfare on a monthly basis.

Impressions are gathered at various levels, including the merchant, member, date, time, channel, and digital interaction. This combined information is referred to as "Impression Data.”

File Structure:

  • The data must be delivered to Finfare in a comma-separated values (CSV) format at least once a month.

Digital Interactions to be captured:

  • View
  • Click
  • Search
  • Delivered (for email)
  • Opened (for email)

Data to Collect:

  • Finfare/Publisher's unique identifier(s)
  • Date and time of the impression event
  • Dining Program's merchant identifier
  • Channel
  • Digital interaction
  • Unique Member identifier

Column Header

FINFARE

DATE

TIME

MERCHANT

CHANNEL

EVENT

Member

Column Description

Publisher identifier to identify the source of the data

Date of impression

Time of impression

RN’s Merchant ID number

Channel identifier

Impression event description

Finfare’s unique Member identifier

Data Type

Text

Date

Time

Integer

Text

Text

Text

Data Format

50 characters maximum.

No special characters

MM/DD/YYYY

HH:MM PMAM

Integer, maximum of 

9 digits

email 

web

app

other

delivered

open

view

click

search

150 characters maximum.

No special characters

Data

Examples

FINFARE1

FINFARE1

FINFARE1

FINFARE1

01/01/2020

02/01/2020

03/01/2020

05/31/2020

12:00PM

02:00AM

04:35PM

10:00PM

15512

78911

89112

192312

web

app

email

other

click

open

view

search

A123456

B654321

Z124HHDG

56734551



T+45 post-launch checklist

This checklist and information must be provided to Finfare within 45 days after the Publisher's Dining Program launch date.

Initial Impression Data Report  (monthly cadence) - Confirm first monthly report sent to Finfare and monthly cadence moving forward 

Post Dine Review Live - Confirm users are receiving review

Screenshots with Dining Rewards content - All applicable locations shared (i.e.. Web, app)

Initial Dining Program merchant live report (monthly cadence) - Confirm first monthly report sent to Finfare and monthly cadence moving forward

Initial Enrollment Data (monthly cadence) - Confirm first monthly report sent to Finfare and monthly cadence moving forward

Initial Marketing Opt-Out confirmation (monthly cadence) - Confirm opt-out data being sent to Finfare