Checkout Sessions
Usetagada.checkout.createSession to build pre-loaded checkout links: cart line items, currency, and optional customer data are applied before the customer lands on your checkout page.
createSession follows the /checkout/init redirect and returns the final URL plus a checkoutToken (when available) without forcing the browser through the 302.Create a basic session
| Field | Description |
|---|---|
redirectUrl | Fully qualified URL to open in the browser |
checkoutToken | Token extracted from the URL when present (e.g. for asyncStatus) |
Pre-fill customer data
Optional string fields are passed through to checkout init:Customer tags for funnel routing
Attach tags so funnel edge conditions (e.g.customer.hasTag) can route the session:
Async payment status (3DS redirects)
After a redirect-based flow (e.g. 3DS), poll session status with the token fromcreateSession:
checkoutToken may be null if it is not present on the redirect URL. Ensure createSession is used (not the deprecated init helper) so the client can parse the token reliably.SDK methods reference
| Method | Description |
|---|---|
tagada.checkout.createSession(params) | Build query for /checkout/init, return { redirectUrl, checkoutToken } |
tagada.checkout.asyncStatus(checkoutToken) | GET async status after redirects |
tagada.checkout.pay(params) | Server-side pay for an existing session (checkoutSessionId, instrument, etc.) |
tagada.checkout.init(params) | Deprecated — prefer createSession |
createSession params include storeId, items, currency, checkoutUrl, returnUrl, locale, customerId, customerEmail, customerFirstName, customerLastName, customerPhone, customerTags, cartToken, and draft.
Next steps
Upsell & downsell funnel
Conditional routing after checkout using funnel edges
Customer management
Tags, listing, and funnel conditions tied to customers
Merchant quick start
End-to-end setup through a live checkout link
Step config guide
Per-step checkout UI, scripts, and order bumps
