On this page
A provider reviewing a proposed reward program needs a consistent account of the merchant, the campaign, and the responsibilities behind it. Contradictory documents can create avoidable questions: one file describes domestic consumers, another suggests international recipients, and a presentation uses a volume estimate different from the application.
An evidence pack should resolve those contradictions before submission. This is a merchant-specific dossier for a defined provider review, not a general discovery checklist or instructions for collecting recipient identity documents.
Collect the current evidence requested by the provider
Begin with the provider’s current requested evidence and the scope of the review. Requirements can differ by arrangement, so do not assume that a pack prepared for one provider is complete or appropriate for another. Ask the responsible reviewer to identify the applicable request and secure submission route.
Assign an owner to each document. Business identity evidence, campaign description, activity projections, operating responsibilities, and customer-facing materials may come from different teams. The dossier index should make clear who can confirm or update each item.
In a fictional Shopify merchant, the campaign owner proposes a domestic purchase reward pilot. Finance supplies activity assumptions, operations describes case handling, and the technical lead explains the approved integration responsibilities. The pack should present those inputs as one coherent proposed program rather than unrelated attachments.
RebateCardX’s reviewed access process provides a route for discussing the information and scope needed for a proposed integration. A technical access request is not automatically the complete merchant or program approval process, so confirm which review the evidence pack supports.
Align campaign claims with the business model
Use a dossier index with version, ownership, access, and an outstanding question. The example below is fictional and does not claim that every listed document is required by every provider.
| Evidence item | Responsible owner | Version or date control | Access restriction | Outstanding reviewer question |
|---|---|---|---|---|
| Merchant business description | Authorized business representative | Current approved description | Review team through the approved route | Does the description match the actual products and customer base? |
| Proposed customer offer | Campaign owner | Offer draft linked to the review | Relevant commercial and program reviewers | Are eligibility and reward timing described consistently? |
| Activity projection | Finance or commercial owner | Assumptions dated and labeled as estimates | Reviewers who need the commercial forecast | Which figures represent the pilot rather than future expansion? |
| Operating responsibility map | Operations lead | Current named roles and boundaries | Authorized review participants | Who owns unresolved customer and provider cases? |
| Integration responsibility description | Technical lead | Current proposed architecture scope | Approved technical reviewers | Which party controls each relevant data and customer surface? |
| Customer-facing sample | Content owner | Approved draft with product assumptions identified | Relevant review team | Does any wording imply an unapproved capability? |
Align the numbers across documents. If the application describes a pilot of a certain scale while a deck presents a larger future ambition, label the distinction explicitly. A future scenario should not look like current committed activity, and a conservative pilot estimate should not hide a materially broader intended use.
State assumptions rather than manufacturing precision. Forecasts should identify their basis and uncertainty. Do not add invented historical results, provider pricing, or customer commitments merely because an application field seems to expect a number.
A difficult case is a marketing deck that describes the reward as instant while the operating process includes review. The dossier owner should resolve the promise before submission. Sending both documents and hoping the reviewer selects the intended interpretation creates a substantive ambiguity about the proposed program.
Track questions and changes through the approval decision
Maintain a reviewer-question log linked to the evidence index. Each question should identify the requested clarification, owner, response version, and whether the answer changes another document. A response about recipient scope may require updating the offer draft, projection, and integration description together.
Do not scatter approvals across private messages without a central reference. The dossier record should show which version was reviewed and what conditions were accepted. An approval of an earlier draft does not automatically cover a later material change.
RebateCardX’s regulatory disclosures distinguish the platform’s role from banking and issuing functions. The merchant’s pack should describe proposed counterparties and responsibilities accurately, without implying that a technology platform performs a role assigned elsewhere in the actual arrangement.
Use the approved secure submission channel for sensitive business evidence. The working index can describe what exists and who owns it without copying every document into a broadly shared campaign folder. Limit access to people who need the material for the defined review.
Record unresolved questions honestly. “Pending provider confirmation” is more useful than a confident answer supplied by someone who lacks authority to make it. The purpose of the dossier is to help the responsible reviewer decide, not to make every field appear complete at any cost.
When the proposed program changes during review, issue a clear version update. Identify the changed scope, affected evidence, and reason. Do not replace files silently while a reviewer is assessing an older set; that can produce an approval whose actual subject is unclear.
For the fictional merchant, the final submission contains a consistent domestic pilot description, aligned activity assumptions, an accurate offer draft, and named operating responsibilities. Questions about unconfirmed capabilities remain visible with owners instead of being disguised as established facts.
The completed evidence pack should let the provider understand the same proposed program from every document. Its value is consistency and traceability: the reviewer can locate the current evidence, ask a bounded question, and connect the final approval or remaining condition to the version the merchant actually intends to operate.
Discuss the merchant information required to assess your proposed Rebate Card X program. Discuss program fit.
Source references
This guide is general information, not financial, legal, tax or regulatory advice. Eligibility, card availability, permitted use and responsibilities depend on the applicable offer and card terms.
