Solvexa
Apply Talk to us
Compliance-ready

Compliance-ready is in our DNA, not a layer on top

We did not add screening to a payment platform, we built the platform around it. Address and transaction screening, counterparty due diligence, sanctions checks and audit-ready reporting sit on the payment path itself, from the first line of code rather than as a module switched on later.

Built compliance-first, not compliance-later

Bolted-on compliance produces the same result every time: a screening tool nobody opens, a spreadsheet of exceptions, and a scramble when a counterparty asks for evidence.

We took the other route and put the checks on the transaction path itself. Every address is scored before funds move, every counterparty is reviewed before it is onboarded, and every decision is recorded with the data it was made on, so the file assembles itself.

None of this is legal advice, and it does not replace your own obligations. It gives you the operational layer those obligations rest on.

The path a transaction takes

Four checkpoints, none of them optional

  1. 01

    Address scored

    Incoming payments on arrival, outgoing payouts before release.

  2. 02

    Counterparty on file

    Ownership, structure and business model reviewed before the first transaction.

  3. 03

    Behaviour watched

    Activity compared against the profile agreed when the account opened.

  4. 04 Always on

    Decision recorded

    What was checked, what was decided, and who decided it, stored together.

On every transaction

Scored before the funds move

A risk score on every address in the flow, computed before the transaction is accepted or released.

Scoring looks at the exposure behind an address: what it has interacted with, how funds reached it, and how far it sits from known high-risk sources. Thresholds are yours to set. A score above the line can be held for review, escalated to a named approver, or rejected outright, and the choice is configured per flow rather than argued case by case.

We run our own risk engine on top of licensed blockchain analytics data.

What that looks like in practice

Counterparty due diligence

Onboarding covers corporate structure, beneficial ownership, licensing where it applies, and the business model behind the payment volume. What we collect is proportionate to the risk the account carries, and files are kept current: a material change in ownership, jurisdiction or activity triggers a review rather than waiting for the next annual cycle.

Ongoing monitoring

Patterns matter more than single transactions. Volume that jumps, counterparties that appear from nowhere, structuring patterns, and flows through mixing services all raise alerts. Alerts go to people, not to a log file: each one is worked, resolved and recorded, with the reasoning attached.

Sanctions and watchlists

Checked, rechecked, and blocked when it matters

At every touchpoint

Counterparties are checked at onboarding and rescreened as lists change, not only on the day they signed.

Consolidated coverage

Major international and national sanctions programmes, plus PEP and adverse media coverage. The exact list is confirmed per contract.

Blocking and escalation

A confirmed match stops the transaction and follows the escalation procedure agreed with you in advance.

Reporting that holds up under review

Banks, auditors and payment partners ask the same four questions in different words: who paid, where the funds came from, what you checked, and what you decided. Our reporting answers all four.

Per transaction

Screening outcome attached to every line

Per counterparty

Due diligence file and its trail

Per case

Alert history with resolutions and timestamps

Per period

Summaries formatted for partner and bank review

How decisions get made

The same rule, the same outcome, every time

01

Risk appetite agreed in writing

Thresholds, prohibited activity and escalation levels are set with you before go-live.

02

The system applies it

The same rule produces the same outcome regardless of who is on shift.

03

Exceptions reach a person

Anything outside the rules goes to an accountable person, not to a queue.

04

Everything is recorded

The decision, the data behind it and the person who made it are stored together.

Please note. The information on this page describes operational procedures, not legal advice. It does not create a compliance obligation on our part in place of yours, and it does not guarantee any particular regulatory outcome. Solvexa is a B2B payment service provider and is not an exchange, a wallet, or a custody service.

Next step ↴

Bring us your risk questions

If a bank or a partner has asked you something you cannot answer yet, that is the conversation to start with.

Talk to our team How it works

An NDA is available on request before you share anything sensitive.