AISTIM / MT4 · MT5

MT4 / MT5 source-code delivery and acceptance guide

Understand EX4, EX5, MQ4 and MQ5 files and check delivered source files, compilation, parameters and agreed behavior.

Decompiler service: pricing, payment and delivery

These terms apply to MT4 / MT5 indicator and EA cracking services. Quotes are per single indicator or single EA. The final total is agreed before work begins.

Reference prices · USD

One indicatorUSD 80–200
One EAUSD 200–500

Indicators: USD 80–200 each. EAs: USD 200–500 each. These are reference ranges; the final quote depends on the file and agreed deliverables. Ready-made product prices do not apply to decompiler work.

Payment methods

We accept Alipay, PayPal and USDT. USDT is supported on TRC-20 and ERC-20; agree any other network in advance. Contact us to confirm payment details, network and amount. Project payments follow your quote; the website support link is for voluntary support.

The deposit counts toward your total

A USD 10–50 commitment deposit is required to begin cooperation, confirm the project and reserve work time, protecting both parties’ investment. It is part of the agreed total, not an additional fee.

Deposit + remaining balance = agreed total

Example: total USD 150, deposit USD 20, remaining balance USD 130.

Refunds and cancellation

If AISTIM cannot complete the agreed cracking work and delivery, the deposit is refunded in full. If the project cannot continue for reasons attributable to the customer, including customer cancellation, the paid deposit is non-refundable.

Delivery time

Delivery is normally within 10 hours and no later than 48 hours. Elapsed hours start once the required files and information are complete, the scope is confirmed and the deposit is received. A verification build is supplied first; source code follows customer approval and receipt of the balance. Time awaiting customer verification or payment is excluded from production time.

Verify first, pay the balance, then receive source code

We first supply an EX4 or EX5 verification build containing AISTIM shop advertising so you can compare it with the original program. This modified build also demonstrates that we have recovered the source code and can change its content. Once you confirm it is correct and pay the remaining balance, we deliver the complete MQ4 or MQ5 source code.

Contact us to confirm your quote

Choose a service

For MQ4 / MQ5 source code, visit the decompiler section. For ready-made trading tools, browse MT4 / MT5 products. For new functionality, provide your development requirements.

Prepare your request

Specify MT4 or MT5, indicator or EA, terminal version, environment and the result you need. Prepare EX4 / EX5 files for decompiler enquiries, or a function and parameter specification for development.

Scope and acceptance

Agree on scope, quotation and deliverables before work starts. Check compilation, installation, indicator display or EA behavior against the agreed requirements, and record any issues to resolve.

Platforms and editions

MT4 and MT5 products use their respective platform files. Installation paths, dependencies and parameters follow the product page and delivery instructions. Screenshots show interfaces or demonstrations, not proof of returns.

How to check delivered MQ4 / MQ5 files

01

Check the delivery list

Check MQ4 / MQ5 source files, required dependencies, installation notes and parameter information against the agreed list. Whether compiled EX4 / EX5 files are included depends on the confirmed scope.

02

Confirm the platform and file type

MT4 uses MQ4 source and EX4 executable files; MT5 uses MQ5 source and EX5 executable files. MQ files contain source for reading and compilation; EX files run in the terminal. Renaming the extension does not convert platforms.

03

Check compilation and installation

Open the source in the matching MT4 or MT5 MetaEditor, follow the delivery instructions and review compilation output. Place files in the appropriate Indicators or Experts folder and refresh Navigator. Follow the product instructions for dependencies and exact paths.

04

Compare functions under matching conditions

Record terminal build, symbol, timeframe, inputs and test period; use matching conditions when comparing the original program. Check indicator displays and alerts, or EA orders and logs within the agreed scope. Start in a demo or test environment; screenshots are not proof of returns.

05

Report a reproducible issue

Include product, platform build, steps, expected behavior and actual behavior, with relevant error messages or screenshots. Logs can help locate the issue. Remove account details, passwords and other private information before sending them.

Acceptance follows the functions and delivery scope agreed in advance.

Related pages

Public product information

The JSON directories below contain public product names, platforms, descriptions and links to their original detail pages. Confirm the final edition, price and delivery terms with us.