Platform

The modules you deploy.

On-ramp checkout, compliance hooks, wallet checks, an operator dashboard, and a branded instance isolated to you.

On-ramp checkout

The customer journey for buying Bitcoin with fiat. You set products, limits, and disclosures. We supply the flow, status handling, and receipts.

Purchase steps you can theme and copy-edit
Status, receipt, and exception paths for operations
Your terms, risk notices, and support links — not Atlasy’s

KYC and AML hooks

The platform waits on your compliance stack. Plug in identity, screening, and monitoring vendors. Atlasy does not run due diligence on your customers.

Gate transacting until onboarding checks pass
Case hand-off to your compliance team
You own the programme, vendors, and legal duty

Wallet verification

Collect destination wallets and run the control checks your policy requires before payout. You decide which proofs count.

Structured wallet capture in the checkout
Operator-defined verification before send
A record of the checks you chose to run

Operator dashboard

The console for the people who run the instance: configuration, cases, and staff access. Separate from the customer-facing brand.

Instance settings without exposing Atlasy to end users
Operational views for support and compliance staff
Role-based access so duties can be split

Branding and theming

An operator instance carries your identity. Colours, wordmark, domain, and transactional email sit with you.

Customer UI under your name and visual system
Your domain and from-addresses
No requirement to show Atlasy on the front end

Operator isolation

Each operator runs a branded instance. Configuration, staff users, and customer records stay in that operator’s deployment — not in a shared consumer brand.

Separate instance per operator
Your staff see your book of business
Your customers contract with you

How the product is built

Operator controls — not decorative seals.

These are product design choices. They are not an audit opinion or a licence for Atlasy.

Role-based access

Staff permissions are assigned by duty. The dashboard is not a single shared admin login.

Brand layered on the core

Theme and legal copy sit above the product so you can change identity without becoming “Atlasy-powered” in the customer’s eye.

Records you can export

Statuses, decisions, and configuration are meant to be producible in an operator review — not a retail growth funnel.

No fake certificates

This site does not display ISO, SOC, FINMA, or VQF seals. If an operator holds those, they belong to that operator.

Ready to launch under your brand?

Book a product conversation. We will walk through the modules, branding, integrations, and a practical go-live path.

Talk to us