How to Add Terms & Conditions and Name Verification to Your LaunchPass Page

What it does: Forces members to check a box agreeing to your rules before paying.

Why you need it:

Real scenario: Member requests refund after 3 months. You have "no refunds after 30 days" in T&C. They accepted it at signup. You show proof to Stripe. Dispute settled in your favor.

Without T&C: Member says "I never agreed to that." You have no proof. Harder to defend.

What it does: Requires members to type the name exactly as it appears on their credit card.

Why you need it:

Real scenario: Someone tries to join with stolen card. Name doesn't match. Card gets declined or flagged. Fraud prevented.

Without name verification: Easier for fraudsters to use stolen cards. More chargebacks. More headaches.

✅ You have specific refund policy (especially no refunds)
✅ You sell trading signals or financial advice
✅ Your content is controversial or polarizing
✅ You have strict community behavior rules
✅ You've had refund disputes before
✅ You charge high prices ($100+/month)
✅ You want legal protection
✅ Your community has rules members must follow

✅ You've had fraudulent signups
✅ You've had chargebacks
✅ You sell high-value access ($50+/month)
✅ You want extra fraud protection
✅ You're in fraud-prone industry (trading, crypto, gambling)
✅ You want to verify real people
✅ You've had problems with stolen cards

Don't require T&C if:

Don't require name on card if:

Balance: Protection vs friction. More requirements = safer but slower signup.

Before enabling in LaunchPass, you need actual Terms to link to.

Where to create T&C:

Make sure it's publicly accessible. Members must be able to read it before accepting.

What to include in your T&C (see template section below).

Examples:

Test the link: Open in incognito browser. Make sure anyone can view it.

Your page now requires T&C acceptance.

If checkbox appears and link works, you're done!

This one is simpler (no URL needed).

Done! That's it.

Field should appear and be required.

Standard checkout:

Takes 30-60 seconds.

Checkout adds:

Takes 45-75 seconds (extra 15 seconds to check box).

Checkout adds:

Takes 40-70 seconds (extra 10 seconds to type name).

Checkout includes:

Takes 60-90 seconds (extra 30 seconds total).

Conversion impact: Each extra field typically reduces conversion 5-10%. Balance security with friction.

Use this template as starting point. Customize for your community.

1. Refund Policy (Critical)

2. Cancellation Process

3. Community Rules

4. Disclaimers (Especially for Trading/Finance)

5. Payment Terms

6. Intellectual Property

7. Limitation of Liability

8. Access and Removal

9. Privacy Policy Reference

10. Technical Requirements

11. Contact Information

I am not a lawyer. This is not legal advice.

Terms & Conditions are legal documents. Consider:

For basic communities ($10-50/month):

For high-value communities ($100+/month):

For international communities:

When in doubt: Get legal advice. Cost of lawyer is less than cost of lost lawsuit.

Question: Where do you see who accepted your T&C and when?

Answer: Currently tracked by Stripe in subscription metadata.

Not visible in LaunchPass dashboard (as of current version).

For disputes:

Better tracking: Keep your own spreadsheet.

When member enters name:

If match: Payment processes normally

If no match: Depends on card issuer

Not foolproof but adds friction for fraudsters.

Does verify:

Does NOT verify:

Think of it as: Speed bump, not roadblock. Slows fraud but doesn't eliminate it.

Stripe handles actual verification:

You don't need to do anything except enable feature.

What happens: You toggle T&C on but don't add URL.

Result: Checkbox appears but link doesn't work. Members get confused.

Solution: Always paste your T&C URL after enabling.

What happens: You link to Google Doc with "view access" restricted.

Result: Members click link, see "Request Access," can't read terms.

Solution: Make document public ("Anyone with link can view").

What happens: You move/delete your T&C page. Link breaks.

Result: Members can't read terms. Sign up breaks or causes confusion.

Solution: Test link monthly. Use permanent URL if possible.

What happens: Your T&C is 20 pages of legal text.

Result: Nobody reads it. Looks intimidating. May reduce signups.

Solution: Keep it simple. 1-3 pages maximum. Use plain language.

What happens: T&C doesn't mention refunds.

Result: Member requests refund. You say no. They dispute with bank. You lose.

Solution: State refund policy clearly in T&C. "No refunds" or "30-day refunds only."

What happens: You enable name requirement. Don't test it.

Result: Field doesn't appear or doesn't work. Members can't sign up.

Solution: Always test after enabling any feature.

What happens: You change T&C after people joined.

Result: Original members never accepted new terms. Legally unclear.

Solution: Email members when T&C change. Give them option to review and accept or cancel.

1. Keep it simple

2. Be specific

3. Update when needed

4. Make it accessible

5. Reference in other places

1. Explain why

2. Show example

3. Test regularly

4. Monitor fraud rates

1. Balance security and conversion

2. Use both for high-risk scenarios

3. Consider A/B testing

Cause: Feature not enabled correctly or not saved.

Solution:

Cause: URL is incorrect or doc is private.

Solution:

Cause: Feature not toggled on.

Solution:

Cause: Name format issue or Stripe error.

Solution:

Cause: They're used to simpler signup.

Feedback: Some members will complain about "too many steps."

Response:

General rules:

Adding T&C checkbox:

Adding Name on Card:

Adding both:

Benefits outweigh costs when:

Calculate:

Test it: Run with features for 1 month. Compare metrics. Decide based on data.

No. Use what makes sense for your community. High-value or high-risk = both. Low-risk = neither or just T&C.

Yes. Update your document. Change the URL in LaunchPass. Notify existing members of changes.

They cannot complete signup. The "Subscribe" button won't work until they check the box.

Yes, as part of payment data. Used for verification and fraud prevention.

Yes, in Stripe subscription metadata. Not currently in LaunchPass dashboard.

No. Included with LaunchPass Premium ($29/month). No additional fees.

No. These are Premium features. Only available for paid communities (which require Premium plan).

Members cannot sign up (link broken). Keep T&C on reliable hosting. Test monthly.

You can use online T&C generators as starting point. Customize for your specific situation. Consider lawyer review for high-value communities.

Recommended but not required. Privacy Policy covers data handling. T&C covers membership terms. Can be separate documents or combined.

Currently only T&C checkbox available. For other agreements, include in your T&C document.

New signups won't see them. Existing members who accepted keep their acceptance on record in Stripe.

Before enabling these features:

Email: [email protected]

We help with:

Response time: Within 24 hours

For Terms & Conditions creation:

Not legal advice: LaunchPass support cannot provide legal guidance on T&C content.

Click blue rocket icon in LaunchPass dashboard for instant help.