Skip to content
ArionPay

Security

Bug bounty

Found a way to break ArionPay? Tell us first, privately. We fix it, and we pay for real findings.

Rewards

What we pay for

We pay by real impact, shown with a working example. The amount within each range depends on how much harm the problem could do and how good the report is.

  • Critical$500 – $1,000
    • Send a customer’s payment to an address the merchant did not choose
    • Add or change a payout wallet, API secret or webhook on an account that is not yours
    • Get into the admin panel, or take over any merchant account
  • High$150 – $500
    • Read another merchant’s invoices, customers, API keys or settings
    • Get past the authenticator-app check on a protected action
    • Make an invoice show as paid without the payment arriving
  • Medium$50 – $150
    • Stored cross-site scripting (XSS) on the dashboard or the checkout page
    • A forged request that changes something on a logged-in account (CSRF)
    • A webhook that a shop accepts as signed by ArionPay when it was not
  • LowThanks, at our discretion
    • A real problem with small impact, for example information that should not be shown but gives no access

Scope

What you may test

  • merchant.arionpay.com: log in, sign up, the merchant dashboard and the admin panel
  • Checkout pages (/pay/…) and payment links
  • The merchant API (/api/v1/…) on merchant.arionpay.com and api.arionpay.com, and webhook signatures
  • arionpay.com (the website), including its contact and demo forms

Not paid

What we do not pay for

  • Reports from automated scanners without a working example
  • Missing security headers, cookie flags, SPF / DKIM / DMARC or TLS settings without a shown attack
  • Clickjacking on pages with no sensitive action, self-XSS, logout CSRF
  • Rate limits on forms that change nothing, and denial of service of any kind
  • Software version numbers without an exploit
  • Phishing or social engineering of our team, merchants or customers, and physical attacks
  • Services we do not run: Cloudflare, Mailgun, blockchain nodes and APIs, wallet apps, Tether / Circle
  • Attacks that need the victim’s seed phrase, password, unlocked device or a malicious browser extension

Rules

Test safely

If you follow these rules, we treat your testing as allowed research: we will not take legal action against you or report you for it, and we will say so if anyone asks.

  1. Test only with accounts you created yourself. Test invoices ("test": true) need no real money and no wallet.
  2. Never send real payments to test, never pay or contact merchants’ customers, and never use other people’s accounts.
  3. Do not look at, keep, change or delete anyone else’s data. If you reach some by accident, stop, delete what you saw, and tell us in your report.
  4. No denial of service, no spam, no load testing. Keep automated requests below 5 per second.
  5. Do not share or publish the problem until we have fixed it, or until 90 days after your report, whichever comes first.
  6. One problem per report. The first person to report a problem gets the reward; later duplicates do not.

This covers testing under these rules from 7 November 2026 on. Taking money, using someone else’s account or keeping their data is never research, whenever it happened.

Report

How to report

Email security@arionpay.com in English with:

  • the page or API endpoint, and the email of your test account
  • step-by-step instructions we can follow, with the requests and answers (leave out passwords and secrets)
  • what an attacker could do with it

We will never ask you for a seed phrase, a password or a payment in order to receive a reward.

  1. Step 1

    Within 3 working days

    We confirm that we received your report.

  2. Step 2

    Within 10 working days

    We tell you whether we can reproduce it and how serious we think it is.

  3. Step 3

    Fixed

    We fix it, tell you, and you may check the fix. Critical problems are fixed first.

  4. Step 4

    Paid

    We pay the reward in USDT or BTC to a wallet you name, after the fix is live.

How ArionPay protects payments

Knowing the design helps you look in the right places: watch-only wallets, every payment matched to exactly one invoice, and an authenticator code for every change that touches money. Read about our security. Machine-readable contact details are in security.txt.