'Register each URL into the matching Test Mode / Production Mode webhook slot in the Pancake dashboard. Separate endpoints prevent test traffic from accidentally crediting production accounts.'
'Register each URL into the matching Test Mode / Production Mode webhook slot in the Pancake dashboard. Separate endpoints prevent test traffic from accidentally crediting production accounts.'
'The environment (test vs production) is decided by the key you paste here — use the Test key while integrating, then swap to the Production key when going live.'
)}
</p>
<FormMessage/>
</FormItem>
)}
</div>
<divclassName='grid gap-1.5'>
<Label>{t('API Private Key')}</Label>
<Textarea
rows={4}
placeholder={t('Leave blank to keep the existing key')}
'The environment (test vs production) is decided by the key you paste here — use the Test key while integrating, then swap to the Production key when going live.'
)}
</p>
</div>
{/*
{/*
Binding section — split into two visually distinct paths:
(A) "Use existing" pair from the loaded catalog — only rendered when
the merchant actually has stores, so first-time setup isn't
...
...
@@ -567,160 +458,164 @@ export function WaffoPancakeSettingsSection(props: Props) {
The two paths are split by an "or" divider so the operator never has
'The bound Store is the parent container for every Pancake product new-api creates from this admin — both the wallet top-up product and any subscription-plan products. One store is enough; pin a different one only if you genuinely run separate Pancake catalogs.'
)}
</li>
<li>
{t(
'The bound Product powers wallet top-ups: when a user enters any amount, new-api runs the checkout against this single Pancake product and overrides the price per session — no need to pre-create $1 / $5 / $10 SKUs.'
)}
</li>
<li>
{t(
'Subscription plans do NOT use the bound Product — each plan has its own dedicated Pancake product, set in the Subscriptions admin (or auto-minted via the "+ Create" button there).'
)}
</li>
</ul>
</div>
{/* Create section — first, since creating auto-fills the pick-existing dropdowns below. */}
"Used as SuccessURL on the new product. You'll be prompted to confirm if left blank."
'The bound Store is the parent container for every Pancake product new-api creates from this admin — both the wallet top-up product and any subscription-plan products. One store is enough; pin a different one only if you genuinely run separate Pancake catalogs.'
)}
</p>
</li>
<li>
{t(
'The bound Product powers wallet top-ups: when a user enters any amount, new-api runs the checkout against this single Pancake product and overrides the price per session — no need to pre-create $1 / $5 / $10 SKUs.'
)}
</li>
<li>
{t(
'Subscription plans do NOT use the bound Product — each plan has its own dedicated Pancake product, set in the Subscriptions admin (or auto-minted via the "+ Create" button there).'
)}
</li>
</ul>
</div>
{/* Create section — first, since creating auto-fills the pick-existing dropdowns below. */}