Test adding a merchant offer to a card

The contract this flow keeps

The enrollment has to register in three independent surfaces, and a click that updates one of them is indistinguishable from one that worked.

• The starting state - zero offers added, so the enrollment is demonstrably new.
• The confirmation - a banner naming both the merchant and the card.
• The catalogue row - an added badge replacing the button, so it cannot be added twice.
• The card itself - a count of one and a row carrying the offer terms and the date.

The button being replaced by a badge is worth asserting on its own. A catalogue that still offers an add button after enrollment invites a duplicate, and duplicates in an offers system are an operational cost rather than a cosmetic one.

The objective in plain English

The confirmation names the card as well as the merchant, since a customer with several cards needs to know which one the offer landed on.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/amex-clone-app/offers?reset=true
max_steps: 40
tags: [american-express, banking, offers]
---

# Amrex 25.4: Offers enrollment

Catalog objective: add a merchant offer to the card.
Key assertion: the offer shows as added.

## Verify the starting state
Verify the page subtitle reads "0 added to •••• •••••• 41008" and the "Harbour Grocers" offer shows an "Add to card" button.

## Add the offer
Click "Add to card" on "Harbour Grocers" and verify a green banner reads "Harbour Grocers offer added to Amrex Platinum."

## Verify the offer is marked as added
Verify the "Harbour Grocers" row in the catalogue now carries an "Added to card" badge instead of the button.

## Verify it appears on the card
Verify the "On your card" card shows "Offers added" of 1 with a "Harbour Grocers" row reading "Spend $50 or more, get $10 back · added 2026-09-16".

The final assertion includes the offer terms and the date it was added, which is what makes the enrollment auditable if the cashback later fails to appear.

Assertion by assertion

A baseline, the action, and two independent confirmations.

Three surfaces asserted against one click is the right ratio for an action whose failure only becomes visible to the customer at a checkout weeks later.

Putting it in CI

kane-cli testmd run tests/american-express/offers-enrollment_test.md

Add a second enrollment attempt on the same offer, since the system should refuse rather than silently accept it.

Offer catalogues change far more often than the flow around them. Generating offer variants keeps that cheap, and checking the UI before a pull request covers catching a catalogue change.