Do not index
Do not index
When you build an AI coaching clone on platforms like Personify, Delphi, Coachvox, Pickaxe, or BuddyPro, there's a critical legal question that most experts overlook: who is actually the merchant of record when a subscriber pays for access to your AI?
This isn't just about economics - it's about legal liability. The merchant of record is responsible for collecting sales tax and VAT, handling refunds and chargebacks, and maintaining compliance across multiple jurisdictions. Get this wrong, and you could face unexpected tax obligations or legal exposure.
Based on current platform documentation, four of the five major AI coaching platforms checked put the creator in the legal seller seat, while Delphi appears to be the outlier whose public terms describe a platform-controlled sale. However, "Stripe Connect built in" marketing language doesn't answer this question on its own - the devil is in the contractual details.
Platform Comparison: Who's the Legal Seller?
Platform | Legal Seller | Tax/VAT Responsibility | Refunds & Disputes | Documentation Quality |
Personify | Likely creator (payments to creator's Stripe) | Creator (undocumented) | Creator (undocumented) | Poor - key liability details missing |
Delphi | Likely Delphi (platform collects, pays creators) | Likely Delphi (terms mention sales tax) | Delphi controls (no prorated refunds) | Moderate - some gaps in public docs |
Coachvox | Creator (explicitly not party to customer agreement) | Creator (configures own Stripe tax settings) | Creator (manages in own Stripe dashboard) | Good - clear contractual language |
Pickaxe | Likely creator (connected Stripe account) | Creator (undocumented) | Creator (undocumented) | Poor - lacks explicit legal allocation |
BuddyPro | Creator (direct charges to expert's Stripe) | Creator (responsible for legal compliance) | Creator (sets own policies) | Good - explicit terms (effective Oct 10, 2026) |
The pattern is clear: most platforms position the creator as the legal seller, but the quality of public documentation varies dramatically from one to the next.
Why "Stripe Connect" Doesn't Answer the Question
Many platforms market "Stripe Connect integration" as if it automatically clarifies merchant-of-record status. It doesn't.
Stripe Connect is a technical framework that can be implemented in multiple ways. A platform might use direct charges (where your connected Stripe account is the merchant), destination charges (where the platform is the merchant but funds go to you), or separate charges with transfers (where both parties have different roles in the transaction).
The technical integration tells you nothing on its own about who bears legal responsibility for disputes, who must collect VAT in the EU, or whose refund policy governs the customer relationship. Those are contractual and regulatory questions, not technical ones.
Coachvox exemplifies clear documentation: its terms explicitly state it is "NOT a party to the agreement between you and the End User," even though payment flows through its Stripe Connect integration. The creator connects their own standard Stripe account, manages subscriptions in their own dashboard, and configures their own tax settings. Coachvox's public monetization page states Coachvox takes 10% per transaction on top of Stripe's processing fees.
Personify operates on a similar creator-Stripe model: payments go straight to the creator's own Stripe account per Personify's pricing page (checked 2026-10-05), and the creator sets the price and owns the revenue. Its Agency plan lets agencies place their own support, terms, and privacy links on the customer experience, which implies the agency or creator - not Personify - maintains the primary customer relationship. But Personify's own marketing-site terms explicitly state they do not govern the actual application, and the real app terms at app.personify.fyi were not retrievable as public text during this research. That leaves chargeback handling, VAT responsibility, and the actual refund policy undocumented in anything publicly accessible.
Pickaxe follows a comparable pattern: builders connect their own Stripe account and submit their own business and identity information directly to Stripe, and Pickaxe takes an 8% or 10% processing fee depending on plan. Unlike Coachvox, Pickaxe does not publish the explicit "not a party to the agreement" language, and its own refund policy covers refunds for a builder's purchases of Pickaxe plans or credits - not refunds a builder may owe to their own subscribers. That gap matters: Pickaxe's public terms simply don't address who owns the refund obligation when a builder's customer wants their money back.
Delphi takes the opposite approach. Its customer terms indicate Delphi collects payment through its own payment processor, controls recurring billing, and sets a no-prorated-refund policy. Creators receive "Creator Payments" under a Statement of Work and must submit tax documents like a W-9 - consistent with Delphi collecting revenue first, then paying creators afterward. Current public pricing places Delphi's monetization on its custom-priced "Immortal" tier with no published revenue-share percentage; an older figure is no longer current and shouldn't be treated as today's terms.
What to Verify Before You Sign
Don't rely on marketing language or verbal assurances. Request these documents from any platform you're considering:
- The actual creator agreement - not just the marketing-site terms of service, but the contract that governs your relationship with the platform once you're monetizing.
- A sample customer receipt - what name appears on the credit card statement? This often reveals the true merchant of record.
- Stripe Connect implementation details - specifically, what charge type does the platform use (direct, destination, or separate charges), and which Stripe account legally bears dispute liability?
- A tax and compliance matrix - who collects sales tax in US states where you have nexus? Who handles VAT registration and remittance in the EU? Who bears the cost of tax compliance software?
- Dispute and chargeback procedures - who receives the chargeback notification? Who must provide evidence to Stripe? Who absorbs the chargeback fee and any disputed amount?
The platforms with clearer documentation make this verification easier. BuddyPro's newly published terms (effective October 10, 2026) explicitly state that all payments are collected directly by the expert, the platform is not a payment intermediary, and the expert is responsible for invoicing and legal compliance. That conclusion is backed by its own Stripe and API documentation, which describes experts connecting their Stripe account via OAuth with end-user checkouts created as direct charges on the expert's own connected account - meaning the expert's Stripe account, not the platform's, is the merchant account that actually receives the transaction. Coachvox similarly clarifies that creators manage their own customer relationships through their connected Stripe accounts.
For platforms with sparser public documentation, like Personify and Pickaxe, you'll need to dig deeper during the evaluation process and ask the questions above directly, in writing.
The Stakes for Established Experts
If you're already running a six-figure coaching business, merchant-of-record status isn't academic. You likely have sales tax obligations in multiple US states, potential VAT exposure in international markets, and existing relationships with tax professionals who need to understand your revenue streams.
Taking on merchant-of-record responsibility for a new AI product means expanding your compliance footprint. You'll need to track AI subscription revenue separately, potentially register for VAT in new jurisdictions if you attract international subscribers, and confirm your existing sales tax setup can handle the new revenue stream. An expert with subscribers spread across several EU countries, for instance, needs to track VAT registration thresholds separately for each country as the AI subscription adds to existing revenue. In the US, economic nexus thresholds that trigger sales-tax collection obligations vary by state, so a merchant-of-record creator selling nationally needs a clear picture of where those thresholds sit before scaling subscriber count.
Conversely, if a platform does act as merchant of record for part of the transaction, it should be handling some of these obligations - but you'll still want written confirmation of exactly what it covers and what remains your responsibility.
The business model also affects your relationship with subscribers. When you're the legal seller, you control the refund policy, own the customer relationship, and can make exceptions for special circumstances. When a platform is closer to merchant of record, as Delphi's public terms suggest, you're typically bound by its policies and procedures instead.
This merchant-of-record question intersects with other due diligence areas, like payout schedules and cancellation and refund policies. The platform that controls the sale usually controls the timing and terms of payouts to creators too, so the two questions are worth researching together rather than separately.
The key takeaway: most AI coaching platforms are positioning themselves as technology providers, not merchants. They're building tools for you to sell your own digital product, with all the legal responsibilities that come with being the seller. Plan accordingly, and get the specific liability allocation in writing before you launch.
Related reading
Written by