modPAY

Your keys.
On-chain proof.
Books that balance.

modPAY is a non-custodial digital wallet, QR token-payment infrastructure and payment-operations platform for business. Payments are signed in the browser, verified on-chain and posted to an append-only ledger in SQL Server.

Keeping keys safe is not enough

Is securing digital assets only about storing private keys? Or is the real question how transactions are authorized, verified and recorded?

In early 2025, about 1.5 billion dollars were taken from a major exchange's cold wallet. No private key was stolen; the hardware wallets were in place. The signers approved a transaction that looked routine on screen, but the data they signed handed control of the wallet to the attacker. Every day, people lose assets the same way: by signing a transfer to a "poisoned" address that resembles one from their history, or an unlimited token approval.

That thought shaped modPAY. It rests on three principles:

  1. Your keys stay with you. Recovery phrases and keys never leave the device; the server and its administrators cannot reach them.
  2. You sign what you see. Signing Guard decodes the signed transaction on the device and compares network, recipient, amount, token, fee and signer with what was on screen. Any difference and nothing is sent. The wallet signs plain transfers only: no approvals, hidden contract calls or delegations.
  3. Nothing is booked until the chain confirms it. Payments and refunds reach the ledger only after on-chain confirmation.

Safe without being tiring: no extra step for verified merchants, your own accounts or addresses you paid before. A first-time recipient asks for the last 4 characters of the address; a lookalike of an address in your history asks for 8. Addresses are shown in easy-to-compare groups of four.

Signing Guard: possible address poisoning warningNew recipient on a phone: type the last 4 characters

Features

Multi-network checkout

One invoice, several networks: the customer pays where they hold funds (e.g. USDC on Ethereum, Avalanche, Polygon or Arbitrum; USDT on BNB Smart Chain). The first payment closes the other options. No bridge, no FX risk.

BNB Smart Chain and Avalanche

Alongside Ethereum, Polygon and Arbitrum: BNB Smart Chain (BNB, USDT, USDC) and Avalanche C-Chain (AVAX, USDC). Fast blocks tracked, per-network confirmation depth.

KVKK / GDPR

Users erase their own account; personal data is anonymized, financial records stay for legal retention. Strictly necessary cookies only.

Signing Guard

The signed transaction is decoded on the device and compared with the screen; any difference and it is not sent. Warnings for address poisoning and hidden approvals.

Keys stay with the user

Recovery phrases and keys never leave the device; encrypted with Argon2id + AES-256-GCM. No administrator can access them.

QR payments

Enter an amount, get a QR. Customers pay in modPAY or any wallet such as MetaMask (EIP-681).

On-chain proof

A payment is confirmed only at the network's confirmation depth. Reorgs, partial and late payments get their own states.

Accounting-ready

Append-only double-entry ledger, reconciliation and trial balance. Every final payment posts automatically; exact-precision CSV exports for accounting.

Refunds

Signed by the merchant in their own wallet; booked once the exact transfer is verified on-chain.

Ledger, built in

A Ledger connects directly over USB (WebHID); the transfer shows on the device and Signing Guard still checks every byte. The key never leaves the device.

Approvals in your pocket

Payouts waiting for approval, incoming payments and policy changes arrive as push notifications (Turkish/English).

Auditor-ready report

Payouts, approvals, screenings and policy changes in one ZIP, with a SHA-256 hash per file as tamper evidence.

Enterprise treasury controls

Per-transaction and daily limits, allow-lists and four-eyes approval for payouts. Loosening a rule waits 24 hours, so one account cannot switch the controls off and pay out at once. Safe multisig and Ledger/Trezor signing.

AML/KYT screening and Travel Rule

Payers, recipients and allow-lists are screened against the OFAC list, Chainalysis or your own KYT service; sanctioned addresses cannot be paid. Above the threshold an IVMS101 record goes to your Travel Rule provider by signed webhook.

Enterprise sign-in and ERP

Single sign-on with Entra ID, Okta, Google and Keycloak (OIDC); organization-wide two-factor requirement. Ledger export templates for SAP, Logo and Mikro.

Invoices paid from another network

Invoice on Avalanche, customer's USDC on Ethereum? They pay from there with Circle CCTP; modPAY completes the mint, so the customer needs no gas on the destination network.

Your brand, Turkish and English

Turkish and English interface. Your institution's name, colors and logo come from configuration, so the product runs under your brand. EURC for euro.

One-click demo

A new user creates a wallet and taps "Get test tokens" to receive test gas and USDC in seconds, then tries a payment or a cross-chain transfer right away. No faucet hunting.

Cross-chain USDC

With Circle CCTP, USDC is burned on one network and minted on another: no pool, no wrapped tokens, funds always in the user's own wallet. Every step (approval, burn, mint) is confirmed separately and Signing Guard checks each call byte for byte. On Ethereum, Avalanche, Arbitrum and Polygon test networks.

E-commerce API

Your shop backend opens invoices with an API key, tracks their status and sends the customer back to the shop after payment. Keys are limited to one workspace, stored hashed and revocable instantly.

Point of sale

The cashier enters an amount, one QR appears; the screen turns green when the payment is final. Runs on any tablet or phone, nothing to install.

Teams and integrations

Organizations, roles, email invitations, signed webhooks and two-factor authentication.

Screens

Payment request and QR code
Payment request and QR code
Ledger, trial balance and reconciliation
Ledger, trial balance and reconciliation
Refund verified on-chain
Refund verified on-chain
Signed webhooks
Signed webhooks
Organizations and roles
Organizations and roles
Wallet and ownership verification
Wallet and ownership verification
Payment request on a phonePayment reviewPayment confirmed

Why modPAY?

More than accepting crypto: infrastructure ready for an institution's auditors, accountants and security team.

Typical crypto payment gatewaymodPAY
FundsCustodial (funds pass through the provider)Non-custodial: funds stay in your and your customers' wallets
DeploymentProvider's cloud onlyYour infrastructure (Kubernetes, IIS, Docker) or hosted; your brand
Signing safetyWhat is signed is not checked against the screenSigning Guard compares the signed bytes with the screen; built-in Ledger
Payout controlSingle approvalLimits, allow-lists, four-eyes approval, 24-hour cooling-off, Safe
ComplianceProvider's own processSanctions/KYT screening, Travel Rule both ways (IVMS101), hashed auditor report
AccountingCSV dumpAppend-only double-entry ledger, reconciliation, SAP/Logo/Mikro exports
Cross-chainBridge or manual swapInvoices paid with USDC from another network via Circle CCTP
Enterprise sign-inSeparate accountsSSO with Entra ID/Okta/Google, MFA requirement

How it works

  1. The merchant creates a payment request; a unique amount and an expiry are assigned and a QR code is generated.
  2. The customer scans it, sees network, recipient, amount and maximum fee, and confirms. The transaction is signed on their device.
  3. The worker finds the transfer on-chain and counts confirmations; payments from external wallets are detected without a hash.
  4. At the required depth the request is confirmed; ledger posting, event and webhook are produced in one database transaction.

Security

Encrypted on the device

Argon2id + AES-256-GCM; auto-lock; password again for every export.

Explicit consent

No transaction is signed before the user reviews and confirms the values.

Hardened sessions

HttpOnly, Secure, SameSite=Strict cookies; CSRF; lockout; rate limits; TOTP.

Immutable records

Ledger and audit rows are protected by database triggers.

Strict CSP

Same-origin only; no inline scripts or styles.

Kubernetes

Non-root, read-only containers; NetworkPolicies; restricted Pod Security.

Compliance: controls mapped to SOC 2 and ISO/IEC 27001:2022. modPAY does not store, process or transmit card data, so it is outside PCI DSS scope. KVKK/GDPR: privacy notice, self-service erasure and retention in the product. The security review report and control matrix are shared during licensing talks.

Technology

Enterprise .NET and Angular stack; 61 domain and 32 SQL Server integration tests, end-to-end tests on desktop and mobile with real signing and on-chain confirmation.

Angular 22TypeScriptPWAC# / ASP.NET Core (.NET 10)SQL ServerEntity Framework CoreDapperADO.NETRabbitMQRedisHangfireSignalRviemDockerKubernetes · HelmGitHub ActionsAzure PipelinesPlaywrightxUnit

Pilot and licensing

PackageScopePrice
Pilot (testnet)30 days; installation, integration and acceptance test; go-live recommendationOn request
BusinessOne organization, one production installation, support and updatesOn request
EnterpriseMultiple environments, custom networks/tokens, ERP integration, priority supportOn request