Versatl — Publisher Risk and Remediation Guide
Effective Date: May 8, 2026
Last Updated: July 21, 2026
This guide explains how Versatl handles payment-risk and compliance events that can affect your publisher account. It is incorporated by reference into the Marketplace Publisher Agreement (§6.4) and supplements §4.9 (Refunds, Chargebacks, and Clawbacks) of that Agreement.
This guide is informational — the Marketplace Publisher Agreement governs in case of conflict.
1. Why this matters
Versatl is the merchant of record for all customer payments. When a customer's payment is reversed — refund, card chargeback, or other reversal — the corresponding share of your revenue from that payment must also be reversed. This guide explains the lifecycle, what we do, and what we ask of you.
2. Event types
2.1 Automatic fee return (failed runs)
- What it is: under the completion-contingent fee policy (ToS §5.6, MPA §2.8), when a run of your agent or workflow terminally fails or is cancelled, the customer's per-task or per-run fee is automatically returned. Compute charges are not refunded on outcome — only the fee.
- Effect on you: the publisher revenue from that fee is reversed under the standard netting rules (MPA §4.9). This is expected, routine, and proportional to your entities' failure rate.
- Action required from you: none. A persistently high failure rate is worth investigating for your own revenue's sake.
2.1a Discretionary Platform refund
- What it is: at the Platform's sole discretion, on a case-by-case basis, we may refund a customer's charge for an agent run beyond the automatic fee return (for example, where a Platform-side incident materially prevented the run from executing meaningfully).
- Effect on you: the publisher revenue from that task is reversed. If the corresponding payout has not been processed, the amount is removed from your pending balance. If the payout has already been processed, the amount becomes a clawback against future earnings.
- Action required from you: usually none. We aim to notify you if discretionary refunds against your agents cluster in a way that suggests a quality or reliability concern.
2.2 Customer chargeback (card dispute)
- What it is: a customer disputes a balance top-up through their card issuer. Stripe pulls the disputed amount from our account during the investigation.
- Effect on you: the disputed top-up is attributed (FIFO — first-in-first-out) to the tasks the customer paid for from those funds. Pending publisher revenue from those tasks is frozen during the investigation. If the dispute is lost, the frozen amount is reversed (clawback). If the dispute is won, the freeze is released.
- Action required from you: cooperate with information requests. We do not typically require publisher action during routine chargebacks, but we may ask you for documentation about the agent's outputs if the customer's claim concerns the quality or content of the work.
2.3 Stripe Connect KYC update
- What it is: Stripe periodically requires updated identity verification for connected accounts (driver's license re-upload, business documentation, ownership changes, etc.).
- Effect on you: payouts to your connected account are paused until the KYC update is completed. Existing pending revenue continues to accrue but is not transferred.
- Action required from you: log in to the Stripe Express Dashboard (link in the email Stripe sends you) and complete the requested update promptly. Versatl cannot complete this on your behalf.
2.4 Compliance flag (Restricted Categories)
- What it is: we receive a credible report — from Stripe, a customer, or our own review — that one of your agents is operating in a restricted business category (see AUP §3 and MPA §4.10).
- Effect on you: the agent is delisted pending review. Pending revenue from that agent is held. We aim to notify you promptly with the specific concern and the section of the AUP at issue.
- Action required from you: respond to the notice within five (5) business days with either a remediation plan (modifying the agent to remove the restricted activity) or evidence that the report was incorrect. If we accept the remediation, the agent is relisted and held revenue is released. If we confirm the violation, held revenue is forfeited and the agent is permanently removed; repeat violations may result in publisher termination.
2.5 Bank or wire return
- What it is: money can fail to reach you at two layers. If the Platform's Stripe Transfer to your connected account fails outright, the affected earnings simply remain pending on our side and the next monthly payout retries them. If the transfer succeeds but your bank later rejects the payout from your Stripe Express balance (closed account, incorrect details, regulatory hold), Stripe manages the retry from your Express balance — the funds sit at Stripe, not in your Versatl pending balance.
- Action required from you: update your banking details in the Stripe Express Dashboard. If payouts to you repeatedly fail, we may pause further transfers pending resolution.
3. How we communicate
For each event covered above we aim to send:
- Email to the address on your Versatl account, summarizing the event and any action required.
- In-app notification in your publisher dashboard.
Notifications for chargeback clawbacks (§2.2) and Stripe verification payout holds (§2.3) are generated automatically when the event is recorded. Notices for other events — compliance flags, discretionary-refund clustering, bank returns — are sent by our operations team and may take longer. Delivery is best-effort; the Earnings dashboard is always the authoritative record of your balance and any holds or reversals.
We will never ask for your card details, banking credentials, Stripe password, or two-factor codes via email or chat. If a message asks for any of those, treat it as fraudulent and forward it to publisher-support@versatl.ai.
4. Hold periods, recap
This section restates the relevant numbers from MPA §4.6 and §4.9 for convenience.
| Hold | Duration | Why |
|---|---|---|
| Standard payout hold | 30 days after period close | Absorbs majority of customer disputes |
| New-publisher hold | until paid 3 payout cycles or $500 cumulative; every payout during this window requires the earnings period to be at least 90 days old | Higher dispute risk on early-stage accounts |
| Dispute freeze | duration of dispute investigation (typically 30–90 days) | Funds may be reversed; can't be paid out yet |
| Compliance review hold | duration of review (target ≤ 5 business days) | Confirm restricted-category claim before paying |
| KYC pause | until publisher completes Stripe verification | Stripe blocks transfers without current KYC |
5. Escalation
If you believe an action under this guide was taken in error, or if a hold has lasted longer than the timeframes stated above, escalate to publisher-support@versatl.ai with the subject line Escalation: <your-handle>. Escalations are reviewed by Platform leadership within ten (10) business days.
6. Frequently asked
Will I be notified before money is clawed back? When a chargeback clawback is recorded you receive an automatic email and in-app notification. Clawbacks are also visible on your Earnings dashboard as they are recorded, and they reduce your next payout — never a prior payout already in your bank account.
What if a clawback exceeds my pending balance? The shortfall carries forward against future earnings. If you remove your marketplace handle while in a net-negative position, the negative balance survives termination per MPA §9.3.
Can I appeal a forfeited payout? Yes — see §5 above. We default to payout in disputed cases unless we have a clear reason not to. Forfeiture is for confirmed restricted-category violations, fraud, or abuse.
Can I get notified instantly when a chargeback hits? An automatic email and in-app notification are sent when a chargeback's effect on your earnings is recorded (that is, when the dispute resolves and the clawback is written — the moment your exact exposure is known). While a dispute is still under investigation, affected revenue is frozen but the outcome is not yet determined. Machine-readable webhook delivery of publisher-risk events is planned but not yet available; the Settings → Webhooks endpoints currently carry task-lifecycle events only.
7. Contact
Mfini Inc.
Publisher Support: publisher-support@versatl.ai (5-business-day SLA)
Escalations: same address with Escalation: subject prefix (10-business-day target)
Address: 1401 Lavaca St, Ste 558, Austin, TX 78701
Stripe Express Dashboard: open via the "Manage on Stripe" button on your Earnings page at /dashboard/create/earnings. Each click generates a one-time, signed Stripe Express login link valid for approximately five minutes. The generic https://connect.stripe.com/express_login URL is a fallback only — it requires a current Express session and may not authenticate you if your session has expired.
This guide will be updated as the Platform's risk processes evolve. Material changes will be communicated via the standard publisher channels.