How we work and what you receive
Every project runs in four stages. Each stage ends with something you can read or run, and the next stage starts only after you approve it. We turn rules you have written into software; we do not suggest the rules.
The four stages, and what you receive at each
-
1
Discovery
We go through the exchange or broker you use, the markets involved, the rules you have written and your risk limits. We also read the platform's API documentation and terms, so technical limits are clear from the start.
You receiveScope document -
2
Proposal and plan
The scope becomes a written proposal with work items, delivery dates and cost. Development starts once you approve it. Fees depend on scope and effort, not on trading volume or results.
You receiveWritten proposal and project plan -
3
Development and testing
Development runs in milestones, each ending with a working version. Where the platform offers a testnet, work happens there first. Trading software is tested on historical data, then in a paper trading account with live market data.
You receiveWorking versions and a test report -
4
Go-live
The software goes live gradually, with small limits, once testing is complete and you approve. In the initial period we watch its technical operation, not your positions or decisions. Maintenance covers the software and API compatibility, not strategy changes or position monitoring.
You receiveLive system and documentation
What we need from you
The platform and your country
Which exchange or broker you use, and where you are based. Which platforms can be used depends on the law of your country and the platform's terms.
Written rules or a written need
For trading software, your entry, exit and risk rules in writing. For an integration, what the software should read and do. We check that rules are precise enough to code and test; we do not choose them.
Your own account and API key
You create the key on your own account, with read and trade permissions only. We do not ask for withdrawal rights. See how API keys are handled.
A place to run it
By default the software runs on your own server or cloud account.
Someone who can approve
Each stage waits for your approval, so we need a person who can read the output and run the acceptance checks with us.
How acceptance testing works
Acceptance checks describe how the software behaves. They never describe profit: a return, a win rate or a backtest result is not an acceptance criterion.
- 1
Agree the checks
The scope document says what the software should do in each case you care about.
- 2
Run the tests
On a testnet where available, or in a paper trading account. Failure cases are simulated on purpose.
- 3
Read the report
The test report lists each scenario and how the software behaved.
- 4
Approve, then start small
You review the result. The switch to a live account comes only after that, with small limits.
Failure cases a test report covers
Which cases apply depends on the project. These come from our TradingView bridge example scenario and the integration scope on the exchange API page. The sample documents show a scope document, a proposal and a test report in full; the test report is filled in from a real run of Fincode's published order gateway reference code.
The same alert arrives four times
One order only. Each alert ID is processed once.
The exchange returns a server error
The order status is checked and reported instead of being assumed.
An alert arrives late
It is rejected and logged, past the threshold you set.
A message is invalid
It is rejected and logged with the reason.
A quantity is too large
The risk limit blocks the order before it reaches the exchange.
A connection drops or a rate limit is hit
The software reconnects or waits and retries, and the event is logged.
What we do not do
Fincode is a software company and does not provide investment advice, portfolio management or crypto asset services. Ready-made strategies, signals or trade recommendations, copy trading, management of customer accounts and profit sharing are not offered.
We decline projects that run on other people's accounts, copy trades or sell signals. Bridges take your own alerts only; paid third-party signal feeds are not connected.
Tests show how the software behaves, not future results. Trades can lose money.
Questions about how we work
Do I need to share my rules before you reply?
No. Your first message only needs the platform, what the software should do and your timeline. Written rules come in during discovery, because the scope depends on them.
Can you help me choose my rules?
No. Fincode does not recommend strategies; strategy and investment decisions are yours. If you have written rules, we can check that they are precise enough to code and test.
Will you run the software for me?
No. By default it runs on your own server or cloud account. Orders are sent by the software, on your own account, with your own API key, under the rules you defined.
Does passing acceptance mean the software will make money?
No. Acceptance shows that the software behaves as agreed. Tests show how the software behaves, not future results, and trades can lose money.
How is the cost set?
You see the work items, dates and cost in the written proposal, before development starts. Fees depend on scope and effort, not on trading volume or results.
What happens after go-live?
Maintenance covers the software and API compatibility, not strategy changes or position monitoring. Outages caused by the exchange, the server or the connection cannot be ruled out entirely, which is why monitoring and an emergency stop are put in place.
Send a short brief
Tell us the platform you use, what the software should do and your timeline. You do not need to share your rules yet. Fincode is a software company and does not provide investment advice, portfolio management or crypto asset services.