Test currency conversion disclosure before confirming

The flow under test

Four numbers have to be visible before confirmation, and each one is a separate disclosure obligation rather than a nice detail.

• Mid-market rate - 1 USD = 83.42 INR, the reference rate the margin is measured against.
• The applied rate - 1 USD = 80.5003 INR, which is what the sender is actually getting.
• The spread - 3.5%, stated as a percentage rather than left to be inferred from the two rates.
• The received amount - 8050.03 rupees, the only figure the recipient cares about.

Asserting the mid-market rate alongside the applied rate is what makes the spread verifiable rather than merely displayed. A page can state a 3.5% spread beside two rates that imply something else entirely.

The test file

The step that matters most asserts all five values while explicitly not having pressed send, because disclosure before commitment is the entire requirement.

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

# PayPaal 10.5: Currency conversion

Catalog objective: send an international payment and verify the conversion rate shown.
Key assertion: the rate and converted amount are displayed before confirming.

## Choose an international recipient
Choose "Mira Shah" and verify the option detail reads "mira.shah@example.in · IN · receives INR".

## Enter the amount
Type "100" into "You send (USD)" and verify a currency conversion panel appears with a badge reading "Currency conversion applies".

## Verify the rate and the converted amount before confirming
Verify the panel shows "Mid-market rate" of "1 USD = 83.42 INR", "PayPaal rate" of "1 USD = 80.5003 INR", "Currency spread" of "3.5%", "Fee" of "$0.80" and "Mira Shah receives" of "₹8050.03".

## Confirm and verify the receipt carries the same numbers
Click "Review and send", verify "They receive" reads "₹8050.03", then click "Send now" and verify the receipt shows "Exchange rate" of "1 USD = 80.5003 INR" and "They receive" of "₹8050.03".

The final step then checks the receipt repeats the applied rate and the received amount, which is what prevents a rate quoted at review from being replaced by a different one at execution.

Step by step coverage

Each step covers a distinct part of the obligation, and the ordering is the substance of it.

The order is the point. A test that checks the same figures only on the receipt would pass a page that discloses nothing until after the money has gone.

Running it

kane-cli testmd run tests/paypal/currency-conversion_test.md

What you have is a compliance-shaped test: the assertions are the disclosure requirements, in the order the regulation expects them.

Rate data changes constantly, which makes the surrounding structure more durable than the figures. Building a suite from written requirements covers deriving assertions from a document, and calling an API inside a flow covers checking the quoted rate against the service that issued it.