Test an international transfer quote and its fee breakdown

The checks that matter

The quote is a chain of four calculations, and each one feeds the next.

Asserting the total fees alongside its two components is what catches a total that does not equal its parts. A breakdown that displays correctly and sums incorrectly is the kind of error nobody notices until a customer does the arithmetic.

The flow as a test file

The variable fee is asserted with its percentage in the label, so a rate change that alters the percentage without altering the amount is visible in the failure.

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

# Wize 15.1: Transfer quote

Catalog objective: create a USD to INR transfer quote and verify the fee breakdown.
Key assertion: the rate, fee and arrival estimate are all displayed.

## Set the quote up
Replace "You send" with "1000", leave "From currency" on "USD" and "To currency" on "INR".

## Verify the fee breakdown
Verify the quote shows "Fixed fee" of "$0.71", "Variable fee (0.43%)" of "$4.30" and "Total fees" of "$5.01".

## Verify the rate and the converted amount
Verify "Amount we'll convert" reads "$994.99", "Guaranteed rate" reads "1 USD = 83.42 INR" and "Recipient gets" reads "₹83,002.07".

## Verify the arrival estimate and create the transfer
Verify an arrival estimate of "by Wednesday, 17 September" is shown, then click the create button and verify a green banner titled "Transfer created" names transfer "TR-80115".

The arrival estimate is asserted before the transfer is created, because a delivery promise made after the money has gone is not a promise the customer used to decide.

Step by step coverage

Two steps of assertion around the quote, then the action that depends on them.

The word guaranteed in the rate label is doing work. A rate presented as guaranteed and then applied differently at execution is a different failure from a rate that simply moved, and asserting the label keeps that distinction in the test.

Adding it to a suite

kane-cli testmd run tests/wise/transfer-quote_test.md

Live rates move, so against a real environment assert the structure and the relationships rather than pinning every figure.

For checking the quoted rate against the service that issued it, the same run can call the API directly. Calling an API inside a flow covers that, and running in CI covers catching drift on a schedule.