Skip to content
One Insurance

Insurance patterns

Payment review

Separate the amount due, the payment state, and the policy issuance state.

Usage & approach

These are visual examples, not a payment integration. Never collect card details in an unapproved form. Amounts and references are fictional. Use the actual backend state for pending, successful, and failed payments, and keep recovery actions specific.

Specifications

Amount
text-3xl font-semibold tabular-nums
Reference
font-mono text-xs break-all
Status
Explicit message; no reliance on color alone.
Recovery
One clear next action for a failed payment.

Pending payment

A neutral pending state keeps the expected next step clear.

HTML + Tailwind CSS · fit to panel

Failed payment

Explain the failure without exposing provider internals.

HTML + Tailwind CSS · fit to panel

Bring this into your project

Copy the HTML from the code panel. Keep complete utility names in files scanned by Tailwind, retain accessible labels and focus styles, and connect actions to your own application. Preview controls belong to this documentation and are not part of the copied example.

IFRC One Insurance · UI Reference
Tailwind CSS v4.3.3 · Visual examples, ready to adapt.