34 lines
2.9 KiB
Markdown
34 lines
2.9 KiB
Markdown
# ai& / aiand Promo Checkout Boundaries
|
|
|
|
Session-derived notes for handling ai& credit promo-code requests safely and usefully.
|
|
|
|
## What is allowed
|
|
- Help a user on **one legitimate account** navigate the official path: `https://console.aiand.com/` → billing/settings → purchase credits → hosted Stripe checkout → `Add promotion code` → apply code.
|
|
- Verify success only from observable state: discount line appears, checkout total changes to zero/expected amount, payment/confirmation completes, or console balance updates.
|
|
- If the user says the promo worked manually, treat that as a clue about environment differences (normal browser, Google OAuth, region/currency, existing account state), not as proof that automation should be escalated.
|
|
|
|
## What to avoid
|
|
- Do not automate bulk signup, alias/plus-address cycling, disposable-email account creation, or repeated attempts to obtain promo credits.
|
|
- Do not attempt to bypass Stripe/checkout rules or invent direct coupon endpoints when docs indicate the code is applied only in hosted checkout.
|
|
- Do not keep registering fresh accounts after a boundary has been stated; pivot to official one-account troubleshooting or a support email.
|
|
|
|
## Workflow when the user is impatient
|
|
1. Keep status updates short and action-first: `захожу`, `открываю billing`, `жму Purchase Credits`, `ввожу код`, `смотрю итог`.
|
|
2. If screenshots are unreadable or the image tool fails, say that plainly and ask for either a readable screenshot or the exact visible text; do not claim the image proves anything.
|
|
3. Re-run the exact official path once if the user insists a step exists. For ai&, the important sequence is: `Add Credits` → select `$50` → `Purchase` → hosted Stripe → `Ввести промокод` / `Add promotion code` → explicitly apply. Do not skip the `$50` preset step when validating the user's claim.
|
|
4. Report only the page state currently visible. If the code is merely typed into Stripe but subtotal remains `$50.00`, say it is not yet verified/applied.
|
|
5. If hosted Stripe returns `Code invalid`, do not guess from UI text alone. Capture the one-account Stripe `POST /v1/payment_pages/cs_live_...` response/HAR (see `references/stripe-hosted-checkout-promo-diagnostics.md`) and report the exact error code. If it is `payment_pages_promotion_code_invalid`, explain the limited set of likely causes: expired/exhausted promo, customer/email restriction, country/region restriction, currency/product/price restriction, or inactive merchant-side configuration. Offer support-message drafting.
|
|
|
|
## Support escalation template
|
|
```text
|
|
Subject: Promo code UNITABETAI not working
|
|
|
|
Hi ai& support,
|
|
|
|
I am trying to purchase credits through the official billing page and apply promo code UNITABETAI in the hosted Stripe checkout, but Stripe shows the code as invalid.
|
|
|
|
Could you confirm whether this code is still active, region-restricted, single-use, or account-specific?
|
|
|
|
Thanks.
|
|
```
|