You want to accept USDC, EURC, or other stablecoins — for tuition fees, event registrations, consulting services, or B2B invoices. Your accounting department runs SAP. They need ISO 20022 bank statements and QR references that auto-match invoices. The gateway makes this possible.
Three things are needed. No server, no subscription, no third party holding your funds.
Where stablecoin payments arrive. Use Phantom, Solflare, or any Solana wallet. For an organization, a multi-signature wallet (Squads) is recommended — payments require approval from multiple people, just like dual authorization at a bank.
Your existing bank IBAN gets linked to your Solana wallet address on-chain, using the verified-iban.sol registry on Solana Name Service. Counterparties can send stablecoins to your IBAN — the gateway resolves the address automatically.
A single web application you open in a browser. Use the hosted version at iso.gbits.io, or download the HTML file and run it on your own infrastructure with your own API key. No account to create, no installation.
Create a Solana wallet (or a Squads multi-sig wallet for your organization)
Fund it with a small amount of SOL for transaction fees (~$0.001 per transaction)
Share your Solana address (or QR code) with the people who will pay you
Send them a regular invoice — Swiss QR invoice, PDF, whatever you use today — but include the Solana address as an additional payment option
When a payment arrives on-chain, open the gateway, connect your wallet, and generate a camt.053 or camt.054 report
Import the XML file into SAP. Done.
The payer doesn't use their bank's eBanking app. They use their Solana wallet. For Swiss QR invoices specifically, the payer can use Gbits Pay — scan or upload a Swiss QR invoice and pay it with stablecoins directly from their Solana wallet. The QR reference from the invoice is automatically embedded as an on-chain memo, so the gateway picks it up and SAP auto-matches the payment to the open invoice.
For counterparties outside Switzerland, or for simple transfers without a QR invoice, the payer sends stablecoins directly to your Solana address using any wallet app (Phantom, Solflare, etc.).
You still issue invoices the way you do today. You just add a stablecoin payment option alongside your bank details.
The gateway produces standard camt.053 and camt.054 XML — the same formats your bank delivers. SAP, Bexio, Abacus, and Oracle import them without modification.
Swiss QR-bill references (QRR, SCOR) are embedded in the stablecoin transaction as an on-chain memo. The gateway maps them to <CdtrRefInf> in the XML — exactly where SAP expects them.
The accountant imports the camt file, the system matches the reference, the invoice is marked as paid. No manual work.
camt.053 supports any date range — daily, monthly, quarterly. The gateway generates statements with opening and closing balances, just like a bank.
Payments settle on Solana instead of SIC, SEPA, or SWIFT. Settlement time: ~400ms instead of hours or days. Cost: ~$0.001 instead of CHF 0.20–2.00.
You receive stablecoins (USDC, EURC, VCHF) instead of bank money. Digital tokens pegged 1:1 to fiat currency, issued by regulated entities (Circle for USDC/EURC).
24/7/365. No cut-off times, no weekends, no bank holidays.
You hold the funds yourself in your own wallet. No bank, no intermediary, no counterparty holding your money.
Your Solana wallet becomes a new cash-equivalent account. The camt.053 provides the opening and closing balances the auditor needs.
The gateway produces the exact same XML your bank produces. If your SAP system can import a camt.053 from UBS or ZKB, it can import one from the gateway. Swiss Payment Standards version tags are included.
Create a sub-account under "Liquid funds" for stablecoin holdings (e.g., 1090 "Digital assets — stablecoins"). Treat it like a foreign-currency cash account. Your auditor can advise on Swiss GAAP or IFRS mapping.
Point the camt.053 import to the new GL account. The gateway uses the synthetic BIC SOLNCHZZXXX (Solana Network, Zurich). Map it once in your bank statement configuration.
Receive USDC (pegged to USD) and your books are in CHF? SAP treats it like a USD payment — applies the exchange rate and books the CHF equivalent. VCHF is 1:1 to CHF with no conversion needed.
Payments settle in under a second. No next-day processing, no batch runs, no value-dating games.
~$0.001 per transaction. For a summer school with 200 participants paying CHF 2,000 each: credit card fees ~CHF 12,000 vs. stablecoin fees ~CHF 0.20.
A participant in Seoul, Dubai, or São Paulo pays with USDC in seconds. No SWIFT, no correspondent banks, no intermediary fees.
Stablecoin payments are final. No dispute window, no chargeback risk. Unlike credit cards.
Your organization holds its own funds. No bank can freeze your account, delay a transfer, or go insolvent while holding your money.
The payment arrives as crypto. The report arrives as a standard bank statement. Your accounting department doesn't learn anything new.
We believe in transparency. Here are the risks and how they can be mitigated.
USDC is issued by Circle and backed by US treasuries and cash reserves. It is not a bank deposit and is not covered by deposit insurance. If Circle were to fail, the peg could break.
Whoever controls the wallet private key controls the funds. If the key is lost or stolen, the funds are gone — there is no bank hotline to call.
Swiss law (FINMA guidance) currently treats stablecoins as digital assets. The regulatory framework is evolving.
The stablecoins themselves are smart contracts on Solana. A bug could theoretically affect holdings.
The gateway is early-stage, open-source infrastructure. Tested at hackathons, not yet battle-tested at enterprise scale.
Converting stablecoins back to CHF requires a crypto exchange or OTC desk — an extra step compared to receiving a bank transfer directly.
The best way to understand the gateway is to try it. Connect a wallet, generate a test report, and see what the camt.053 looks like.
Animated inbound/outbound flows
Solana → ISO 20022 XPath
16 questions on mapping decisions
Full project overview
You don't need to commit to anything. Generate a camt.053 from your wallet's existing transactions and show it to your accountant. If SAP accepts it, you have your answer.
Questions? romanix@gbits.io