Moving money across borders means our customers trust us with two things that cannot be replaced: their funds and their personal data. Finlogic's engineering and security teams test our platforms continuously, but no internal review programme catches everything. Independent researchers routinely see what in-house teams stop noticing.
This programme is our open invitation to that community. If you discover a weakness in any Finlogic system, tell us before you tell anyone else, and we will investigate it quickly, fix it, and reward you for the finding.
Payouts are graded by the real-world impact of the issue rather than by its technical category. There is no fixed ceiling, a finding that threatens customer funds or the integrity of our settlement rails will be paid above the published band. The figures below describe what a typical report in each grade attracts.
| Severity | Reward | Typical example |
|---|---|---|
| Critical | $3,800 – $14,500 | Movement of customer funds, full account takeover at scale, or unrestricted access to production data |
| High | $800 – $3,500 | Authentication bypass, server-side code execution, or exposure of another customer's records |
| Medium | $150 – $500 | Stored scripting flaws, meaningful logic errors, or limited disclosure of non-public information |
| Low | up to $150 | Issues with narrow impact that still merit a fix on our side |
Rewards are quoted in US dollars and can be settled to a Finlogic account or by international transfer. Finlogic determines the final grading and amount for every submission.
Two reports describing the same flaw rarely earn the same amount. The difference is almost always the quality of the write-up.
Reports that set out the flaw precisely, what breaks, where, and why it matters to a Finlogic customer are graded more generously than a one-line note with a screenshot attached.
Scripts, request captures, or a short recording that lets our engineers reproduce the issue on the first attempt shorten the review cycle and increase the payout.
If you can point to the underlying cause or suggest how the fix should be approached, say so. Practical remediation advice is treated as part of the finding.
Write to dev@finlogic.com. Please include enough detail for our team to reproduce the behaviour without going back and forth with you.
The affected URL or endpoint, the browser or client you used, the operating system, and the device. For mobile findings, note the app version.
Raw HTTP traffic with the vulnerable parameters highlighted, along with any payload required to trigger the behaviour.
Numbered steps from a clean session to the point of failure. Attach a screenshot or a short screen recording where the flaw is easier to show than to describe.
Tell us what an attacker actually gains. Impact drives severity, and severity drives the reward, so this section is worth writing carefully.
Do not post details, proof-of-concept code, screenshots, or video to any public destination including GitHub, Pastebin, YouTube, Imgur, X, or a personal blog while the issue is open.
Our commitment: we acknowledge every submission within two business days and give you a triage decision, with the assigned severity, within ten business days. If our team cannot reproduce the issue from the material supplied, we will come back to you once before closing the report, a finding we cannot verify cannot be paid.
Every Finlogic-operated service is in scope, including this website, the customer dashboard, our multi-currency account platform, the bulk payment tools, and our public APIs. As a rule of thumb: if a flaw could lead to financial loss, unauthorised access, or a data breach, we want to hear about it.
Research carried out in good faith and within these boundaries will not lead to legal action from Finlogic. We ask you to hold to all of them.
Email: dev@finlogic.com