Test sending money to a contact with a note

The flow under test

A transfer has one irreversible moment and three chances to get the details in front of the sender before it.

• Selection - the recipient chosen is the one the sender intended, out of a contact list where names repeat.
• Review - the amount and the recipient are restated together before the send button is available.
• Confirmation - a banner naming both, immediately after.
• The record - an activity row with the transaction id, the date, the note and a negative amount.

The activity assertion is the strongest one in the file, because it checks a negative sign. A transfer recorded as a credit rather than a debit is an accounting error that no amount assertion alone would catch.

The test file

The note field is included deliberately. Free text that travels through a transfer and back out into a feed is where encoding problems surface, and the assertion quotes it exactly.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/paypal-clone-app/send?reset=true
max_steps: 45
tags: [paypal, payments, p2p]
---

# PayPaal 10.3: Send money

Catalog objective: send money to a contact with a note.
Key assertion: the recipient and amount are confirmed in the activity.

## Choose the recipient and amount
Choose "Tom Alvarez", type "25" into "You send (USD)", and type "Dinner on Friday" into "Add a note".

## Review the send
Click "Review and send" and verify the review panel shows "Sending" of "$25.00" and "To" of "Tom Alvarez".

## Send it
Click "Send now" and verify a green banner titled "Money sent" says you sent "$25.00" to "Tom Alvarez".

## Verify it in the activity feed
Verify the receipt shows "Transaction" of "TX-9921" and "Note" of "Dinner on Friday", then go to https://my-testing-repo-main.vercel.app/paypal-clone-app/activity and verify the feed has a "Tom Alvarez" row reading "TX-9921 · 2026-09-15 · "Dinner on Friday"" with an amount of "−$25.00".

The final step leaves the send flow entirely and navigates to the activity page, which is the only place the transfer can be verified independently of the screen that created it.

Step by step coverage

The four steps map onto the four moments where a sender can still catch a mistake, plus the record that outlives all of them.

Verifying on a different page than the one that performed the action is what separates a confirmation message from a persisted transfer.

Running it

kane-cli testmd run tests/paypal/send-money_test.md

What you get is coverage on an irreversible flow, checked on the screen that performs it and again on the record that survives it.

Free text passing through a system is also where injection and encoding issues appear. How assertions are resolved against the page covers exact string matching, and evidence based QA covers retaining proof for a financial flow.