Does the role renew every month?
Role payments are one-time. Optional timed passes require a ready expiry service; new timed setup is blocked while it is unavailable. Renewing requires another purchase.
Direct answer
To sell a Discord role, create the role and its channel permissions, place Cartcord above it, and connect the correct role to a product. Confirmed payment triggers an attempted grant. You can offer untimed access or an optional fixed-duration pass with automatic expiry. These passes use one-time payments: the buyer must purchase again to renew, and no automatic recurring charge is created.
How it works for paid role sellers
- 01
Invite the bot
Open the dashboard with Manage Server.
- 02
Publish the product
Review payment eligibility and configure the bot grants the role after paypal capture. a seller can choose untimed access or a fixed-duration pass..
- 03
Buyers use /buy
After payment verification, configured delivery is attempted.
Understand the operating cost
Choose by the actual product, audience and services you need. Cartcord's plans are Free $0, Basic $29.99, Pro $59.99 and Enterprise $129.99 per month. Cartcord charges no sales commission; PayPal processing and other merchant costs remain separate. A marketplace may provide discovery, billing, hosting or tax services that a flat Discord-store plan does not.
What a buyer would see
- VIP access role$49 · The bot grants the role after PayPal capture. A seller can choose untimed access or a fixed-duration pass.
- Supporter role$9.99 · The bot grants the role after PayPal capture. A seller can choose untimed access or a fixed-duration pass.
What /products shows
Interactive example. This preview does not create an order or charge a payment.
Members open the storefront, choose a product, and start checkout.
Design access before choosing a price
Create a dedicated paid role rather than reusing an administrator or moderator role. Identify exactly which channels, events or resources it unlocks and test those permissions with a non-staff member. Deny access through the default role where needed, then allow the paid role deliberately. A role color alone does not make a private community, and an unrelated broad permission may accidentally expose the same channels to everyone.
Keep the bot's role above the role it needs to grant. Discord's role hierarchy can prevent a grant even when the bot has Manage Roles. Use the hierarchy checker as a preparation aid, then verify the live guild configuration. Do not give a commercial product permission to manage your server merely to make delivery easier. The product should provide the smallest role that delivers the benefit you actually sell.
Choose untimed access or a timed pass
Untimed access has no configured automatic expiry. A timed pass records a duration in days from confirmed payment and schedules expiry. State that duration in the name or description, and show what the member receives during it. A seven-day pass is a single seven-day purchase. Calling it a weekly subscription would imply future billing and cancellation behavior that this checkout does not provide.
Configure duration while the product is hidden and active checkouts are finished. Existing paid orders keep their original duration snapshots, so a later edit should not shorten access already purchased. For passes longer than three days, the worker schedules a reminder three days before expiry. A reminder is a delivery attempt rather than a guarantee that Discord will accept the DM or that the customer will read it.
Test the complete member journey
Use a permitted test identity that does not already have the paid role. Open the store, select the offer, verify the displayed duration and complete the intended test flow. Inspect the paid order, role grant and private-channel access. Then exercise a failed-delivery path by checking what support sees when the bot cannot grant the role. A payment can succeed while a Discord permission or availability problem delays fulfillment.
Give buyers one recovery destination. Their purchase history should use the same Discord identity used at checkout; support should ask for an order ID instead of a screenshot of a payment email alone. Re-sending delivery retries the purchased access. It does not create a new payment, reset the original clock or turn an expired pass into a fresh term. Explain that distinction to staff before launch.
Preserve access that came from another source
A member may already have a role from a manual grant, a moderator decision or another valid purchase. Expiry and refund handling need to respect those origins. Cartcord records whether it added a role and checks other valid grants before removing access. A pre-existing role should not disappear simply because the member bought and later refunded a product that used the same role.
Overlapping purchases also need careful expectations. A second purchase does not automatically mean the first order's expiry timestamp is extended. Each pass has its own paid term, and another valid grant can preserve access when an older term ends. If you intend to sell a specific stacking or renewal rule, document and test that rule rather than inferring it from the role still being present.
Operate the membership as a real service
A private channel is only the delivery mechanism. Publish the schedule, moderation rules, response times and concrete content or activities included. If a live session moves or a resource becomes unavailable, communicate the resolution through the support channel you promised. Avoid an undefined premium community promise when the value depends on a creator's continuing time and availability. The payment system cannot supply the service for you.
Monitor failed grants, expiry retries and refund revocations. Keep the bot installed and its permissions intact; an expired pass cannot be removed from Discord while the bot cannot act. Review the durable job result before marking a support issue resolved. If automatic renewal, payment retries or a self-service billing portal is essential to your business, use a billing product that actually supports those capabilities until a seller recurring engine is available.
A launch checklist you can repeat
Start from a hidden product and review it as a buyer: name, current price, included deliverables, dependencies, access duration, license and support contact. Connect the seller payment account for the intended store and verify that the selected product can be published. Use a genuine preview of your work. Remove test data, private credentials and unlicensed material before adding the delivery destination.
Run an authorized checkout test with an identity that represents a buyer, then inspect both the payment result and fulfillment result. A browser return page is not evidence of a captured payment by itself. Exercise purchase recovery and a delivery retry. Before announcing the product, keep a record of the terms, the version being sold and the recovery instructions your staff will give a customer.
Compare the operating model, not just the headline fee
Manual ticket selling can suit occasional custom work, but staff must reconcile each payment and fulfill each promise. A percentage marketplace may include discovery, billing, tax or hosting services you would otherwise operate. Cartcord's flat server plan and direct seller PayPal checkout serve a different workflow. Calculate the cost of the features you actually need instead of treating every percentage or subscription as interchangeable.
Include payment processing, currency conversion, hosting, refunds and support time in the comparison. Cartcord taking zero sales commission does not remove those costs or make Cartcord the merchant of record. Check the current plan's limits and provider eligibility for your particular product. Choose the route that meets the buyer's delivery and recovery needs at the volume you can realistically support.
| Responsibility | Manual ticket workflow | Cartcord released workflow |
|---|---|---|
| Payment confirmation | Staff reconcile the correct merchant transaction | Provider confirmation is checked before configured delivery |
| Fulfillment | Staff send the resource or complete the promised service | Configured file, link, key or role delivery is attempted; manual work still needs staff |
| Recovery | Staff locate the purchase and determine what was delivered | Original-account purchase recovery and recorded delivery results help investigate failures |
| Cost | Account for processor charges, tools and staff time | Account for the store plan, processor charges, hosting and support |
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
Why would the role not be granted?
The bot must sit above that role in Server Settings. If it is below, move it up and re-send the order from the dashboard.
Can I still charge a monthly plan for Cartcord?
Yes. Your Cartcord subscription is separate. The buyer's payment for the role goes to your PayPal.
Which commands start the purchase?
/store, /products, and /buy.
Can I use a coupon?
Coupons, including a 100% free claim, are on Pro and Enterprise.