Checkout

Clear steps for a high-emotion purchase.

The checkout should feel calm and precise: who receives it, where it goes, when it arrives, what the card says, and how the shop should handle substitutions.

Returning customer

Sign in to use saved checkout details.

A logged-in customer profile can pre-populate contact info, billing, recipient addresses, house account eligibility, and saved preferences.

Customer

Purchaser/contact details sent with the web order and used for receipts, questions, and delivery updates.

First name Last name Email Phone Company / account name

House account eligibility Approved for account billing

Backend indicator: enabled · Account MS-10482 · Net 30 terms · POS validation pending integration

Billing

Billing address supports AVS/payment authorization through the existing Azure/Fusebox connector.

Billing street address City State ZIP code Country

Recipient

Fulfillment mode, requested date, ZIP/zone, and delivery fee carry over from product selection and are confirmed here before payment.

Recipient first name Recipient last name Recipient phone Location type Delivery street address Suite / room / unit City State ZIP code Delivery instructions

Zone A · East Dallas $19.95 delivery · same-day cutoff 1:00 PM

Occasion & Card Message

Occasion is a structured MAS field; message text should enforce the line/character limits MAS expects.

Occasion Signature Card message 42/350 characters · POS-safe format: 10 lines of 35 characters

Limit: 350 characters, matching the POS comfort zone of 10 lines at 35 characters.

Delivery

Delivery zone Zone A · East Dallas

Delivery charge $19.95

Same-day cutoff 1:00 PM

Requested delivery date

Available today for this zone. Blackout dates and capacity limits should disable unavailable dates before payment.

Secure Payment

Card details should be collected with Fusebox-hosted secure fields or tokenized inputs, so the website never stores raw card data. House account appears only for approved customers.

Encrypted payment fields

Card number

Expiration CVV Billing ZIP

In production these inputs would be Fusebox secure fields or an embedded payment component that returns only token/auth metadata.