Confirm payment

Write a Halden billing notice to the owner of the Larkspur Labs workspace on the Halden API, asking them to confirm a card payment that their bank has put on hold for verification. Cover the facts below.

The $23.60 payment for the May 2026 Halden API invoice for the Larkspur Labs workspace is waiting on a bank confirmation step. The card on file is a Visa ending in 5958. The card issuer requires this check through Visa Secure before the charge goes through; the payment is not taken until the workspace owner completes it.

Confirming the payment at https://halden-email.s3.amazonaws.com/billing/confirm is the one action the email asks for. The headline carries the $23.60 figure and asks for the confirmation; the confirm button comes first, then the explanation of why the confirmation is needed, then the payment details.

Why the confirmation is needed: banks sometimes require an additional step to make sure an online transaction was authorized. Visa Secure sets that standard and protects the cardholder from fraud. Consumer-protection regulation means many online payments now require two-factor authentication. The bank decides when authentication is required, and cardholders often see this step when they start paying for a service or when the cost changes. This background is explained at https://halden-email.s3.amazonaws.com/help/payment-confirmation

Payment details, to be laid out as a line-item table:

• Billing period: May 1 – May 31, 2026
• Line item: Halden API Build plan, quantity 1, $20.00
• Subtotal: $20.00
• Total excluding tax: $20.00
• Sales tax (18%): $3.60
• Total due: $23.60
• Amount paid: $0.00
• Amount remaining: $23.60

Questions go to the Halden help center. https://halden-email.s3.amazonaws.com/help

The footer gives the postal address and links to https://halden-email.s3.amazonaws.com/privacy and https://halden-email.s3.amazonaws.com/terms

Dark mode should be supported.

Use /world/halden-email for brand chrome and CSS; the transactional family fits. Use the absolute HTTPS URLs from tokens.json; do not use /world/ paths as image src.

Leave the HTML in output/email.html, a plain-text version in output/email.txt, and the subject in output/meta.json as {"subject": "..."}. Don't include From, To, or Date headers.