/signup is the entry point for creating a new self-serve Paybond workspace. Public marketing offers Sandbox (free) and Pay as you go. Prepaid Credits packs are purchased after activation from /console/configuration/billing. Custom volume, SSO, and procurement start at /contact/sales.
Starter, Team, and Business plan IDs remain in the catalog for existing subscribers and entitlement checks, but they are not advertised for new self-serve signup or console upgrades.
Which plans use signup
| Plan | Entry point | Best fit |
|---|---|---|
| Sandbox (Free) | /signup or /signup?plan=free | Sandbox-only first guardrail integration |
| Pay as you go | /signup?plan=payg | Production usage billed per intent |
| Credits | /signup?plan=payg&product=credits then Billing → Credits | Prepaid packs after PAYG activation |
| Custom needs | /contact/sales | Procurement, SSO contracts, custom volume |
When to use signup
Use /signup when:
- you are creating a new Paybond workspace on Sandbox or Pay as you go
- you want the published self-serve onboarding path without a sales process
Use another entry point when:
/console/loginis needed because the workspace already exists/contact/salesis needed for custom terms or procurement review
In short:
/signupcreates a new self-serve workspace/console/loginopens an existing workspace/contact/salesstarts custom / procurement conversations- Credits packs are bought in console Billing after the workspace exists
What buyers should expect during signup
The self-serve flow is designed to stay simple:
- Choose Sandbox or Pay as you go (pricing CTAs pre-select the plan query parameter when applicable).
- Enter the details needed to create the workspace.
- Verify the owner email address.
- If Pay as you go, complete Stripe Checkout to attach a payment method ($0 until production intents run).
- Activate the workspace.
- Continue into onboarding in the console. Buy Credits packs from Billing when you want prepaid burn.
Plan-level behaviors:
- Sandbox (Free) completes without paid checkout and is intended for sandbox-only guardrail integration. Live settlement rails stay blocked.
- Pay as you go requires checkout even though the monthly anchor is $0. Stripe collects a payment method up front and attaches a subscription with metered intent (and settled-volume when configured) line items. Production usage is billed from intent #1 with no included bundle.
- Credits are one-time Stripe Checkout purchases (
mode=payment) that credit a tenant-scoped prepaid balance. Meter sync prefers drawing down Credits before reporting PAYG / overage units to Stripe.
After Pay as you go activates, the workspace owner can enable live settlement rails and create production API keys from the console.
After signup
After activation, the workspace owner is taken into the console onboarding flow to complete setup for the new tenant.
From that point on:
- future access uses
/console/login, not/signup - available console features depend on the selected plan
- tenant-specific configuration is completed inside the workspace after signup
- free tenants upgrade to Pay as you go from
/console/configuration/billing - prepaid Credits packs are purchased from the same Billing page
- existing Starter / Team / Business subscribers continue to manage those subscriptions through the Stripe Customer Portal (not advertised for new upgrades)
Entry-point guidance
- Landing page CTAs for Sandbox and PAYG should lead to
/signupwith the appropriateplanquery parameter. - Credits CTAs should lead to
/signup?plan=payg&product=credits(then Billing after activation) or directly to Billing for signed-in tenant admins. - Pricing is the public commercial comparison page (Sandbox / PAYG / Credits).
- Custom / talk-to-sales CTAs should lead to
/contact/sales, not to the self-serve form. - Public
Sign inactions should lead to/console/login.