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.

What we pay

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.

What moves your reward up

Two reports describing the same flaw rarely earn the same amount. The difference is almost always the quality of the write-up.

A clear 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.

A working demonstration

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.

A proposed remedy

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.

Sending us a report

Write to dev@finlogic.com. Please include enough detail for our team to reproduce the behaviour without going back and forth with you.

  1. Describe the environment

    The affected URL or endpoint, the browser or client you used, the operating system, and the device. For mobile findings, note the app version.

  2. Show the request and the response

    Raw HTTP traffic with the vulnerable parameters highlighted, along with any payload required to trigger the behaviour.

  3. Walk through the reproduction

    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.

  4. Explain the consequence

    Tell us what an attacker actually gains. Impact drives severity, and severity drives the reward, so this section is worth writing carefully.

  5. Keep it between us

    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.

Scope

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.

Findings we reward

  • Remote code execution on our infrastructure
  • Bypassing authentication or multi-factor checks
  • Privilege escalation between roles or accounts
  • Injection flaws such as SQL, command, template, or otherwise
  • Cross-site scripting in either stored or reflected form
  • Cross-site request forgery against sensitive operations
  • Insecure direct object references exposing other customers
  • Server-side request forgery reaching internal services
  • Business-logic errors affecting balances, limits, or FX rates
  • Exposure of credentials, keys, or personal data
  • Clickjacking where a sensitive action can be triggered

Findings we do not reward

  • Scanner output submitted without a demonstrated exploit
  • Missing DNSSEC, SPF, DMARC, or similar configuration notes
  • Absent security headers with no accompanying attack path
  • Host header manipulation with no demonstrable effect
  • Self-inflicted scripting requiring the victim to paste code
  • Clickjacking on pages that perform no sensitive action
  • CSRF on logout, login, or other non-sensitive forms
  • Anything requiring a man-in-the-middle position
  • Anything requiring physical access to an unlocked device
  • Issues that only reproduce on rooted or jailbroken devices
  • Legacy plug-in exploits such as Flash, and unsupported browsers
  • Rate-limit or brute-force reports without a proven consequence
  • Denial of service, volumetric testing, and social engineering of our staff

Eligibility

  • Only original findings qualify. A vulnerability already known to us, already reported, or already public earns no reward.
  • Where several researchers report the same issue, only the first complete submission is paid.
  • One reward is paid per underlying flaw, however many entry points expose it.
  • Current and former Finlogic employees, contractors, and their immediate families cannot claim a reward.
  • We cannot pay anyone resident in, or located in, a jurisdiction subject to sanctions administered by FINTRAC, the United Nations, the FATF listings, or any other regime binding on Finlogic.
  • Payment is conditional on completing the identity checks our regulatory obligations require.
  • Finlogic decides, at its own discretion, whether a report qualifies and how it is graded. Submitting a report means accepting the terms on this page.

Rules of engagement

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.

  • Give us a reasonable window to remediate before you publish anything, and coordinate the timing of any disclosure with us.
  • Test only against accounts you own or have been given explicit permission to use. Never interact with a live customer account.
  • Do not degrade, disrupt, or overload our services, and do not modify or destroy any data you encounter.
  • If you come across personal data by accident, stop immediately, tell us, and delete every copy once we confirm receipt.
  • If a flaw lets you move funds, return the full amount to Finlogic without delay and include the details in your report.
  • Do not attempt to socially engineer Finlogic staff, customers, or our suppliers, and do not pursue physical attacks against our offices.
  • Comply with the applicable law in your jurisdiction and in ours at every stage of your testing.

Get in touch

Email: dev@finlogic.com

diagram diagram

Found something we should know about?

Send it over privately and our security team will pick it up. Good findings are acknowledged, fixed and paid for.