# Separate marketing site and backend

Follow a customer journey across your site, checkout, and backend.



## What you need [#what-you-need]

List the marketing site, app, checkout, and backend involved in the journey, and who can edit each one. You need a reliable way to confirm success and an approved plan for the actual HTTPS sites.

## Map and connect the journey [#map-and-connect-the-journey]

1. Write down the customer’s path, for example: “Framer page → app checkout request → payment provider → our verified webhook.” Check each part. Sites that share a hostname do not necessarily share code or access.
2. Configure the right site and known checkout domains. If you need to carry browser context into checkout, create a fresh `checkoutAttemptId` UUID (a random identifier with no customer details) after consent. Wait for `tracking.handoff(checkoutAttemptId)` in the browser.
3. Pass only that ID through your checkout-start request and checkout metadata. Once your payment handler verifies a successful payment, pass the handoff ID separately from the payment’s own ID.

Your site must be able to run the handoff, and you must agree to a live-mode test; browser verification mode cannot perform it. `stored` means Tyton saved checkout context, not that a purchase happened.

## Keep the two IDs separate [#keep-the-two-ids-separate]

Checkout attempts join browser context. Payment IDs identify conversions: renewals need new IDs; payment retries retain their ID and original time.

Do not transfer `_fbp`, `_fbc`, IP, or user-agent values in checkout URLs or provider metadata. Do not overwrite an existing provider customer reference. Tyton does not automatically decorate links or guess the domains.

## Success check [#success-check]

Test a completed payment, a failed payment, and a repeated provider notification. Check that there is one real payment and the same payment ID on retries. If the handoff is missing, the valid conversion still goes through with the information available to the backend.

## If you get stuck [#if-you-get-stuck]

A closed checkout with no trusted success callback or editable webhook path cannot support the required server Purchase integration. Report the gap explicitly; a return URL is not payment proof.
