> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coverbase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# The marketing rule library

> The rulebooks Coverbase ships for sponsor-bank marketing review, what each rule checks and cites, how pattern checks and AI checks differ, how to fork a rulebook and what a version means, and how to test a rule against sample text.

For AI agents: a documentation index is available at [https://docs.coverbase.com/llms.txt](https://docs.coverbase.com/llms.txt). This page is also available in markdown by appending .md to the URL.

> [!NOTE]
>
> This guide is part of the [User Guides](https://docs.coverbase.com/user-guides/overview.md) collection. It covers the **Rulebook** tab under **Marketing**. For submitting, reviewing and sweeping, see the [Marketing compliance guide](https://docs.coverbase.com/user-guides/marketing-compliance.md). For the rules a partner sees before submitting, see [The partner portal, for partners](https://docs.coverbase.com/user-guides/marketing-partner-portal.md#the-rules-before-you-submit).

> [!NOTE]
>
> Marketing compliance is an optional module. If you do not see **Marketing** in the left navigation, ask your Coverbase account team to turn it on.

A rule is one check an asset must pass: a required disclosure, a forbidden claim, a trigger term that needs its companions, a brand rule, or a general UDAAP rule. Rules ship in rulebooks, one per regulation or standard. A program applies the rulebooks you pick for it, and each rule runs only on the product types and channels it is scoped to. Every flag records the rule and the rulebook version that raised it, which is what the exam packet's sign-off lists.

The mistake people make most often is trying to edit a library rule. Library rulebooks are read-only. To change a rule, fork the rulebook, then edit your copy and assign the copy to your programs. See [Forking and versions](#forking-and-versions).

## The Rulebook tab

Open **Marketing**, then **Rulebook**. Rulebooks are grouped, each with its rule count and the product types it applies to. A library rulebook reads **Library · vN**; your fork reads **Yours · vN**. The views **All** and **Enabled** switch between every rule and the rules switched on. The search box matches rule names and citations.

Each rule row shows **Rule**, **Citation**, **Checked By** (**Pattern**, **AI** or **Pattern + AI**), **Severity** and **On/Off**. Click a row to open the rule.

## What ships

Eight rulebooks. Severity is the rule's default; a flag carries it.

### FDIC Part 328 Subpart B

How a non-bank may describe deposit insurance, and the bank it must name when it does. Applies to every product type.

| Rule | What it checks | Citation | Severity | Checked by |
| - | - | - | - | - |
| Bank named wherever deposit insurance is mentioned | Every mention of the FDIC or deposit insurance names your bank within 60 words, so a consumer reading only that view knows which bank holds the deposits | 12 CFR 328.102 | High | Pattern + AI |
| Pass-through insurance language is accurate | Insurance is described as coverage of deposits held at your bank through the partner, never as coverage of the partner | 12 CFR 328.102, 12 CFR 330.5 | High | AI |
| "Not a bank" statement present and placed | The asset says the partner is not a bank and that banking services are provided by your bank, on the page or screen itself | 12 CFR 328.102(b), FTC Act section 5 | High | Pattern + AI |
| No "bank" in the partner's name, URL or product name | No product name, brand, URL or headline presents the partner as a bank | 12 CFR 328.102(b)(1) | High | AI |
| Non-deposit products carry the three-part disclaimer | An investment, crypto or rewards-in-stock product offered beside a deposit product says it is not FDIC insured, not a deposit, and may lose value | 12 CFR 328.102(b) | High | AI |
| No safety absolutes | No claim that funds are 100% safe, risk-free, guaranteed or protected against all risks | FTC Act section 5, Dodd-Frank section 1031, DFPI v. Yotta (2026) | High | Pattern + AI |
| Insurance limits stated correctly | A stated amount is \$250,000 per depositor, per insured bank, per ownership category, and a higher amount is explained by a sweep program | 12 CFR 330 | Medium | AI |
| Stablecoins never described as insured or government-backed | A stablecoin or crypto balance is not presented as insured or as safe as a deposit (crypto programs) | GENIUS Act section 4 (2025) | High | Pattern + AI |

### Reg DD deposit advertising

What an advertisement for a deposit account must say when it states a rate, a bonus or that the account is free. Applies to deposit programs.

| Rule | What it checks | Citation | Severity | Checked by |
| - | - | - | - | - |
| A stated rate is labeled APY | A rate of return is stated as an annual percentage yield, not as bare interest | 12 CFR 1030.8(b) | High | Pattern + AI |
| APY companions present: as-of date, variable-rate statement, minimum balance | Where an APY appears, the same view gives the as-of date, says the rate is variable if it is, and states the minimum balance. Runs only on text that states an APY | 12 CFR 1030.8(c) | High | Pattern + AI |
| No "free" or "no fees" where a fee can apply | The account is not called free or no-fee when a maintenance or activity fee can apply, judged against the program's approved claims | 12 CFR 1030.8(a) | High | Pattern + AI |
| Bonus and promotional terms adjacent to the offer | A bonus or promotional rate states eligibility, dates, the minimum deposit and how long it must stay, and when it is paid, in the same view | 12 CFR 1030.8(d) | Medium | AI |

### Reg Z credit advertising

Trigger terms, required disclosures and approval claims for credit cards, loans and buy-now-pay-later.

| Rule | What it checks | Citation | Severity | Checked by |
| - | - | - | - | - |
| Open-end trigger terms are accompanied by the required disclosures | A stated periodic rate, APR or fee amount on a credit card is accompanied by the open-end disclosures in the same view | 12 CFR 1026.16 | High | AI |
| Closed-end trigger terms are accompanied by the required disclosures | A down payment, payment amount, number of payments, repayment period or finance charge on a loan or installment plan is accompanied by the closed-end disclosures | 12 CFR 1026.24 | High | AI |
| "No interest" and "0% APR" statements trigger disclosures too | A no-interest or 0% statement says how long the promotion lasts and what applies after it | 12 CFR 1026.16(b), 1026.24(d) | High | Pattern + AI |
| "Subject to credit approval" wherever the card or loan is offered | The phrase appears on website, app store, email, paid ad, print, in-app and affiliate assets | Program requirement; 12 CFR 1026.16 | Medium | Pattern |
| No "instant approval" or "guaranteed approval" | No claim that approval is instant, guaranteed, or without a credit check | FTC Act section 5, 12 CFR 1002.4(b) | High | Pattern |
| Prescreened offers carry the FCRA opt-out notice | A prescreened or pre-approved offer in email or print carries the short notice and the opt-out number (credit card and loan programs) | 15 U.S.C. 1681m(d), 12 CFR 1022.54 | High | AI |

### Reg E prepaid and payments

Fee disclosure timing, account naming and speed claims for prepaid cards and payment products.

| Rule | What it checks | Citation | Severity | Checked by |
| - | - | - | - | - |
| Prepaid short-form fee disclosure shown before enrollment | The short-form fee disclosure appears before the consumer is asked for personal information, on website, app store and in-app assets | 12 CFR 1005.18(b) | High | AI |
| Prepaid cards never called a bank account, checking account or savings account | A prepaid card or stored-value balance is not described as a bank, checking or savings account | FTC Act section 5, 12 CFR 328.102 | High | Pattern + AI |
| Funds-availability and transfer-speed claims match the product | An "instant", "immediately" or "same day" claim matches the timing in the program's approved claims (payments, earned wage access, prepaid, deposit and debit card programs) | FTC Act section 5, Regulation CC | Medium | AI |

### Visa brand standards

The issuing statement and mark treatment Visa requires of a co-branded card. Applies to debit card, credit card and prepaid programs whose network is Visa.

| Rule | What it checks | Citation | Severity | Checked by |
| - | - | - | - | - |
| Issuing statement present and exact for this bank and Visa | Wherever the card is shown or named, the exact issuing statement for your bank and Visa appears | Visa Product Brand Standards (September 2025); program agreement | High | Pattern + AI |
| Visa mark at least as prominent as the partner's and the bank's marks | On card art and visual assets, the Visa mark is at least as prominent as the other marks. Needs the screenshot | Visa Product Brand Standards (September 2025) | Medium | AI |
| Full product name on first prominent mention with the registration mark | The first prominent mention uses the full product name with the registration mark | Visa Product Brand Standards (September 2025) | Low | AI |

### Mastercard brand standards

The issuing statement and card-face requirements Mastercard sets for a co-branded card. Applies to debit card, credit card and prepaid programs whose network is Mastercard.

| Rule | What it checks | Citation | Severity | Checked by |
| - | - | - | - | - |
| Issuing statement present and exact for this bank and Mastercard | Wherever the card is shown or named, the issuing statement for your bank and Mastercard appears | Mastercard Brand Standards; program agreement | High | Pattern + AI |
| "Debit" on the card face when the Mastercard logo appears | Debit card art shown with the Mastercard logo carries the word "Debit". Needs the screenshot | Mastercard Brand Standards | Medium | AI |

### Endorsements, email and SMS

FTC endorsement disclosures, CAN-SPAM and TCPA elements. Applies to every product type.

| Rule | What it checks | Citation | Severity | Checked by |
| - | - | - | - | - |
| Paid or incentivized endorsements disclose the relationship next to the claim | A creator post, testimonial or referral asset on social, video or affiliate channels discloses payment, free product or commission close to the claim | 16 CFR 255.5 (2023) | High | AI |
| Testimonials are from bona fide users and carry the typical-results qualifier | A quoted result is presented as that person's experience, with what a typical consumer should expect | 16 CFR 255.2, 16 CFR 465 (2024) | Medium | AI |
| Email carries the sender's physical address and a working unsubscribe | A marketing email carries a postal address and an unsubscribe mechanism | 16 CFR 316 (CAN-SPAM) | Medium | Pattern |
| SMS carries opt-out instructions and message-rate language | A marketing text says how to stop and that message and data rates may apply | 47 CFR 64.1200 (TCPA), CTIA Messaging Principles | Medium | Pattern |

### UDAAP general

Unfair, deceptive or abusive claims that any channel can carry. Applies to every product type.

| Rule | What it checks | Citation | Severity | Checked by |
| - | - | - | - | - |
| No absolute claims without substantiation | Superlatives and absolutes about rates, fees, speed, security or ranking are substantiated in the same view | Dodd-Frank section 1031, FTC Act section 5 | Medium | Pattern + AI |
| No implied government, regulator or celebrity affiliation | No seal, regulator name or public figure implies an endorsement or affiliation that does not exist | FTC Act section 5, 12 CFR 328.102 | High | AI |
| Comparison claims name the comparison basis and date | A comparison with other providers or the national average names what was compared, the source and the date | FTC Act section 5 | Low | AI |
| Claims match the program's approved claims list | Every factual claim matches the program's **Approved Claims**; a new, contradicting or differently-stated claim is flagged | Program agreement | Medium | AI |

## Pattern checks and AI checks

Each rule is checked one of three ways, shown under **Checked By**.

| Mode | How it runs | When it flags |
| - | - | - |
| **Pattern** | A deterministic phrase check, run in the request when a submission or capture lands, so the review opens with these flags already on it | The text fails the pattern. No model is involved. |
| **AI** | An instruction run against the text, and the screenshot where the rule needs it, within minutes of the submission | The model finds a break and quotes the passage, with reasoning, a suggested fix and a confidence |
| **Pattern + AI** | Both | Either |

A pattern is one of three kinds:

* **A required phrase must appear**: one of the listed phrases has to be in the text.
* **A forbidden phrase must not appear**: none of the listed phrases may be in the text.
* **A trigger phrase needs its companion nearby**: wherever a trigger phrase appears, a companion phrase has to appear within a set number of words. The rule drawer reads **within N words of** the companions.

Some patterns run only when the text mentions a scope phrase, shown as **only when the text mentions** in the drawer. The APY companions rule, for example, stays quiet on a page that states no rate.

Phrases and instructions never carry a bank's wording. A rule names `{bank_name}`, `{partner_name}`, `{program_name}` or `{network_name}`, and the program's **Approved Language** fills them in when the rule runs. That is why the same library rule checks each program for its own issuing statement.

A pattern flag carries **High confidence**. An AI flag carries the model's confidence, and **Low confidence, quote not located** when the quote the model returned is not in the text; the flag is kept so the reviewer sees the claim, and nothing is highlighted.

## Forking and versions

Library rulebooks carry no organization and are the same in every workspace. They are read-only: opening a library rule shows **Library rules are read-only. Fork the rulebook to edit a copy.**

To change a rule:

1. Open the rulebook and click **Fork for editing**. Coverbase copies every rule into a rulebook of your own, keeps a record of which library rulebook it came from, and opens the copy. The copy reads **Yours · v1**. If the rulebook was already forked, the button opens your existing copy.
2. Assign the fork to your programs with **Edit program**, under **Rulebooks**. A program that still lists the library rulebook keeps running the library's rules.
3. Edit rules in the copy. Each rule's drawer has **What the rule checks** (the AI instruction), **Deterministic check** (the pattern, which runs first), **Severity**, **Applies to Products**, **Channels**, **Remediation text the partner sees** and **Sample language** the partner can lift as-is. Click **Save as vN**.

Every save bumps the fork's version. A flag records the version that raised it as **Rule vN**, so a flag raised under v3 reads as v3 after you save v4. The exam packet's **Rulebooks in force** part lists each rule as it read during the period, with the dates it changed.

**On/Off** on a rule switches it off for every program that uses the rulebook. The drawer says how many programs a rule is on for. A rule in a library rulebook can be switched off without forking.

## Testing a rule

Open a rule and scroll to **Test Against Text**. Paste marketing copy, pick under **Program whose approved language to use** the program whose bank text and approved claims should fill the rule's placeholders (or **No program**), and click **Run check**.

![The rule drawer for A stated rate is labeled APY, showing its citation, Pattern + AI under Checked By, High severity, the What the rule checks instruction, a Deterministic check reading a trigger phrase needs its companion within 15 words of APY or annual percentage yield, Applies to Products reading Deposit, Remediation text the partner sees, Sample language, and a Test Against Text section with pasted copy, a program picker, the Run check button, and a result reading Pattern check ran and AI ran with one hit quoting the phrase 4.5% interest at high confidence.](https://mintcdn.com/coverbase/ASfsL9ARZRU6mOkd/images/user-guides/marketing-compliance-rule.png?fit=max\&auto=format\&n=ASfsL9ARZRU6mOkd\&q=85\&s=a4734b8bf4eb517890c2c10273045b95)

A rule's drawer with the test run: the pattern ran, the AI ran, and one hit quotes the passage.

The result says **Pattern check ran** or **Pattern check skipped** (the rule has no pattern, or its scope phrase is absent), **AI ran** or **AI skipped**, and either **No hits** or each hit with its quote and confidence. A test changes nothing: no flag, no review, no version.

## Troubleshooting

| Symptom | Cause | Fix |
| - | - | - |
| **Save rule** is missing and the drawer says library rules are read-only | You opened a rule in a library rulebook | Click **Fork for editing** on the rulebook and edit the copy. |
| You edited the fork but reviews still cite the old wording | The program still lists the library rulebook, not your fork | Open the program, **Edit program**, and pick the fork under **Rulebooks**. |
| A rule never fires on a program | The rule is scoped to a product type or channel the program does not have, or it is switched off | Read **Applies to Products** and **Channels** in the drawer, and the **On/Off** column. |
| The issuing statement rule flags every asset | The program's **Card Issuing Statement** is empty, or the **Card Network** is wrong | Fill the statement under **Approved Language** and set the network. |
| A test reads **Pattern check skipped** | The rule has no pattern, or the pasted text lacks the rule's scope phrase | Expected. Read whether **AI ran**. |
| A flag reads **Rule v2** after you saved v3 | A flag keeps the version that raised it | Expected. Re-run the pre-review on the review to check the asset against v3. |

## Related

> [card] [Marketing compliance guide](https://docs.coverbase.com/user-guides/marketing-compliance.md)
>
> Programs, reviews, the screenshot view, sweeps, notifications and the exam packet.

> [card] [The partner portal, for partners](https://docs.coverbase.com/user-guides/marketing-partner-portal.md)
>
> The rules and sample language a partner sees before submitting, and the quick check.

> [card] [Detector library](https://docs.coverbase.com/products/detector-library.md)
>
> Radar's detector library, which the rulebook library is modeled on.

> [card] [Permissions and roles](https://docs.coverbase.com/user-guides/permissions-and-roles.md)
>
> Who can fork and edit a rulebook.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.