Use cases by buyer, and what to answer first
This page covers five kinds of buyer. Find yours to see what it usually needs, which service page fits, an example scenario where one exists, and the questions worth answering before you contact Fincode or anyone else.
Which of these are you?
The services page lists what Fincode builds. This page starts from your situation. Its questions are useful even if you hire someone else: give every vendor the same answers, and their quotes become comparable.
Fintech product team
You want exchange, broker or market data inside your own product. Matching service: exchange API integration.
Software agency
A client wants exchange connectivity or a trading module, and you cannot staff it. Matching service: work for agencies.
Company trading its own account
Treasury or a trading desk wants internal tools connected to a broker or exchange, on the company's own accounts only. Matching service: exchange API integration.
Individual with written rules
You have written entry, exit and risk rules for your own account and want them to run as software. Matching service: trading bot development, or code review if you already have a bot.
Finance team needing read-only reporting
You need balances, fills and transfers from several company accounts in one reconciled report, with no orders. Matching service: exchange API integration, scoped to read-only access.
These are typical needs, not a client list. Fincode has no client references yet. Apart from Fiva, Fincode's own product, every page under Projects is an example scenario, not a real client project.
Fintech product team
What you usually need: a tested connector for market data, balances or orders behind your own interface, with rate-limit handling, retries, logs and documentation. You may first want a feasibility review: which data can be licensed, what the APIs allow and what a first version should leave out.
Answer these before you contact anyone
- Does the product only read data, or does it send orders? On whose accounts?
- Which platforms and markets come first, and in which countries are your users?
- Do that platform's API terms allow your commercial use? Some agreements restrict commercial, SaaS or third-party use without written approval.
- Does your data license let you show the data to your users or pass it on? Display, machine use and redistribution are often licensed separately.
- Who holds your users' API keys, and where are they stored?
- Who keeps the connector working when a platform changes its API, and who on your side approves each stage?
Where to go next
- Matching service
- Exchange API integration. For Turkish coverage, Turkish exchange connectors. For a review before you build, project and product analysis.
- Example scenario, not a client project
- Read-only crypto portfolio risk dashboard: example scenario. It is written for an individual investor, and it shows connectors, key permission checks and reconciliation.
- Fincode's own product
- The Fiva case study shows market and fund data work in a real app. Fiva places no trades, so it says nothing about order handling.
- What to check first
- The platform's API terms and your own licensing position. If your product would place orders for other people, that can bring licensing duties and can fall under the work Fincode declines, so settle it with your lawyer and raise it in your brief before scope is agreed.
Software agency
What you usually need: an exchange connector, a rule-based trading module or a review of trading code you inherited, taken on as subcontract work with a written scope, a test report and documentation a developer on your side can read.
Answer these before you contact anyone
- Exactly which part are you handing over, and what does it connect to in your client's system?
- Who is the end client, in which country, and is it a crypto asset service provider? Other rules can apply to outsourced work.
- Who holds the trading account, and who wrote the rules?
- Does your contract with your client allow a subcontractor, and what has to flow down to one?
- Who talks to the end client, whose name goes on the deliverables and who receives the code? Raise these in your brief; what we agree goes in writing.
- Who on your side reviews the code and approves each stage?
Where to go next
- Matching service
- Work for agencies.
- Example scenario, not a client project
- No scenario covers subcontracting itself. The closest is Multi-exchange crypto arbitrage monitoring: example scenario, for connector work behind one common format.
- What to check first
- The conditions that pass through to your client: their own rules, their own account, and no signals, copy trading, other people's accounts or profit sharing. Check them against your client's plans before you promise anything.
Company trading its own account
What you usually need: software that connects treasury or risk screens to a broker or exchange API, with order handling, positions, limits, an audit trail and end-of-day reconciliation. If written rules should run unattended, you also need rule-based trading software on the company's own account.
Answer these before you contact anyone
- Is every account the company's own? Client or third-party money changes the legal picture, and we decline projects that run on other people's accounts.
- Which broker or exchange do you use, and does its contract give you API access for this use?
- What does the software decide, and what stays with a person? If rules decide, are they written down?
- Who may send, change or cancel an order, and who can stop everything?
- Which limits must run outside the trading logic, such as maximum position size or a daily loss limit? You set the numbers.
- What has to reconcile against the broker's records and when, and which records must you keep for audit?
Where to go next
- Matching service
- Exchange API integration for internal order handling and monitoring. Trading bot development for written rules.
- Example scenario, not a client project
- Broker API order management integration: example scenario. It follows a company's treasury team trading for its own account.
- What to check first
- API access and data rights: your contract with the broker or exchange decides both. On Borsa Istanbul, for example, a client cannot send orders to the exchange without using a member's systems. API access comes from a brokerage licensed by the Capital Markets Board (SPK) under its own contract, and automated use of market data needs an agreement signed directly with the exchange. See Borsa Istanbul market data.
Individual with written rules
What you usually need: software that runs your entry, exit and risk rules on your own account and server, with risk limits, an emergency stop, logs and alerts, tested on historical data and in a paper trading account before a small live start. Fincode does not suggest the rules. If you already have a bot, a written review may be all you need.
Answer these before you contact anyone
- Are your rules precise enough that two developers would build the same thing? The samples show the level of detail a scope needs.
- Does a subscription tool already do this? If one supports your exchange and your rules, use it: it will usually cost less than custom software. See crypto trading bot pricing.
- Do your platform's terms and your country's law allow this use?
- What are your limits: maximum position size, daily loss limit, and when should the software stop? You set the numbers.
- Where will the software run, and who deals with it when the server or connection fails?
- Can you accept that tests show how the software behaves, not future results, and that trades can lose money?
If your rules fire from TradingView alerts
Read TradingView's Terms of Use (opens in a new tab) first. As read on 5 November 2026, they license alerts and webhooks for display use and prohibit automated trading use, including through third-party products, and they say this applies to users and third-party providers alike. Take legal advice before you rely on this route. Software that reads market data directly from an exchange API does not use TradingView alerts at all.
Where to go next
- Matching service
- Trading bot development. If you already have code, trading bot code review.
- Example scenario, not a client project
- BIST strategy backtesting platform: example scenario. It is written for a research team, and it is the closest example of testing written rules.
- What to check first
- Whether you can use your platform at all. That depends on the law of your country and the platform's terms. If you are resident in Turkey, read which platforms can be used below.
Finance team needing read-only reporting
What you usually need: balances, fills, transfers and fees read from your company's exchange or broker accounts with read-only keys, kept in one ledger, reconciled against what each platform reports and exported in the format you need. The software places no orders and moves no funds.
Answer these before you contact anyone
- Is every account in scope the company's own, and who at the company creates the read-only keys?
- Which platforms and which records do you need: balances, fills, transfers, fees or all of them?
- How far back must the history go, and does each platform's API still serve that far? If not, where do the older records come from?
- When a report and a platform disagree, which figure wins, and how large a difference is acceptable?
- What are your cut-off time, time zone and reporting currency, and which price source values the holdings?
- Where does the output go, who reads it, and who decides accounting and tax treatment? That decision stays with your accountant, not the software or its developer.
Where to go next
- Matching service
- Exchange API integration, scoped to read-only access. For Turkish platforms, Turkish exchange connectors.
- Example scenario, not a client project
- Read-only crypto portfolio risk dashboard: example scenario. It is written for an individual investor, and its read-only keys and reconciliation jobs are the closest match.
- What to check first
- That each platform offers a read-only key and that its API covers the records and the period you need. A read-only key cannot place orders or withdraw, but it still reveals balances and trades, so keep it secret. See read-only portfolio tracking.
What stays the same
You supply the written rules or the written need. The account and the API key are yours, and by default the software runs on your own server or cloud account. Every project runs in four stages, each ending with something you can read or run, and the samples show the format.
Acceptance checks describe how the software behaves, never profit. Fees depend on scope and effort, not on trading volume or results.
Four questions any brief can answer
- Whose account does the software touch?
- Who wrote the rules or the need?
- Where will it run?
- Who approves each stage?
Which platforms can be used
For customers outside Turkey, which platforms can be used depends on the law of your country and the platform's terms. For customers resident in Turkey, we work with platforms on the Capital Markets Board's (SPK) list that offer an API; being listed does not mean a platform is authorized. Article 99/A of Capital Markets Law No. 6362 treats activity by foreign crypto-asset platforms directed at Turkish residents as unauthorized.
Fincode is a software company and does not provide investment advice, portfolio management or crypto asset services. Tests show how the software behaves, not future results. Trades can lose money.
What Fincode does not do
- Recommend strategies, rules or parameters
- Sell signals or trade recommendations
- Build copy trading
- Run other people's accounts or watch positions
- Take a share of profits
- Give legal, tax or accounting advice
Questions about use cases
How is this page different from the services page?
The services page lists what Fincode builds and what you receive. This page starts from who you are and lists the questions to answer before you contact anyone, so the answers help even if you choose another vendor.
Do I need every answer before I write to you?
No. Your first message only needs the platform, what the software should do and your timeline. Your answers save time in discovery, and anything still open gets settled in the scope document.
Are the example scenarios real client projects?
No. Fincode has no client references yet. The scenarios show how typical needs are designed. Fiva, the one real product, is Fincode's own iPhone app: it shows fund data and estimates and does not place trades.
Can Fincode tell me which rules or strategy to use?
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.
I do not fit any of the five. Can I still ask?
Yes. Send what you have, and we will say in writing whether it fits. The exception is work we decline for everyone: signals, copy trading, running other people's accounts and profit sharing.
Before you send a brief
Have your answers?
Send a short brief with the platform, what the software should do and your timeline. You do not need to share your rules yet, and do not include API keys. Fincode is a software company and does not provide investment advice, portfolio management or crypto asset services. Trades can lose money.