How to Handle Customer Support, Updates and Refund Requests for Trading Software

Last checked: 12 October 2026. This guide draws on the MetaTrader 5 Help pages on Market updates and activations, reports of MetaQuotes support-channel rules, and Paystack’s published chargeback fee as reported by a 2026 gateway review. Refund and consumer laws vary by country, so ask a lawyer about your own obligations.

Most of the work of selling software happens after the sale. Customers ask how to install it, a platform update breaks something and a few ask for their money back. Handled well, these moments produce loyal customers and good reviews. Handled badly, they produce chargebacks and public complaints. This guide covers support, updates and refunds for sellers of MT5 indicators and Expert Advisors.

Support: set expectations before the sale

Tell buyers, on the product page, what support means: where to ask, how fast you reply and what you will and will not help with. A promise like “reply within two working days” is realistic for a solo seller. A promise of 24-hour support is not, unless you have help.

It also helps to say what is outside support. Most sellers will not teach trading, tune a strategy for a customer or fix a broker’s data problems. Write that down so you can say no politely.

Where support happens

• On the MQL5 Market. A report on MetaQuotes’ description rules says support must be provided through product comments or the mql5.com messaging system, which supports group chats and channels, not through links to Telegram groups or other third-party messengers. Follow the current rules, because products can lose visibility if they do not.
• On your own site. Use an email address or a support form that creates a ticket. Chat apps are fast but hard to search later. Keep a record of each case.

Reduce support requests before they start

1. Write a clear installation guide with screenshots and common errors.
2. Build a short FAQ from the questions you actually receive.
3. Show helpful errors inside the tool, such as “symbol history not loaded, wait a few seconds”, instead of silent failure.
4. Print diagnostic information in the Experts log to make troubleshooting easier. Ask customers to send the log lines, not just a screenshot of the chart.
5. Make the version number visible in the tool, so you always know which version a customer runs.

A support reply routine

1. Acknowledge quickly, even if you need time to investigate.
2. Ask for specifics: terminal build, broker, symbol, timeframe, version and the exact message.
3. Reproduce the problem on your own setup if you can.
4. Reply with a clear fix or a clear explanation if it is not a bug.
5. Record the case, so patterns show up. If five people hit the same problem, fix the product or the documentation.

Stay calm and factual with frustrated customers. Many are anxious because money is involved. A courteous reply that solves the problem often turns an angry buyer into a recommender.

Updates

MetaTrader 5 builds change, brokers change symbol conventions and bugs appear. Plan for updates before you sell.

• On the Market. The help page says that to publish an updated version, you open the Version tab, choose New Version, upload the product file and describe what changed. Buyers see a message and an Update button when a new version is available.
• On your own site. Keep a changelog, tell customers by email and make downloads available in an account area or a link that does not expire.

Say in advance how long free updates last. “Free updates for the lifetime of version 1” is clearer than “lifetime updates”. If you release a major new version that is substantially different, you may charge for it, but be clear about the policy at the time of the original sale.

Always test an update on a demo account before release, and keep the previous version available in case the new one breaks something. A bad update to a tool that traders use in live markets can cost real money, and that damages your reputation.

Refunds

On the MQL5 Market. Sellers’ reports quote the service rules as stating that products purchased through the Market are non-refundable. That quote came from a forum post, not from the current rules page, so read the live rules yourself. If it is correct, it makes the pre-purchase demo and a clear product page more important, because buyers cannot undo a mistake.

On your own site. You set the policy, within the law. Consumer protection laws in many countries give buyers certain rights, and card networks and payment providers have dispute processes. A written policy might say:

• A refund window, such as 14 days from purchase.
• Conditions: the buyer has tried the tool, asked for support and the problem could not be solved.
• What is not covered: trading losses. A refund policy must not become a guarantee of profit, and you should say that trading losses are not grounds for refund.
• How to ask, and how long refunds take.

Be wary of two traps. A money-back guarantee that is too generous can be abused. One that is too hidden causes disputes.

Chargebacks

A chargeback happens when a customer asks their bank to reverse a payment. A 2026 review of Paystack reports a chargeback fee of 2,500 naira on Nigerian accounts, noting it appears in support documents rather than on the main pricing page. Fees and rules vary, so check your gateway. Chargebacks cost money and can harm your standing with the payment provider. To reduce them:

• Make the charge descriptor on the card statement recognisable, so buyers do not forget the purchase.
• Send clear receipts and delivery emails.
• Keep records of the sale, the delivery, support emails and the terms accepted.
• Offer easy refunds. A refund is cheaper than a dispute.

Handling abusive customers and public reviews

• Reply to public reviews once, politely, with facts and an offer to help. Do not argue.
• Never write or buy fake reviews. Platforms and regulators treat this as deceptive.
• If a customer is abusive, calmly restate your policy and stop engaging when it gets personal.

Metrics worth tracking

• Time to first reply.
• Percentage of sales that lead to support requests.
• Refund rate.
• Most common issues, to guide fixes.

What we could not confirm

• Whether the MQL5 Market currently refunds purchases in any circumstances. Read the live rules.
• Typical refund rates for MT5 tools. We found no published data.

Frequently asked questions

Should I give lifetime support? Define it. “Support for the current major version” is realistic.

What if a platform update breaks my product? Fix it quickly, tell customers what happened and release an update.

Key takeaways

Set support expectations before the sale, put help where the platform’s rules allow, reduce requests with documentation and clear error messages, define update and refund policies in advance and keep records.

Sources checked

• MetaTrader 5 Help, “How to Become a Seller” (new versions) and “How to Purchase an App”, metatrader5.com
• FX News Group, report on MetaQuotes Market description and support-channel rules
• MQL5.com forum, quotation of Market service rules on refunds (secondary source)
• learnwithhasan.com, Paystack payment gateway review (April 2026), for the chargeback fee