New compliance rules, working in your product.
Your lawyers tell you what the law requires. I make it work in your app, with proof for your auditor, and your customers still get through sign-up.
-
You have a new rule
From the law or your compliance team.
-
I build it into your product
Screens, settings and tests, without losing customers.
-
You can prove it
Every check is saved for your auditor.
Your policy says what. Your engineers need to know how.
Lawyers and compliance decide the rules. Engineers need clear tasks. I turn one into the other and see it through.
“The Company shall ensure that transfers of crypto-assets to self-hosted addresses are subject to appropriate measures to establish that the address is owned or controlled by the customer, where the amount exceeds EUR 1,000.”
Approved by compliance. Nobody in product owns it yet.
Example: Travel Rule for crypto withdrawals
The six projects I do most often.
Pick yours. Each one ends live in your product, with proof for your auditor.
A second identity check provider, picked by country, with a backup if one fails.
Business accounts that ask for directors and owners once, not three times.
Crypto transfers checked for risk, with clear next steps when one looks wrong.
Sender and receiver details on every crypto transfer, in 6 screens.
New EU rules added to sign-up and payments before they start.
Sign-up for a new country, under the licence or partner you already have.
One rule, from the law to the proof.
Every rule gets a line like this. When an auditor asks, you show it.
I have done this inside a regulated product.
I ran sign-up and compliance at UR, with a team supervised by the Swiss regulator FINMA. Before that, product at Mantle.
Held in mETH Protocol at Mantle, which I worked on. I also moved the BIT token to MNT with exchanges.
In product. Head of Product earlier, at QZ Solutions.
Mapped in my free tool, across 71 countries and regions.
Product manager, sign-up and compliance
Mario owned some of the most complex areas of our fintech and compliance product stack.
Start small. Keep the plan either way.
Four ways to work together. Most clients start with the two-week review.
Regulatory Terminal
Ask which rules apply in which country. Every answer links to its source. Also works in Claude.
Two-week review
I compare your rules with your product: what is missing, where you lose customers, and a plan with cost.
Build project
One area, built end to end: Travel Rule, identity checks, business accounts, DAC8 or a new country.
Product lead on your team
I run the work, the providers and the audit proof until you hire someone.
Estimates. The price is fixed after the first call, before any work starts.
Check what applies before we talk.
The Regulatory Terminal tells you which rules apply to you and where. Every answer has a source. No sign-up.
MiCA itself sets conduct and disclosure duties, such as risk warnings. ◐ MiCA Art. 66
Customer due diligence at onboarding comes from AML law, not MiCA. ◐ 2015/849 Art. 13
Every crypto transfer needs Travel Rule data. ● 2023/1113 Art. 14
BaFin guidance on video identification for CASPs: we do not have this yet. ∅ No source
Questions people ask.
Short version: I am not a lawyer, and I work with your compliance team, not instead of it.
No. Your lawyers and your compliance team decide what the requirements are and approve them. I implement them in the product, and I flag where a requirement is unclear so they can rule on it.
With it. Your compliance officer stays the owner of the policy and signs off every product rule. They can see each rule next to its screen, setting and test.
No, that is a question for a law firm. The free tool shows which rules exist and what they say, with sources, so that talk is shorter.
I have implemented Sumsub and ReadID, plus KYT and Travel Rule providers. I take no commissions from providers, so I recommend the one that fits your product.
Week one: I read your rules, go through your app and talk to compliance, product and engineering. Week two: what is missing, where you may lose customers, and a plan with providers, time and cost.
Tell me what you need to build.
A short form, no account. I read every message and reply within one working day.
Or email mariusz@szyma.co