# Nova Triage 7 USDC Sample Deliverable

## Scope

Focused review of a public product/API/landing page with one objective:
turn scattered issues into a short action list the owner can execute today.

## Example Input

A SaaS landing page offers "crypto payments in minutes" and links users to signup,
API docs, and dashboard screenshots.

## Findings

### 1. Primary CTA Is Too Vague

The page asks users to "Get Started" before explaining what they receive after signup.
For developer tools, this usually underperforms against a concrete action.

Recommended change:

Use a primary CTA such as `Create a Test Payment` or `Generate Checkout Link`.
Keep `View Docs` as the secondary CTA.

### 2. Proof Is Not Close Enough To The Claim

The strongest claim is fast crypto checkout setup, but the proof appears later or is
not shown as a working flow.

Recommended change:

Add a compact 3-step proof block above the fold:

1. Create business
2. Add wallet
3. Generate payment link

Include a tiny sample response with `payment_url`, `payment_address`, `amount`,
and `expires_at`.

### 3. Buyer Risk Is Not Addressed

The landing page does not immediately answer what happens if a payment expires,
is underpaid, or lands on the wrong network.

Recommended change:

Add a short "Payment states" section:

- `pending`: waiting for funds
- `detected`: transaction seen
- `confirmed`: enough confirmations
- `forwarded`: funds sent to merchant wallet
- `expired`: checkout should be regenerated

### 4. Developer Handoff Needs One Copy-Paste Example

The page describes API usage, but the conversion path improves if the visitor can
copy one complete request immediately.

Recommended change:

Add a tested minimal cURL example:

```bash
curl -X POST https://example.com/api/payments/create \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "business_id": "YOUR_BUSINESS_ID",
    "amount": 7,
    "currency": "USDC_SOL",
    "description": "Test checkout"
  }'
```

## Priority Order

1. Replace vague CTA with a concrete checkout action.
2. Move proof of the payment flow above the fold.
3. Add payment-state handling to reduce buyer anxiety.
4. Add one complete API example.

## Verification Notes

This style of deliverable is intentionally concise: it avoids broad redesign advice
and focuses on fixes a founder or developer can ship quickly.