“.co in Fintech: Where It Clears and Where It Doesn’t (Comps)”

Why This Matters
Outcomes & Guardrails
The Framework
Messaging Templates
Checklists
Playbooks & Sequences
Case Study (Sample)
Metrics & Telemetry
Tools & Integrations
Rollout Timeline
Objections & FAQ
Pitfalls to Avoid
Troubleshooting
More
Next Steps

Why This Matters

In fintech, every touchpoint is high-stakes. Domain selection—often a fast decision—directly impacts trust, conversion, growth velocity, and operational safety. Too often, it’s approached like a branding afterthought: “.com taken? Let’s take the .co.” But with financial products, you’re not just selling convenience; you’re convincing users, backers, and partners you take risk (and detail) seriously.

Why does domain choice matter so much in fintech?

Perception: Users—especially high-value or compliance-focused audiences—map trust to digital cues. Unfamiliar TLD? That can create an outsized perception problem.
Conversion friction: Typos, lost emails, and misdirected traffic silently erode signups and trust.
Investor diligence: Experienced VCs and acquirers know domain confusion is a latent risk; it signals operational rigor (or lack thereof).
Security posture: Phishing, spoofing, or user error risks spike if .co and .com coexist, or if user education is thin.
Legal/compliance: Regulated markets (e.g., payments, asset management) often have higher documentation, disclosure, and auditing burdens—your domain can complicate, or de-risk, compliance processes.

You’re reading this because you want…

Field-tested, founder-to-founder clarity on “should we ship with .co?”
Comps from funded, launched, and acquired fintechs—did they stay .co, or migrate?
Strategic frameworks and messaging that wantonly reduce risk and ambiguity.
Real world checklists, tactical playbooks, and edge-case readiness (not just branding lore).

On the line is your brand’s trust flow. Make it a competitive advantage, not a hidden liability. Absolutely lets you cut through the noise fast—sign up for a free brand/domain review or browse best-fit fintech names at www.namiable.com.

Outcomes & Guardrails

Outcomes

Upon completing this guide, you’ll have:

Decision Confidence: A defendable framework to assess where .co fits your model and risk profile.
Market Awareness: Benchmarks and “market comps” to calibrate what actually clears in fintech (who stuck with .co? Who migrated? Why?).
Clear Messaging: Repeatable templates for users, partners, and investors, reducing question fatigue and anchoring trust.
Operational Readiness: Deployment checklists so you avoid “uh-oh” moments at launch, in email, or at scale.
Migration Planning: The insurance of a realistic migration/multi-domain strategy for futureproofing or fundraising.
Case Law: Hard evidence and stories from those who traveled this path, with actionable takeaways.

Guardrails

Applicability: Recommendations strictly tuned for fintech (banking, payments, B2B SaaS, lending, insurance, DeFi)—not general e-commerce, direct-to-consumer or non-regulated SaaS.
Recency: All examples sourced from 2021–2024 launches, fundraising events, or exits.
Definition of Clear/Doesn’t Clear: “Clear” means the domain presents no structural user friction, no conversion or revenue drag, and avoids major legal/investor/partner concerns. “Doesn’t Clear” means it introduces unignorable barriers or recurring points of confusion/skepticism.
Data-driven: Opinions supported by founder/investor interviews, direct user data, and market outcomes.

Start strong. Reduce friction before it compounds.
Absolutely’s fintech toolkit will help you make the right call—try free, or secure your fintech .co or .com at www.namiable.com.

The Framework

Use this detailed “.co in fintech” decision framework:

1. Primary Audience Analysis

Consumer (B2C): Will your users trust a .co? Younger/bankless/crypto-adjacent cohorts often do, older/more conservative segments less so.
- Edge Case: Serving both? Map your riskiest demo.
SMB: Owners are increasingly TLD-agnostic but look for clarity and security cues.
Enterprise: IT, MIC, and compliance teams are trained to flag non-.com emails/domains. Expect pushback or IT blocks for anything unfamiliar.
- Operator Tip: Pretest with a contact’s corporate email/endpoint filtering.

2. Brand/Trust Alignment

Immediate Trust: Are you handling money at signup? .co is more acceptable in lightweight, social, or marketplace flows—more risk if moving or storing funds upfront.
Brand Differentiation: Does ”yourbrand.co” easily get confused with a .com competitor? Are they live? Are they in the same vertical, or is there trademark risk?

3. Channel and Funnel Checkpoints

Traffic Sources: If your traffic is mostly direct (typed-in), domain confusion is higher risk than when people reach you via links/search/apps.
Typed vs. Clickthrough: Mobile-first apps experience less direct domain confusion than web-first onboarding funnels.
Referral/Testimonial Risk: Third-party mentions (PR, blogs, podcasts) can incorrectly cite .com, not .co.

4. Peer and Market Comps

Peer Audit: Dig up at least 15 recent fintech launches—what TLDs did they open with, and how did this affect their growth, PR, and funding?
Migration Rate: What % of .co fintechs locked in .com or rebranded before Series B/C? (See case studies and comps further below.)

5. Regulatory & Legal Review

KYC/Compliance: Are you launching in a market or vertical with heightened disclosure or fraud prevention requirements? Will partners/examiners question a .co?
- Edge Case: Cross-border/EMI/crypto? Regulator unfamiliarity with .co is a real (if niche) risk.
Spoofing/Phishing: If .com is available/unprotected, bad actors may target your user base. Monitor and register defensively where feasible.

6. Email Reliability

Deliverability: Test both transactional and marketing emails from your .co to major providers. Look for misrouted, delayed, or spam-flagged mail.
- Edge Case: New gTLDs (like .finance or .pay) can face even higher friction—.co fares better, but still less than .com.

7. Fundraising/Investor Diligence

VC/PE Skepticism: Some VCs will surface brand (domain) risk in due diligence checklists. Seasoned teams proactively address this.
- Operator Example: Preempt with a memo; cite comps who cleared or migrated their .co.

8. Future-proofing & Optionality

Reserve and Monitor Alternatives: Have you registered the .com (or defensively registered obvious typo/brand variants)? If not, what’s your price to buy? Who else owns them?
Migration Friendly: Can you redirect, re-educate, and cleanly migrate if business needs shift?

Run this as a scored checklist with your team.
Decision fatigue and “brand debate” wastes months—let data and founder comps guide you.
Get side-by-side custom market comps and migration calculators at Absolutely or www.namiable.com.

Messaging Templates

Clear messaging keeps you ahead of confusion, supports internal adoption, and supports sales, fundraising, and legal ops. Use these as plug-and-play comms:

1. To Partners

Subject: Our Domain Strategy: [brand].co

Hi [Partner],

We’re thrilled to ramp up our partnership, and wanted to clarify a small but important detail: our web and email presence runs exclusively on [yourbrand].co. This domain is trusted by many fintech leaders—selected for global accessibility, security, and modernity.

Should you or your IT/security teams need additional assurance or want a whitelist for communications, our technical documentation is ready.

Thanks for your partnership,
[Your Name]

2. To Customers

FAQ / Site Copy:

Why [brand].co?

Like industry innovators Brex (launched as brex.co) and Monzo, we selected .co for its memorability and trusted reputation in fintech. Look for secure SSL/TLS lock icons, and always log in directly at our .co domain to keep your account protected.

Pro tip: Add “Remember: .co, not .com” below email logins, and set up banners during onboarding.

3. To Investors

Subject: Proactively Addressing Brand Domain for [Upcoming Fundraise]

Dear [Name],

In anticipation of diligence review, here’s clarity on our [brand].co decision. Like several high-growth fintechs, we selected .co for availability, speed to market, and strong industry precedent. Our commitment to email and user education, domain monitoring, and eventual migration planning make this a non-issue in trust and conversion.

Full details on our reasoning, comps, and domain watch strategy are attached.

Best,
[Founder Name]

4. Internal FAQ / Slack Memo

Why are we .co?

Extensively validated with market data and founder interviews.
All comms, credentials, and product links are .co; report any misdirects or login confusion internally.
For full rationale see [Notion doc link] or ping [PM/brand lead].

5. User Migration Notification

Subject: Streamlined Access: We’re Now [brand].co

Hello [User],

We’re upgrading your experience! Going forward, access your dashboard and support resources at [brand].co. Please update saved bookmarks and make sure all correspondence is through @brand.co emails for the best support.

Need help? Full migration details are on our support page [link].

6. For Legal & Compliance Partners

To: Legal/Compliance Points of Contact

Please be advised that as of [DATE], all regulatory correspondence, KYC docs, and secure transmissions will originate from .co addresses. Contact [compliance lead] with any validation or security checklist needs.

For tailored messaging packs and compliance frameworks,
Absolutely delivers peace-of-mind—explore founder-friendly templates for every channel at www.namiable.com.

Checklists

You cannot fix what you don’t systematically check. Expand each checklist to shore up edge-cases and non-obvious failure points.

1. Prelaunch .co Domain Checklist

Competitor Scan: Document top 20 fintechs (stage, market, TLD); analyze any .co to .com migrations or branding pivots.
WHOIS & Trademark: Confirm legal clearance, spot recent transfers, check for name disputes or legacy use in key markets.
Nickname/Phishing: Register most common typos, close .com/.info/.net versions defensively, or monitor with an alert service.
Email Testing: Use tools like Mail-tester.com and reach test with 10+ providers, including major banks and regulated entities.
Security Baseline: Implement SPF, DKIM, DMARC; set up Threat Intelligence (e.g. KnowBe4, EasyDMARC).
Customer Journey: Run 10+ onboarding flows; map fall-off, lost password, trust screens—flag when/where domain becomes salient.
Analytics Prep: Wire up site events to track domain-typed, misdirected, or bot-traffic-to-.com errors.
Go-Live Review: Confirm all assets (PDFs, job posts, decks, ad copy, SMS) direct to .co as canonical domain.

2. Ongoing Operations & Monitoring

Deliverability and Spam Watch: Ongoing daily/weekly reports, proactive delisting requests with providers as needed.
Customer Feedback Loop: Quarterly surveys or “Did you have any trouble finding/signing in?” opt-in.
Phishing and Lookalike Scan: Automated tools/patrol for spoofed .co/.com/typo squatters.
Reputation Scan: Monitor review sites, product-hunt, and fintech forums for confusion or misattribution.

3. VC Diligence & Funding Readiness

Domain Narrative: Brief explaining “Why .co”—reference market comps, technical controls, and migration options.
Comps List: At least five recent .co fintech success stories (and if/when they migrated).
Downside Plan: Clean migration path and estimated timeline/budget for a .com switch if required.
Email Seeding: Ensure all current/future comms with investors are standardized and typo-proofed.

4. Migration Staging

Tech Stack: Full audit—redirects, SSL, domain mappings, cloud services, app stores, and OAuth endpoints.
Search/SEO: Inventory top inbound links, update or 301 as feasible; preserve rankings with 90+ days monitoring.
Staff & Partner Sync: Notify well in advance—no “breaking changes” without hand-holding.
Backwards Compatibility: Forward support for legacy addresses until adoption is complete (90–180 days).

Get every checklist—plus war room checklists for failed launches, investor pushback, and compliant branding—free on Absolutely or via the fintech launch hub at www.namiable.com.

Playbooks & Sequences

Move from theory to best-in-class execution—stepwise playbooks for launch, validation, and mitigation.

Playbook 1: .co Domain Prelaunch Validation

Step 1: Stakeholder Alignment

Meet with product, brand, legal, and compliance leads—review .co fit using this guide.
Assign owner for risk, legal, and partner communication.

Step 2: Market Pulse

Launch voice-of-customer polling: run 10–15 interviews (across customer, investor, partner, and SMB/enterprise verticals).
Run split-test homepage with .co and .com “lookalikes”; map perception gaps.

Step 3: Technical Readiness

Register all logical variants (brandco.com, brnd.co, yourbrand.co.uk).
Implement SPF/DKIM/DMARC, configure Google Postmaster and Microsoft SNDS.
Test transactional flows on all major ISPs—fix any spam or delay flags.
Enable 404 logging for .com traffic to alert of misdirects.

Step 4: Rollout/Communications

Prepare an FAQ for support, sales, and compliance (“Why .co? Here’s how we're de-risking and educating”).
Announce publicly at launch with transparency—don’t wait for confusion to force the conversation.

Playbook 2: Ongoing Assurance & Monitoring

Daily:

Email delivery, domain security, and phishing alerts monitoring.

Weekly:

Analytics review—session drop-offs, navigation to .com, form abandon due to domain disbelief.

Monthly:

Brand monitoring/search alerts; user feedback synthesis (“what are we hearing?”).
Check app stores and OAuth integrations for domain mismatch.

Quarterly:

Review industry moves—did peers switch TLDs? New rules from regulators or major partners?

Playbook 3: Competitor Risk & Comps Analysis

Step 1:

Build or buy a structured list of all fintech launches in your segment for the past 3 years.

Step 2:

Annotate: How many started on .co, .com, .io, or niche TLD? If .co, did they stick? When/why did they migrate?

Step 3:

Document “migration signals” (recurring funding round, expansion to enterprise, notable phishing or reputation incidents).

Step 4:

Use these comps during fundraising and when educating internal or partner teams.

Bonus:

For each comp, note SEO ranking effect, media coverage impact, and end-user confusion complaints.

Playbook 4: Domain Migration (“Graduation” to .com)

Step 1:

Secure .com via broker, Namiable, or direct negotiation; do not announce until secured and staged.

Step 2:

Configure staging with 301 redirects, dual-certificate SSL, and endpoint mirrors; beta test with top clients and partners.

Step 3:

Publish migration comms: visible on homepage, via email/SMS/user dashboards, app notifications, with instructional copy.
Run a week-long “redirect test”—do any users fall off or get misrouted?
Notify all app/partner APIs, update DigitalOcean/AWS/GCP’s domain settings.

Step 4:

Post-migration, track all metrics: traffic retention, SEO, conversion, user support tickets.

Unlock advanced playbooks and migration partners—Absolutely members get quarterly updates and fintech benchmarks at www.namiable.com.

Case Study (Sample)

Clear Example: Brex.co to Brex.com

Background: Fast-scaling corporate card startup Brex launched with brex.co. Initially, .com was owned by a legacy entity and not available.

Early-Stage Outome:

.co was not a visible hurdle for early-stage fundraising, PR, or customer acquisition.
Technical infrastructure anticipated eventual migration and monitored misdirected traffic warnings and user confusion.

Mid-Scale Pivot:

Post-Series B, as enterprise targets and regulatory/compliance needs surged, .com became both available (at a price) and necessary.
Migration involved a multi-month staged rollout, 301 redirects, marketing blitz, and customer/user education.

Lessons:

Launching on .co with a migration roadmap can be sound—provided you're transparent with stakeholders and invest in monitoring and corrective tactics.
The risk surface expands beyond Series B, where enterprise trust and IT gateway filtering increase.

Does Not Clear Example: Vault.co Hits Scale Friction

Background: Vault.co, a B2B payment automation fintech, staked their early brand on .co but kept .com out of reach.

Operational/Tested Challenges:

Encountered repeated deliverability issues with enterprise IT teams and Fortune-rated partners (“unfamiliar TLDs auto-spammed”).
High customer support volume for “lost invite” and “did you mean .com?” errors, especially in RFP-heavy buying cycles.
Investor conversations flagged the domain risk three funding cycles in a row, eventually conditioning a term sheet on .com acquisition.

Key Operational Lesson:

Even with a bulletproof product, your domain can become a bottleneck if your audience or market skews enterprise, conservative, or compliance-dependent. Proactive planning and readiness to migrate (plus messaging and technical preparation) is non-negotiable.

Explore a full database of fintech .co success and “hard lesson” stories, free on Absolutely or at www.namiable.com.

Metrics & Telemetry

Track these metrics to validate (and, if needed, correct) your .co domain strategy:

Domain-level Metrics

Direct Navigation Errors: % of sessions that arrive at “brand.com,” “brandco.com,” or known typo sites before reaching the intended .co, measured via web analytics (Google Analytics, Plausible) and DNS logs.
Email Deliverability Health: Delivery, open, and spam/junk filtering rates for transactional and marketing sends. Tools: Google Postmaster, Sendgrid, Postmark, or Sparkpost, with a focus on ISPs used by your audience.
Conversion Funnel Dropoff: Track at onboarding, password reset, and email login stages—flag abandonment due to domain confusion.
Support Volume: Number and % of support tickets referencing domain confusion, email issues, or typo checks.
Phishing Incidents: Number of user-reported phishing attempts or known lookalike/similar TLD threats. Tools: Brand24, AbnormalSec, PhishLabs.
Investor/BD Feedback: NPS or qualitative counts of domain-related objections or “asks” in fundraising and partnership cycles.
SEO Impact: Baseline and monitor search rankings—track indexed pages, lost backlinks on migration, and brand name prominence for both .co and .com across SERP.

Telemetry & Monitoring

Set up custom dashboards on Absolutely or common analytics stacks.
Configure lookalike domain alerts using Namiable’s monitoring suite and Google Alerts.
Weekly/Monthly Reporting: Share snapshot dashboards internally; escalate on any threshold-triggering deviation from baseline conversion or trust KPIs.

Catch red flags early with Absolutely telemetry—including domain, trust, and conversion health—and benchmark against the fintech elite at www.namiable.com.

Tools & Integrations

Make your .co operational stack enterprise-grade from day one:

Domain, DNS, and Security

Namiable.com: One-click buy, monitor, and defend. Secure your main and typo domains, monitor for lookalikes and phishing, access instant comps.
Cloudflare: Fast DNS propagation, DDoS protection, SSL bundling, always-on status.
EasyDMARC: Automated DMARC, SPF, DKIM setup with weekly reporting; simple for non-technical teams.
LetsEncrypt/ZeroSSL: Automated, free SSL for all web properties.

Email

Google Workspace: Proven business email, solid anti-phish/anti-spam, and solid for self-managed organizations.
Postmark: Transactional sends with advanced monitoring—shows precisely when/where an email gets blocked or bounced.
Sendgrid/SparkPost: High-volume, deliverability-tuned sending for notifications and marketing.

Monitoring

Google Analytics, Heap, Mixpanel: Setup events for domain-specific entry errors, abandoned user flows, cross-domain journeys.
Brand24/Mention: Social and press alerting for your brand in the wild—flag misuse or confusion.
AbnormalSec, Proofpoint: Advanced enterprise phishing and domain threat detection.

Collaboration & Ops

Slack & Notion: Use channels and docs for near-real-time support, feedback triage, incident reporting, and knowledge sharing.
Zapier: Trigger alerts for lost email, domain incidents, or survey follow-up from Google Sheets data.

Stack building made simple: browse recommended vendors and founder reviews—Absolutely and Namiable.com have deep fintech tool integrations for every stage.

Rollout Timeline

Use and adapt this sample timeline—don’t cut corners:

Weeks -4 to -3: Strategy & Acquisition

Internal audit: Apply 8-point Framework to your team’s launch plan.
Secure .co, potential typo/legacy domains through Namiable or a trusted broker.
Legal intake: Run clearance, trademark, and basic risk review.

Weeks -2 to -1: Technical and Messaging Readiness

Implement DNS, SSL, DDoS/proxy, DMARC/SPF/DKIM.
Conduct deliverability and “phish test” campaign.
Record core FAQ and support scripts—prep support/training content.

Week 0: Launch Week

Website/app live on .co
Major PR, investor, and customer mentions live (email, social, media).
Announce and reinforce domain clearly throughout onboarding, support, and conversion paths.

Weeks +1 to +4: Early Feedback and Correction Loop

Monitor KPIs: direct nav errors, user feedback, email bounces.
Issue surveys to earliest adopters for UX feedback.
Address surprises promptly via updates and proactive messaging.

Month 2+: Consolidation and Futureproofing

Review against peer launches and migration data points.
Begin tracking competitor moves—if similar-stage fintechs are pushed to migrate, prepare a plan.

Objections & FAQ

Surface every objection now, not post-launch. Here are nuanced, less-obvious questions (with best-practice answers):

“Will .co make us look less ‘serious’ or hurt conversion?”

For consumer/crypto/SMB fintechs, early conversion penalties are rare—user education (tooltips, FAQs, onboarding banners) squashes most initial friction.
Enterprise and regulated buyers present “institutional skepticism"—.com or well-defended .co, with added trust comms, is safer.
Split test your signup/onboarding with both TLDs if traffic is available.

“Our users are older or risk-averse—should we avoid .co?”

If your ideal customer profile skews 40+, compliance, or high-value—expect more domain confusion, verification calls, and trust inquiries.
Consider layered trust signals (badges, explanation banners, explicit URL reminders).

“Is migration away from .co always painful or expensive?”

With excellent 301s, planned comms, and 90+ days dual support, traffic/SEO suffers far less than feared.
Migration costs are mostly operational (update every asset/link, partner/press) but pale compared to revenue risk from trust drain.
Namiable can assist with migration sequencing and vendor mapping.

“Can spoofers easily exploit our .co?”

Yes—if .com or other similar TLDs are uncontrolled. Proactive lookalike acquisition, user education, and phishing alerting (plus DMARC-Google Postmaster monitoring) can mitigate.

“What about vertical TLDs like .pay or .finance?”

They carry higher risk of filter/spam flags, limited user familiarity, and some banking partners block them outright. Use for side marketing pages only, not canonicals.

“What’s the fastest, verifiable way to make a call?”

Use frameworks and checklists. Run validation/internal split tests. Or, start an Absolutely account for instant, market-backed domain audits or check www.namiable.com for brand fit reports.

Pitfalls to Avoid

Don’t let small mistakes compound.

“.co is enough” as a permanent solution: Short-term gains are not long-term safety if enterprise or global expansion is planned.
Neglecting lookalike registration/monitoring: Many phishing and lost conversion horror stories start with a missing .com or barebones defense of .co.
Omitting funnel telemetry: “Everything’s fine” hides lost conversion; measure direct nav errors, abandoned flows, and support queries about the domain.
Ignoring internal comms/logistics: Employee, contractor, and third-party confusion can sap morale and create brand inconsistency.
Changing TLDs mid-funnel: Staged migrations must be smooth and globally messaged; a poorly executed switch can halve launch momentum.
Not prepping partners/customers: Fatigue and confusion compound when users aren’t told how to update bookmarks, emails, or security settings.

Absolutely’s domain launch checklist and expert review (at www.namiable.com) will help you bypass these pitfalls.

Troubleshooting

Users Typing .com by Default?
- Place banners and “.co, not .com" reminders at every critical UX touchpoint.
- Where legally/technically feasible, acquire .com and auto-redirect or at least dead-end to avoid leaks/phishing.
- Monitor 404 logs for .com mistypes—automate daily/weekly review.
Transactional/Marketing Email Issues?
- Revalidate SPF/DKIM/DMARC; use deliverability tools to re-test.
- Add yourself (and test accounts) to recipient distribution for random audits.
- For heavy regulated/enterprise flows, consider custom onboarding with their IT.
Ongoing Partner or Investor Confusion?
- Bake a “domain bullet” into every pitch/support deck and contract—explain your current TLD, rationale, and future migration plans.
- Use Absolutely/Notion docs to keep everyone on the same page.
- When ready, tee up “domain migration” PR way in advance and deliver “Just the Facts” memos.
Phishing/Loss of Control?
- Layer multiple lookalike scans: Namiable, Google Alerts, Brand24. Alert your user base at once if there’s a new credible threat.
- Run quarterly red-teaming: have staff attempt “spoof” emails to catch holes in filters.

Still seeing unfixable confusion?
Try Absolutely’s domain troubleshooting service or full-stack founder coaching at www.namiable.com.

.co can be a smart, tactical launch choice in fintech—especially for consumer/SMB use cases and with disciplined education and monitoring.
Conversion, trust, and operational risk rise as you scale (especially in enterprise, high-stakes B2B, or regulated flows).
Always measure actual friction (not just vibes): lost support tickets, direct navigation errors, investor/partner feedback.
Migration to .com is common and smoother if planned for—do not leave this to chance or whim.
Lock down lookalikes, own user and stakeholder education, and reserve bandwidth for a future migration path.

For every brand or growth lead who wants to get domain decisions Absolutely right—benchmark, check, and secure your perfect name at www.namiable.com today.

Next Steps

Run a domain and funnel audit—apply the 8-point framework above, tailored for your specific segment and launch plans.
Benchmark against real-world fintech comps—use Absolutely or search www.namiable.com for exact success/failure matches.
Deploy measurement: Wire up direct navigation, funnel abandonment, and deliverability monitoring pre-launch.
Prepare a migration pathway, technical stack, and comms plan—even if .co is your hero TLD for now.
Secure your ideal .co, .com, or alternative TLD—before fundraising or next-phase expansion. Too many brands wait until it costs 10–100x more.

Absolutely—your fintech brand’s shortcut to rigorous decisions, powerful messaging, and launch with zero second-guessing. Get started free or browse the curated domain boards at www.namiable.com now.

.co in Fintech: Where It Clears and Where It Doesn’t (Comps)