- Payment guide: explains the current payment path, return path, and real boundary first.
- Registration page: for first purchase, where team info, domain, admin account, and plan are registered.
- Renewal / recovery page: for existing tenants that need to resume service.
- Redeem page: where users return after payment and continue the activation or recovery path.
Tenant Payment Guide
Payment Guide for Formal Team Tenants
Current Tenant TruthThe current standard-tenant line should not be described as “full in-site checkout plus auto-activation.” The real current framing is: keep the order and tenant context on-site, jump to LDXP for payment, and then return with a redeem code to continue activation or recovery.
This page separates first purchase, renewal recovery, redeem-code return, and the current boundary so they no longer get mixed back into the personal free path or the private-deployment template.
tenant_1001 sample slottenant_1003+ shared SaaSLDXP paymentRedeem-code returnAuto-activation still not promised
- This is still not a complete general subscription center for all tenants.
- Auto-renew only records the preference for now; it does not mean automatic deduction is live.
- Auto-activation, auto-recovery, formal third-party payment callbacks, and signature verification are still not part of the public promise.
- The private-deployment template
tenant_1002still does not run a public self-serve payment path and remains project or contract based.
Step 01
On-site onboarding first
- The tenant side first records the team or customer name, contact, domain, and admin account.
- The order and tenant context stay on-site before payment, instead of scattering payment actions across unrelated forms.
- This is carried by the shared-SaaS frontend.
tenant_1001only verifies the same formal path as a sample slot.
Step 02
Jump to LDXP for payment
- The current environment decides whether monthly and annual plans jump to separate product URLs.
- If separate product URLs are not configured, both plans fall back to the same LDXP entry.
- The public wording should stay: “payment currently goes through LDXP, and the final product split depends on the current environment configuration.”
Step 03
Return with a redeem code
- After payment, the user returns with a redeem code and matches it against the on-site order.
- Once the redeem succeeds, the order continues into activation or recovery instead of the user manually editing tenant state.
- The result page, login page, and tenant workspace then take over the next confirmation step.
Role Split
How 1001, 1002, and 1003+ differ on payment framing
| Slot | Current role | Current payment framing | What it should not be confused with |
|---|---|---|---|
tenant_1001 | Standard-tenant sample / main-path verification slot | Shares the same payment framing as standard SaaS, used to verify first purchase, renewal, and redeem-code return | It should not be described as the public commercial sales slot |
tenant_1002 | Data automation platform / private-deployment template / internal delivery console | Project or contract based today, without public self-serve payment | It should not be described as the standard team-edition online subscription page |
tenant_1003+ | Standard SaaS shared tenant | The formal current public team entry; keep the order and context on-site, pay through LDXP, then return for redeem or continued handling | It should not go back to cloning a new frontend per tenant |
What To Say
More accurate public wording right now
- It is accurate to say that the standard tenant side already separates payment guidance, first-purchase onboarding, renewal recovery, and redeem-code return.
- It is accurate to say that payment currently goes through LDXP first, then returns on-site to continue activation or recovery against the order.
- It is not accurate to say that the standard team edition already has a complete general online subscription center.
- It is not accurate to say that all tenants already support automatic activation, automatic recovery, and formal third-party callback handling.
- It is not accurate to say that the private-deployment template
tenant_1002is also a public standard payment entry today.