Connect payments and build your checkout

Start your payment provider application now, before anything else on this page. Verification takes days, and it is the only thing on the launch path that can hold your go-live date. Then work through the rest of this page:

Connect a provider.
Build the checkout.
Decide what it collects.
Attach it to the channel that will use it.

Decide the provider and the form together. What the checkout asks for is what you have on the order afterwards, and merchants routinely reach the counter having never collected a phone number.

Connect a provider

Connect a provider under Settings → Payments.

Provider	Available to	What it takes
Stripe	Every store	Connect through TWICE’s own Stripe platform. No separate Stripe account needed. Enable the card methods you want to accept.
Manual methods	Every store	Add offline methods you accept (pay on pickup, bank transfer, cash) with a label and description. Reconciled by hand, not by a provider.
Adyen, SumUp	Selected merchants only, off by default	Skip these for a standard launch. Contact TWICE if your account needs one.

Enable Stripe card payments, and Apple Pay and Google Pay activate automatically. There is no separate toggle. TWICE registers your storefront domains for verification in the background. Neither wallet appears in an embedded (iframe) checkout link. Keep working down the launch path while verification clears. Nothing else depends on it finishing. It gates one thing only: a live-mode payment taken and refunded on a real card is a go-live condition, and you run that at Test your processes.

Build the checkout

Build the checkout under Settings → Checkouts. A checkout is a configurable flow from cart to confirmation. Build more than one where you need it, for example a B2C checkout and a separate B2B one, and duplicate an existing checkout rather than starting blank. Set the steps and sections first. Leave the styling until after launch, because colours and typography change nothing about what the checkout collects.

Step	Appears when	What it decides
Delivery	You enable it	Pickup, shipping, delivery, and the schedule customers pick from
Contact	You enable it	What you ask about the customer. See Decide what it collects
Additional details	An item in the order asks for extra information	Its own title and description
Payment	Always	Which of your connected system methods and any custom methods are offered
Confirmation	Always	The post-purchase screen’s information and layout items

If you take deposits, set the amount on the listing’s Pricing tab. A checkout carries no deposit setting. The amount reaches the checkout automatically once a deposit-carrying listing is in the cart. Decide here only whether the checkout offers a card method. Stripe and Adyen cards place the hold automatically. A checkout offering only manual methods still accepts these orders, and you track and release the deposit yourself. See Security Deposits.

Decide what it collects

Route every question to one of two places before you build the form.

Ask about	Put it	Lands on
The person, and it is a built-in (name, email, phone, address, tax ID, …)	A Customer field on the Contact step	The matching column on the customer profile
The person, and it is your own field (membership number, licence class)	A customer attribute, surfaced on the Contact step	The attribute on the customer profile
The item they are taking (height, shoe size, a condition acknowledgement)	A listing checkout field, on that listing’s Checkout Settings tab	The order line, not the customer

Put a phone number on Contact once, and every future order has it. Put a shoe size on the listing, and only orders for that listing ask it. Mixing the two up is the most common way a launch checkout collects the wrong thing in the wrong place. Full detail on each: collect customer data at checkout for the person, ask customers for information at checkout for the item.

Attach it to the channel that will use it

Set the checkout’s status to Active. A checkout does nothing until it is active and reachable. Then do one of these:

Mark it Default for the whole account, or
Connect it to a specific storefront in the Theme Editor’s Checkout page, or
Assign it to one or more locations there, for locations with different requirements, such as a ship-only warehouse with no pickup step.

Priority	Source
1	The customer’s selected location, if it has a checkout assigned
2	The storefront’s own default, set in the Theme Editor
3	The account’s Default checkout

Remove a location assignment before you deactivate or delete a checkout. A checkout assigned to a location cannot be removed while the assignment stands, and removing the assignment falls that location back to the next checkout in the priority order above. Check that fallback is the one you want first.

Done when

Every payment method you plan to accept is connected under Settings → Payments, and Stripe verification is complete or visibly in progress.
At least one checkout is Active and either marked Default or assigned to the channel that will use it.
The Contact step asks for exactly the account-level details you need, and nothing you have not decided to act on.
Every per-item question (sizing, personalisation text, a condition acknowledgement) lives on the listing’s Checkout Settings tab, not on the checkout.
If you take deposits, the deposit is set on the relevant listings’ Pricing tabs, and at least one connected method on the checkout can place an automatic hold, or you have a plan to track manual ones yourself.