Prompt 1,251 words Copy
# Design from Reference: Checkout.com Payment Details
Create an original, high-fidelity visual design inspired by the reference. Prioritize composition, typography, colors, spacing, and component styling over technical implementation.
## Reference
- **Product:** Checkout.com
- **Category:** Details
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/e89731b5ea5e4c56fa83-1600.webp)
- **Source:** https://dashboard.sandbox.checkout.com/payments/all-payments/payment/pay_5ztbia6k422e5lvv5ggx3vovdy
Analyze the attached screenshot first. If no image is attached, open the screenshot link; if neither is accessible, ask for it rather than guessing.
## Visual Design Context
### Overall aesthetic
- **Character:** A restrained financial operations interface built from white space, thin gray rules, black text and blue navigation accents. Data appears directly on the canvas rather than inside elevated cards.
- **Density:** A long, information-rich detail page balances compact metadata with generous gaps between the timeline, payment information, device details and risk charts.
### Page composition
- **Capture scale:** The source measures 2880 × 4360 image pixels. The following CSS estimates assume a 2× capture scale; device-pixel ratio is unverified.
- **Application shell:** Two full-width navigation rows sit below a small workspace header. Primary navigation spans both ends of the screen; the active Payments tab has a blue underline. The secondary row contains three payment views.
- **Main column:** A centered content region approximately 1200 CSS px wide has about 120 px side margins. A breadcrumb-style page title precedes the amount, status, actions and three metadata groups.
- **Vertical regions:** A four-event timeline leads into payment-method columns, paired purchase/customer sections, a full-width device section and a two-column risk assessment. An outlined information banner closes the page.
### Information hierarchy
- **Page identity:** A bold title and large amount establish the record; the currency is smaller and muted, with a compact Captured badge beside it.
- **Section structure:** Small semibold headings and full-width hairline dividers define each information group without introducing large card containers.
- **Field relationships:** Muted labels align in narrow left columns, while darker values occupy wider right columns. Copy icons follow selected identifiers.
- **Risk emphasis:** A green score badge, segmented scale and orange/green contribution bars provide the strongest visual signals near the bottom.
### Typography
- **Family:** A neutral sans serif is visible throughout; the exact font is unverified.
- **Headings:** The page title and amount are approximately 28 px CSS, bold, with roughly 34 px line height. Section headings are approximately 14 px and semibold.
- **Data and navigation:** Most labels, values and navigation items are approximately 14 px, with 20–24 px line height. Long addresses and explanatory values wrap within their columns.
- **Contrast by role:** Labels use gray, values use near-black and actionable text uses blue. Timeline dates are semibold; event amounts are quieter.
### Colors & surfaces
- **Measured foundation:** ICC-aware conversion to sRGB yields a dominant white canvas of #FFFFFF, black text pixels of #000000, muted dark gray #5C5B60 and light neutral badge/surface pixels #F4F2F2.
- **Borders:** Sampled neutral gray #DFDDDD supports subtle dividers and pill outlines; antialiasing produces additional edge shades.
- **Navigation and actions:** Measured blue #006BFF marks the primary action, links and active navigation. Pale blue #CAE5FF appears in highlighted navigation and the information treatment.
- **Chart palette:** Measured orange-red #FF5F3B fills positive contribution bars. Bright green indicates decreasing contributions and lower risk; yellow bridges the segmented risk scale.
### Components
- **Actions:** Two compact, roughly 32 px high buttons sit to the right of the amount row. The secondary action has a gray surface; the primary action is solid blue with white icon and text. Corners appear approximately 3–4 px.
- **Timeline:** Four chevrons align on a fine vertical connector. Each event combines a date, rounded status/code chips, an amount and, where applicable, a blue assessment link.
- **Definition lists:** Payment information uses two equal-width groups, with approximately 165 px label tracks. Small card-brand and country symbols appear inline with values.
- **Risk visualization:** A narrow score panel is separated from the wider horizontal contribution chart by a vertical rule. Dotted grid lines support category comparison; a legend sits below.
- **Information banner:** A full-width box has a thin blue border, approximately 6 px radius, a pale-blue icon strip and two lines of small explanatory text.
### Visual rhythm
- **Section spacing:** Major groups are separated by approximately 55–70 px CSS, while definition-list rows follow a compact 32 px cadence.
- **Alignment:** Section headings, rules, metadata and the closing banner share the main left edge. Paired columns maintain consistent gutters of approximately 16–24 px.
- **Controlled whitespace:** The timeline occupies only the left portion of the canvas, leaving substantial breathing room on the right before the denser information sections.
### Responsive
- **Evidence boundary:** Only the desktop capture is available; the following behaviors are recommendations.
- **Column collapse:** Stack payment-method groups, purchase/customer details and risk panels on narrow screens. Preserve label/value relationships and allow long values to wrap.
- **Navigation and actions:** Replace the wide primary navigation with an accessible compact menu. Stack or wrap the amount and action controls without shrinking their touch targets.
- **Charts:** Retain readable category labels and a clear zero baseline; use horizontal scrolling or a dedicated compact chart layout when necessary.
### Adaptation guidance
- **Preserve the data grammar:** Reuse section rules, aligned definition lists, inline copy affordances and timeline chips for detailed operational records.
- **Build reusable tokens:** Start with a white canvas, 14 px body type, compact 32 px controls, 4–6 px radii and a blue action color; calibrate these CSS estimates against the target product.
- **Handle variable content:** Test wrapped field values, missing metadata, longer event histories and larger contribution labels while keeping section alignment stable.
- **Use semantic signals:** Pair status colors with labels and chart legends. Keep transaction identifiers and personal values as replaceable data rather than embedding the screenshot's contents.
## Content
**Instructions:**
Generate realistic example content that fits the selected design reference.
Create appropriate headlines, descriptions, labels, buttons, and supporting copy based on the type of interface being designed.
If a product or business description is provided, use it to guide the content.
Otherwise, invent a plausible fictional SaaS product appropriate for the reference.
Keep the content concise, coherent, and visually balanced.
Do not present fictional statistics, customer names, or testimonials as verified facts.
## Design Direction
**Instructions:**
Use the reference screenshot as the main source of visual inspiration rather than a strict layout template.
Preserve its most distinctive design characteristics, such as typography, visual rhythm, color relationships, component treatments, and overall aesthetic.
Feel free to modify section arrangements, proportions, spacing, and individual components to better suit my content.
Introduce original design decisions where they improve usability, composition, or brand consistency.
The result should clearly reflect the reference's visual language without looking like a direct reproduction.
Follow the visual identity of the reference design.
Use its typography, color palette, component styling, and overall aesthetic as the primary design direction.
Do not introduce an unrelated visual identity.
## Output
**Instructions:**
Generate a high-fidelity visual mockup of the requested interface.
Present the design as a polished, realistic website or product UI screenshot.
Prioritize visual composition, typography, spacing, colors, alignment, and component details.
Use the available image-generation or visual-design capabilities.
Do not replace the mockup with source code, a written design specification, or a textual description.
If direct visual generation is unavailable, clearly explain the limitation.
## Constraints
- Use the actual screenshot as the primary visual reference.
- Preserve essential messaging and factual accuracy.
- Prioritize visual quality and consistency.
- Do not invent unsupported product claims.
- Adapt structure and copy length for visual balance. Reference image Attach it to your message: assistants can’t open image links. Open in ChatGPT ↗ Open in Claude ↗
Build it in Lovable ↗ v0 ↗ Figma Make ↗
Opening a tool copies the screenshot so you can paste it with your prompt.