Customer payment
VAT
Gateway fee
Conversion
Payout / conversion to EUR
01
Payment routes
Map every channel — PSP, gateway, wallet, bank — and the path a payment takes to euros in your account.
When your business creates its own flow of money. Your accounting needs its own infrastructure.
For SaaS and digital businesses that accept cryptocurrency, combine Stripe with other payment providers, or run their own checkout. We connect payments, wallets, conversions, customer evidence, invoicing, VAT, and accounting into one controlled workflow — from the original sale to the final settlement.
Custom scope. Fixed monthly retainer. No per-transaction fees.
One payment can become revenue, VAT, a gateway fee, and a conversion into euros — and your accounting has to see every one of those events.
All it takes is to 1map how your money moves, 2turn every event into an accounting rule and 3close the books by those rules every month.
WHY CLIENTS COME TO US
Crypto payments. Multiple PSPs. Custom checkout.
We do not move money and do not hold client funds. We build the accounting and financial-data layer around the payment systems you already use — so every sale, fee, conversion, and payout ends up in the books once, with its evidence.
01 · CRYPTO PAYMENT ACCOUNTING
Customers pay in USDT, USDC, BTC, or other assets.
You sell SaaS, subscriptions, or services and accept crypto through a gateway or straight into a business wallet. We connect sales, gateway and blockchain records, wallets, fees, conversions, exchange-rate valuation, invoices, and the books.
- Gateway & on-chain records
- Wallets
- Conversion to EUR
- Exchange-rate valuation
- Invoices
02 · MULTIPLE PAYMENT PROVIDERS
Stripe plus a crypto gateway, or a second PSP.
One product is sold through several payment channels. We build one consistent model of sales and settlements, match every source to its documents and the bank, prevent double counting, and keep balances under control.
- Stripe
- Crypto gateway
- Alternative PSPs
- Bank
- One sales ledger
03 · CUSTOM CHECKOUT & EVIDENCE
Your own order form, customer fields, and billing.
You run your own checkout or non-standard billing. We define which data to collect, how to prove the customer's country, when to check a B2B VAT ID, which documents to issue, and how they link to payments and reporting.
- Customer country proof
- VIES check
- Invoice rules
- PSP transaction link
- VAT & OSS
CASE STUDY
Stripe, crypto on four networks, three VAT regimes — one fixed price.
A SaaS sold worldwide: card payments through Stripe, USDT and USDC through a crypto gateway and a custodial wallet, conversions into euros, OSS, and reverse-charge purchases. Six accounting firms had declined it before.
ADDITIONAL FINANCIAL MODELS
Affiliate, revenue share, and marketplace payouts.
Partner commissions, referral rewards, revenue sharing, and marketplace or creator payouts may also need an individually designed accounting workflow. Availability and scope are assessed separately for each project.
CUSTOM CHECKOUT · ACCOUNTING EVIDENCE
Slovakia, the EU, the US. Companies and consumers.
Once you sell through your own checkout, every order has to carry the facts that VAT and accounting rely on. We define that chain from the first form field to the closed month.
- 01
Customer & order
Who buys and what they buy, B2B or B2C, and the customer's country.
- 02
Tax & evidence
The VAT rules that apply, the country evidence to keep, and a VIES check where needed.
- 03
Invoice & payment
The right document with the buyer's details, linked to its PSP or gateway transaction.
- 04
Accounting & reporting
Matching, fee treatment, classification, VAT and OSS returns, and the period close.
We define which data and documents your accounting needs and how they flow. Building or changing the checkout itself is a separate, agreed scope of work.
WHERE YOU FIT
One Stripe: Firms Payments. Stripe + crypto: Infrastructure.
A SaaS with subscriptions through Stripe can stay in Accquix Firms even at high transaction volume. Infrastructure starts when an additional payment system brings its own processing and controls every month.
FIRMS CORE
Invoices, platforms, and consolidated statements.
A standard sales model where accounting relies on invoices, platform reports, and ordinary settlement.
FIRMS PAYMENTS
Your own sales through Stripe or another PSP.
Your payments, fees, refunds, payouts, and VAT flow form one recurring direct-sales process.
INFRASTRUCTURE
Several payment systems, crypto, or your own checkout logic.
Gateways, wallets, conversions, and customer evidence that have to be defined, matched, and controlled together.
- A SaaS with 1,000 ordinary Stripe payments a monthFirms Payments
- A SaaS selling through Paddle or Lemon Squeezy as Merchant of RecordFirms Core, unless other complexity exists
- Stripe plus USDT through a crypto gatewayInfrastructure
- Customers pay into a business wallet, then tokens are converted to EURInfrastructure
- Two PSPs, both producing standard flowsScope review — possibly Infrastructure, not automatically
- A custom checkout that needs its own evidence and invoice workflowInfrastructure, when it goes beyond standard processing
- A regular sole trader with invoices and a few foreign expensesSolo Core
- Automated partner or affiliate payoutsAssessed individually
Infrastructure is not more expensive because your company is bigger. It is individual because of how your money moves.
See Accquix FirmsTHE CENTRAL PRINCIPLE
We do not only book the result. We define how it came to exist.
THE CENTRAL PRINCIPLE
One payment can create multiple accounting events. Infrastructure defines how each one is identified, evidenced, and processed every month.
First we understand the economic event. Then we design its evidence, control, and monthly entry.
Customer payment
Payment route
VAT
Country, rate, and document
Gateway fee
Cost and statement
Conversion
Asset, rate, and difference
Payout / conversion to EUR
Bank
Accounting
HOW IT WORKS
First we design the rules. Then we operate them every month.
We do not start with an export. We start with the model: which channels take the payment, where the money goes next, and which events happen along the way.
Payment route
VATGateway feeConversion
02
Accounting rules
For each event type, define the accounting treatment, required data, and supporting documents.
03
Controls
Define completeness, matching, conversion, correction, and exception controls.
Bank01
Payout / conversion to EUR02
Accounting03
04
Monthly operation
Turn the model into a repeatable process with clear inputs, deadlines, and responsibilities.
Your payment setup needs its own control layer.
WHAT YOU GET
A working model first. Then the books, every month.
Infrastructure is priced around the payment systems and controls we operate regularly — not around the number of rows in a report.
FIRST · A WORKING MODEL
Documented, before the first close.
A one-time setup that turns your payment setup into written rules.
- documented payment routes
- accounting rules per event type
- required evidence and input formats
- matching rules and an exception list
THEN · MONTHLY ACCOUNTING
Operated by those rules.
Regular accounting that follows the agreed model every month.
- sales and settlements processed
- gateways, wallets, and bank matched
- transactions classified
- documents and tax obligations checked
- the period closed
ALWAYS · PREDICTABILITY
One process, one owner, one price.
You know who is responsible and what the month will cost.
- a clear process with set inputs and deadlines
- one accountable person
- a fixed monthly fee for the agreed architecture
- no charge per standard transaction
Custom scope. Fixed monthly retainer. No per-transaction fees.
Discuss my payment setupACCQUIX INFRASTRUCTURE
Stripe and crypto. Booked correctly in Slovakia.
Invoices, VAT, fees, conversions, and the payout in euros — if you take payments in more than one way, we design the accounting that keeps all of it provable every month.