Back to the cake studio

Payment security

Payment comes after confirmed cake details.

A payment policy page explaining the intended secure checkout model, server-confirmed totals, disabled demo checkout, and future provider integration.

Current demo

Checkout remains disabled. The cart and builder can estimate totals, but no payment provider is called and no order record is created.

Future checkout

Production totals should be recalculated server-side from product, variant, add-on, delivery, tax, and discount rules before any payment session is created.

Verification

A real payment flow should rely on provider-confirmed status and signed webhooks, not on browser redirects alone.

Payment content describes the intended architecture and current demo boundary.