Does Cartcord take a percentage of sales?
No. Cartcord charges a flat server plan and 0% of the order. PayPal's processing fee still applies.
Cartcord versus SellAuth
Both SellAuth and Cartcord publish zero platform sales-commission models. SellAuth advertises broader payment methods and plan-dependent recurring/affiliate features; Cartcord focuses on Discord-authorized workspaces and one-time seller PayPal checkout. Compare current limits and capabilities instead of assuming one avoids a percentage the other charges.
| Area | Cartcord | SellAuth |
|---|---|---|
| Sales commission | Zero Cartcord sales commission; separate flat store plan | SellAuth also publishes zero transaction fees; payment costs still need review |
| Store workflow | Discord-authorized workspaces, product commands and public storefronts | Broader storefront features and multiple payment methods are advertised |
| Recurring products | Not released for buyer payments | Recurring subscriptions are listed on eligible SellAuth plans |
| Affiliate accounting | Pro+ opt-in coupon rewards; no cash balances or payouts | Affiliate features are listed on eligible SellAuth plans |
| Migration scope | Hidden product drafts; fulfillment is configured separately | Review current export access and retain original buyer/order records |
Acknowledge the features both products offer
SellAuth's published pricing advertises zero transaction fees and multiple payment methods. It would be inaccurate to describe every SellAuth sale as carrying an additional platform percentage that Cartcord alone avoids. Compare the actual plan, product allowance, processor costs and features you will use. Check the provider's current page because monthly, annual and promotional presentations can differ.
Cartcord's distinctive workflow is its Discord-oriented seller workspace and product commands, with direct seller PayPal checkout and eligible purchase recovery. That does not make it a complete replacement for SellAuth's published recurring subscriptions, affiliates, custom domains or other capabilities. The legacy URL also serves people searching for a Sellpass replacement; it should not be read as confirmation that every historical provider or export remains available.
Evaluate the kind of store you operate
A community selling a few maintained products may value the ability to manage the store from existing Discord permissions and explain purchases through familiar commands. A business requiring many payment methods, a separate website brand, affiliates or recurring customer agreements may need a different set of tools. Write down those requirements before comparing a headline price.
Within Cartcord, distinguish a stocked key from an enforced software license. The optional verification API needs application integration. Distinguish a file archive from a bundle of separately fulfilled products. Distinguish a manual service preset from automated provisioning. These details determine whether the buyer receives what the listing promises, regardless of which storefront appears less expensive.
Audit the migration boundary
Start with a product export you are authorized to use. Cartcord can validate a CSV and save hidden drafts; it does not import previous orders, private delivery assets, credentials or subscriptions. Preserve the original records and confirm a way to support historical buyers. Configure each new product's delivery destination, stock, price and permitted-use terms before publication.
Test an eligible purchase and recovery path before moving traffic. Confirm which system owns each order and which provider handles a refund. Do not ask a previous buyer to purchase again to recover an entitlement the old store still owes. If the destination lacks a capability the existing business relies on, keep that part of the current workflow until a tested replacement is available.
Turn a feature checklist into acceptance criteria
For each feature on your shortlist, write the action a buyer or operator must complete. Instead of recording only 'licenses', specify whether the product needs a delivered key, a signed verification response, activation limits or a refund revocation check inside an application. Instead of 'affiliates', specify attribution, eligibility, reward type and how a refund affects the reward. This exposes differences between similarly named features before a store commits to a migration. It also prevents a large plan table from hiding the one missing capability that matters.
Cartcord's released creator referrals issue configured single-use coupon rewards for eligible verified purchases. They do not send cash commissions or create a withdrawable payout balance. A merchant requiring cash affiliate settlement must include that requirement explicitly when reviewing SellAuth or another provider. Likewise, buyer recurring billing, seller Stripe checkout and direct game-command delivery are not released Cartcord capabilities. Use the current operating guides to judge what can actually be enabled, rather than treating a future development item as part of the purchase.
Inspect stock, delivery and application integration
Stock means different things for different goods. A finite key pool needs a unique unused value for each fulfilled order; a link can be reused; a manual service may have a limited capacity unrelated to file count. Check how your existing catalog expresses those differences. Reconfigure the destination product deliberately and verify the advertised quantity before publishing. Do not import confidential keys into a public description or assume a CSV's delivery label contains the private fulfillment configuration.
For software, decide where entitlement enforcement belongs. Delivering a key records a purchase, while an application integration must check the verification response and handle its own failure policy. For protected files, decide which access controls the host provides and what happens after the buyer downloads a copy. Cartcord's optional vault links have specific use and network limits; they are not a promise that a file becomes impossible to copy. These operational details usually matter more to buyer satisfaction than a generic claim of secure delivery.
Keep a migration ledger for the first sales
Record each source product, new draft, delivery setup and publication decision in a private ledger. Mark products that depend on unavailable payment methods, recurring agreements or unsupported provisioning. Keep them hidden until there is a tested solution. Preserve the source platform's order exports and support records with appropriate access controls. The public Sellpass search term does not establish that every historical export format or account operation still exists; confirm the actual source you control before planning an automated transfer.
After a small release, reconcile successful orders against delivered items and the seller's payment records. Investigate failed delivery through the original order rather than issuing an unrelated replacement sale. Check how coupons, stock and product changes affect the next purchase. Assign a person to historical refunds so buyers are not passed between storefronts. A completed migration means the team can support both old and new obligations with clear records. It is more than a successful CSV upload or a new checkout link in the server announcement.
Sources and comparison assumptions
Checked on October 24, 2026. Plans, eligibility and fees can change. Compare your actual payment method, order count, taxes, hosting and support requirements. Cartcord's zero sales commission does not remove processor costs or make Cartcord the merchant of record.
Compare your monthly cost scenarios
Enter your actual fees. These are editable USD scenarios, not provider quotes. Include processor charges in both scenarios. Compare equivalent services and permitted products; required platform checkout still applies.
Enter every fee, including zero where applicable. Use non-negative amounts, whole orders and percentages up to 100.
Taxes, refunds, disputes, conversion, payout and support costs need separate review. Cartcord sales commission is 0%; the store plan and processor costs remain.
Questions
Who receives the buyer's payment?
The seller's own PayPal account. Cartcord does not hold the funds.
Which commands do buyers use?
Only /store, /products, and /buy.
Are paid roles a subscription?
Role payments are one-time. Optional timed passes require a ready expiry service; new timed setup is blocked while it is unavailable. Recurring buyer billing is not released.
How should I choose a plan?
Choose by your actual product count, order volume and required features. Review the current pricing table and include payment processing and support costs in the comparison.