Need Quick Answers?
Browse our frequently asked questions or use the search below to find what you're looking for.
General Questions
GriffNode is a non-custodial crypto payment gateway. Businesses use it to accept Bitcoin, Ethereum, Litecoin, Dogecoin, Dash and 11 ERC-20 tokens, including USDT and USDC, straight into their own wallet.
You get a WooCommerce plugin, payment links, a hosted checkout, a REST API and a dashboard for all your payments.
GriffNode is a legitimate, non-custodial software tool for accepting cryptocurrency payments. You can verify that yourself: payments go directly from your customer's wallet into yours, because we only ever hold your wallet's public key (xPub). An xPub cannot spend funds, so we cannot move your money, and there is no balance on our side to freeze or run off with.
We charge one flat monthly subscription, paid up front. We will never ask you to send crypto to "activate," "verify," or "release" funds, and we never take a cut of your sales. Anyone asking you for a deposit or "withdrawal fee," using our name or any other, is running a scam.
No investment schemes, ever. We do not offer investments, trading, or guaranteed returns, no one from GriffNode will ever message you out of the blue about "opportunities". GriffNode is run by a named, contactable founder, Emil Dabrowski ([email protected]), and our code is published openly on GitHub. We also have a Trustpilot page.
We currently support:
- Bitcoin (BTC) - The original cryptocurrency
- Litecoin (LTC) - Fast and low-fee transactions
- Dash (DASH) - Privacy-focused digital cash
- Dogecoin (DOGE) - Popular community-driven coin
- Ethereum (ETH) - Smart contract platform
- ERC-20 tokens - USDT, USDC, EURC, DAI, WBTC, WETH, SHIB, PEPE, LINK, UNI and LEO, paid to your Ethereum address
Additional cryptocurrencies are added based on merchant demand and network stability.
Four things set GriffNode apart:
- Payments go straight to your wallet. We never hold your money.
- A flat monthly price. No percentage of the payment amount and no GriffNode fee per transaction.
- Live in minutes. Sign up, connect your wallet and take your first payment.
- Built for developers too. A REST API, 8 open source SDKs, and webhooks on Business and higher.
Confirmed blockchain payments can't be charged back through a card network. You still handle refunds and customer service yourself.
No! We offer solutions for all skill levels:
- No-code: Use our dashboard to generate payment links and invoices
- WooCommerce and WordPress: Install our WooCommerce plugin or our WordPress plugin straight from the WordPress.org plugin directory
- Other platforms, including Shopify: Send customers to a hosted payment page and confirm orders with a webhook
- Developers: Integrate using our REST API with SDKs for JavaScript, Python, PHP, Go, Ruby, Java, C# and Rust
GriffNode is available to merchants worldwide, with some exceptions. We currently cannot serve merchants in:
- Countries under international sanctions (e.g., North Korea, Iran)
- Regions where cryptocurrency is explicitly illegal
Our Compliance page explains the sanctions rules.
We support most legal businesses including e-commerce stores, SaaS platforms, freelancers, non-profits, and service providers. We do not support:
- Illegal goods or services
- Adult content or gambling (in most jurisdictions)
- Unregistered securities or investment schemes
- Money laundering or terrorist financing
See our Terms of Service for complete usage guidelines.
We don't promise an uptime percentage. Our status page shows current service health, so you can check it yourself at any time.
Our dashboard is fully responsive and works on mobile browsers. We don't currently have native iOS/Android apps, but our web interface provides full functionality on mobile devices including payment monitoring, transaction history, and account settings.
Yes. Starter is free: 30 transactions a month, no card and no fee per transaction.
There is no simulated test mode yet. Test API keys (sk_test_) exist, but payments made with them are real on-chain payments, so test with a small amount. See the Test Mode Guide.
We usually reply to support email the same day, on every plan.
Critical issues (payment failures, API outages) go first on every plan. Professional and Enterprise messages go ahead of the rest of the queue, and Enterprise gets a direct line to the founder.
In most jurisdictions, yes. Accepting cryptocurrency as payment for goods and services is legal in the majority of countries, including the US, the UK, the EU, Canada and Australia. A handful of countries restrict or ban it outright, and we cannot serve merchants in sanctioned regions, see our Compliance page.
GriffNode is non-custodial: payments go straight from your customer to a wallet you control, so you hold your own funds rather than a third party holding them for you. That does not remove your own obligations. You still have to follow the rules that apply to your business, including tax reporting, sales/VAT treatment and any licensing your industry requires.
This is general information, not legal advice. Check the rules in your own country, and speak to a lawyer or accountant if you are unsure.
The main differences are the fee model and custody. BitPay, Coinbase Commerce and NOWPayments all price as a percentage of every transaction. GriffNode charges a flat monthly fee ($0, $49 or $129, or custom) and takes no cut of the payment amount, so a $10 sale and a $10,000 sale cost you the same.
Custody and payout terms differ by provider, so check each one’s own terms. GriffNode is non-custodial: we only ever hold your wallet’s public key (xPub), which cannot spend, and payments land directly in your wallet as the chain confirms.
Nobody offers chargebacks, because blockchain payments are irreversible by design. Fees and terms change, so check each provider’s current pricing page before deciding, and see the full pricing comparison.
For a provider-by-provider breakdown, read BitPay alternatives, crypto payments vs Stripe, or the underlying difference this all rests on: non-custodial vs custodial processors.
Almost certainly, yes. Most tax authorities treat crypto received for goods or services as ordinary business income, valued in your local currency at the moment you receive it, and many also treat a later disposal of that crypto as a separate taxable event if its value has moved.
Because GriffNode is non-custodial the funds are yours from the moment they land, which is exactly why the reporting is on you rather than on us. To make that easier, your dashboard includes tax reports: export your transaction history with per-transaction fiat values for any period and hand it to your accountant.
This is general information, not tax advice. Rules differ by country, so confirm your obligations with a qualified accountant.
Our Privacy Policy explains what data we process, why, who receives it and how long we keep it. We never sell or rent personal data.
Account & Security
Getting started is simple:
- Visit griffnode.com/signup
- Enter your email and create a secure password
- Verify your email address
- Complete your profile and wallet setup
- Start accepting payments immediately!
The entire process takes less than 5 minutes.
No. 2FA is optional and never blocks signup or setup, but we recommend it. Once 2FA is on, actions that change where your money goes, such as changing a wallet, ask for a fresh 2FA code or passkey.
We support authenticator apps (TOTP, such as Google Authenticator, Authy or 1Password), recovery codes and passkeys.
We don't! GriffNode operates in direct-to-wallet mode by default:
- You provide your cryptocurrency wallet addresses (XPubs)
- Customer payments go directly to your wallet
- We never hold or custody your funds
- You maintain complete control at all times
Your keys, your crypto. We're completely non-custodial.
What that distinction actually means for your money is covered in non-custodial vs custodial payment processors, and why it matters if a bank ever debanks your business.
Use the "Forgot Password" link on the login page. You'll receive a secure reset link via email. If you've enabled 2FA, you'll also need your authenticator app or backup codes.
Important: We cannot recover your account if you lose access to both your email and 2FA device. Always save your backup codes in a secure location!
- Keep your secret key (
sk_live_) on your server only. Never put it in browser code or commit it to source control. - Use your test key (
sk_test_) in development so your live key stays out of it. - Rotate keys after a team change, or whenever you think a key leaked.
- On Professional and Enterprise, restrict keys to your servers' IP addresses.
If you suspect unauthorized access:
- Immediately change your password
- Revoke all API keys and generate new ones
- Review recent transactions for unauthorized activity
- Enable 2FA if not already active
- Contact [email protected] immediately
We'll help secure your account and investigate any suspicious activity.
Not in the dashboard yet. Email [email protected] from your current address and we'll change it for you.
Go to Security in your dashboard and choose Delete account. Make sure no payment is still open, and export your transaction history first if you need it. Deleting is permanent.
Invoices and accounting records are kept for as long as tax law requires. The Privacy Policy lists every retention period.
Yes, on the Professional and Enterprise plans. In Dashboard → API & Integrations → API Keys → IP whitelist, add each server's public IP address (IPv4 or IPv6). Once the first entry is added, requests with your keys from any other IP are rejected with a 403 error.
On the sign-in screen, choose to use a recovery code instead of the 6-digit code, and enter one of the recovery codes you saved when you turned on 2FA. Each code works once.
Lost those too? Email [email protected] from your account's email address.
Repeated failed sign-ins are slowed down to stop password guessing. Wait a few minutes, or reset your password with Forgot password on the sign-in page.
Yes. The Security section of your dashboard keeps an activity log of your account, such as sign-ins and security changes.
Payments & Transactions
A flat monthly fee, never a percentage of your sales:
- Starter: free, 30 transactions a month
- Business: $49 a month, 300 transactions a month
- Professional: $129 a month, 1,000 transactions a month
- Enterprise: custom pricing for higher volume
There is no GriffNode fee per transaction and no percentage of the payment amount. When you reach your plan's monthly limit, new checkouts pause until the next month or until you upgrade. We never charge an overage fee. Blockchain network fees are separate and paid by the sender. No setup or cancellation fees. See our Pricing page for details.
Confirmation times vary by cryptocurrency:
- Bitcoin (BTC): ~10 minutes (1 confirmation) to 60 minutes (6 confirmations)
- Litecoin (LTC): ~2.5 minutes (1 confirmation)
- Ethereum (ETH): ~15 seconds to 5 minutes
- Dash (DASH): ~2.5 minutes (InstantSend: 1-2 seconds)
- Dogecoin (DOGE): ~1 minute
GriffNode waits for a set number of confirmations for each coin before it marks a payment as completed.
Confirmed blockchain payments are generally irreversible and don't go through a card network chargeback process.
You can still refund a customer by sending a separate payment from your own wallet to an address they give you. GriffNode never holds your funds, so we can't send refunds for you.
You remain responsible for customer service, refunds, delivery, consumer protection and your other legal obligations.
Minimum: To ensure payments cover blockchain network fees, we recommend:
- Bitcoin: $5 USD equivalent
- Ethereum: $2 USD equivalent
- Other coins: $1 USD equivalent
Maximum: No upper limit on transaction size. Process payments of any amount.
Integration & Technical
Yes! We provide a comprehensive REST API with:
- Complete payment lifecycle management
- Webhook notifications on Business and higher
- Address generation and monitoring
- Transaction history and reporting
- Rate limiting and security features
Check our API Documentation for detailed integration guides.
We publish a WooCommerce plugin and a WordPress plugin, and both are listed in the official WordPress.org directory: in your admin go to Plugins, Add New, search for GriffNode and click Install Now on the one you need. You can also upload either zip from our GitHub releases page. We do not have a Shopify app, and GriffNode is not in Shopify's list of payment providers, so on Shopify, and on any other platform, you send customers to a hosted payment page and confirm the order with a webhook. See our Integration Documentation for setup guides, or the platform walkthroughs for Shopify, WooCommerce, WordPress and Wix.
Not yet. Test API keys (sk_test_) keep your live key out of development, but payments made with them are real: they use real addresses from your wallet and real coins.
The cheapest test is a small real payment, a few dollars in a low-fee coin such as LTC or DOGE, which lands in your own wallet. A simulated test mode is in development. See the Test Mode Guide.
Troubleshooting & Common Errors
Most common causes:
- Still pending confirmations: Check the blockchain explorer with the transaction ID
- Wrong amount sent: Verify they sent the exact amount displayed (including fees)
- Payment window expired: Generate a new payment request
- Wrong currency: They sent BTC instead of LTC, etc.
Transaction IDs can be tracked at Troubleshooting Guide.
A payment up to 2% below the requested amount counts as paid. Below that, it is marked Partial in your dashboard, and on Business and higher your webhook gets payment.partial.
You can ask the customer to send the rest, accept the partial amount and adjust the order, or refund it from your wallet.
Overpayments are automatically accepted and marked as "Overpaid" in your dashboard. You can:
- Keep the overpayment as a tip/donation
- Apply it as store credit for future purchases
- Refund the excess amount to the customer
The full amount goes to your wallet; you control how to handle it.
No, it's not lost. Common reasons for delays:
- Low network fee: Transaction waiting in mempool for miners
- Network congestion: High blockchain activity causing delays
- Unconfirmed parent: Previous transaction needs to confirm first
Most transactions confirm within a few hours. A transaction that never confirms eventually drops out of the network, and the coins never left the sender's wallet.
Unfortunately, cryptocurrency transactions are irreversible. If sent to:
- Invalid address: Transaction will fail and funds stay in sender's wallet
- Wrong but valid address: Funds are gone unless the recipient agrees to return them
- Your old address: If it's still in your wallet, you'll receive it
Always double-check addresses before sending!
Troubleshooting steps:
- Send a test event from Dashboard → Webhooks
- Verify your endpoint is publicly accessible (not localhost in production)
- Make sure your server returns a 2xx status within 10 seconds
- Check firewall isn't blocking our IPs
- Validate webhook signature in your code
See Webhook Documentation for setup details, or the crypto payment webhooks guide for a worked example with signature verification.
Common authentication issues:
- 401: Invalid or missing API key in Authorization header
- 403: Valid key but insufficient permissions, or IP not whitelisted
Correct header format: Authorization: Bearer YOUR_API_KEY
Check your API key status in Dashboard → API Keys.
Every API key has a per-minute and a per-hour limit, set by your plan:
- Starter: 30 requests a minute, 500 an hour
- Business: 100 a minute, 2,000 an hour
- Professional: 300 a minute, 5,000 an hour
- Enterprise: 1,000 a minute, 20,000 an hour
A throttled request returns 429 with a Retry-After header: wait that many seconds before retrying, and watch X-RateLimit-Remaining. To check many open payments, use one GET /transactions/list?ids= request. See the API Reference.
This can happen if customer refreshes the payment page or clicks "Pay" multiple times. To prevent:
- Use unique
order_idfor each transaction - Check for existing payments before creating new ones
- Send an
X-Idempotency-Keyheader when you create a payment
If a customer paid twice, refund one payment from your own wallet.
Every payment is open for 60 minutes, with the price locked for that whole time. After it expires, create a new payment request.
Coins sent up to 6 hours after the window are still detected: the payment shows as Paid late and we email you, so you can choose Mark as paid (your shop gets payment.completed) or Dismiss after refunding the customer from your wallet. Coins sent later still land in your own wallet (we never hold funds) but aren't matched to the order: check your wallet and handle them yourself.
Payments made with a test key (sk_test_) are real on-chain payments today, not testnet ones. So check them like any live payment:
- The customer sent the exact amount shown, in the right coin
- The 60-minute payment window had not expired
- The transaction has enough confirmations on a block explorer
A simulated test mode is in development. See the Test Mode Guide.
Common plugin issues:
- API keys not configured or incorrect
- Plugin not activated in payment settings
- Currency not supported (prices must be in USD, EUR, GBP or PLN)
- Plugin needs update to latest version
- Conflicting payment gateway plugins
Check plugin logs and see platform-specific guides at Integration Docs.
The dashboard shows pending payments only, not your total wallet balance. To see actual wallet balance:
- Use a blockchain explorer with your wallet address
- Check your wallet application directly
- Remember: GriffNode doesn't hold funds, they go straight to your wallet
The dashboard only tracks payments created through GriffNode: the API, our plugins and payment links.
SSL errors usually indicate:
- Outdated SSL certificate bundle on your server
- Firewall blocking HTTPS connections
- Using HTTP instead of HTTPS in API base URL
- Self-signed certificates in development (disable SSL verify for testing only)
Ensure your HTTP client library has up-to-date CA certificates.
Exchange rates are locked when payment is created and held for the payment window duration (60 minutes). This protects against volatility. The rate shown in your dashboard is the rate at payment creation time, not current market rate.
To minimize discrepancies, encourage customers to complete payments quickly.
Wallet & Addresses
An extended public key (xPub, ypub or zpub) lets us derive a fresh receiving address for every payment and watch for incoming funds.
An extended public key cannot spend your funds. It can, however, be used to derive public addresses and expose associated transaction history. Treat it as sensitive information. Never share your private key or wallet recovery phrase.
See the Wallet Setup Guide for how to export it, or how one seed phrase controls thousands of addresses.
Not recommended. While technically possible, reusing addresses:
- Reduces privacy (all transactions publicly linked)
- Makes payment tracking difficult
- Increases risk of payment confusion
GriffNode automatically generates unique addresses for each payment using HD wallets. Always use the address provided for each transaction.
Open Wallets in your dashboard and add the new xPub. If 2FA is on, we ask for a fresh code or passkey first.
Payments created before the change keep their address from the old wallet, so keep the old wallet until those are paid or expired. New payments use the new wallet.
Give us the extended public key your wallet exports. For Bitcoin we accept xpub, ypub and zpub keys. Native SegWit addresses (starting with bc1q) have the lowest fees, so use them if your wallet supports it.
Taproot (bc1p) and multisig keys are not supported yet.
Yes! You configure a separate wallet for each supported cryptocurrency:
- Bitcoin → Your Bitcoin wallet XPub
- Ethereum → Your Ethereum wallet XPub (ERC-20 tokens are paid to the same wallet)
- Litecoin → Your Litecoin wallet XPub
- And so on...
Each cryptocurrency requires its own wallet. You cannot use a Bitcoin wallet to receive Ethereum, for example.
Absolutely! Hardware wallets are highly recommended for security. Simply export the XPub from your hardware wallet and provide it to GriffNode. Your private keys never leave the hardware device.
Any wallet that can export an extended public key should work. We have tested Ledger for Bitcoin and Litecoin.
If you're using HD wallets (XPub), all generated addresses are part of your wallet - you don't need to sweep them. Your wallet application automatically manages all addresses.
If using individual addresses, use your wallet's "sweep" or "consolidate" feature to move funds to a single address (note: you'll pay network fees for each consolidation).
Standard derivation paths:
- BIP44 (Legacy): m/44'/0'/0' - For addresses starting with "1"
- BIP49 (SegWit): m/49'/0'/0' - For addresses starting with "3"
- BIP84 (Native SegWit): m/84'/0'/0' - For addresses starting with "bc1"
Most wallets use BIP84 by default. The derivation path must match your wallet's XPub type.
No! Never! GriffNode operates in watch-only mode. We only need your XPub (public key) to generate addresses and monitor incoming payments. Your private keys remain exclusively in your control.
We cannot spend your funds, only watch for incoming payments. An extended public key cannot spend your funds. It can, however, be used to derive public addresses and expose associated transaction history. Treat it as sensitive information. Never share your private key or wallet recovery phrase.
Not recommended. Exchange wallets have limitations:
- Addresses often change or expire
- Cannot export XPub (must use single address)
- Exchange may flag/freeze accounts receiving merchant payments
- You don't control the private keys
Use a software or hardware wallet that can export an xPub instead.
Before saving your wallet address:
- Send a small test transaction to the address
- Verify it appears in your wallet
- Only then configure it in GriffNode
- Double-check the address character-by-character
Our system validates address format, but cannot verify if you own it. Always test first!
Wallets use a "gap limit" (typically 20) - they stop scanning for addresses after finding 20 consecutive unused addresses. If you generate many addresses that don't receive payments, some may be beyond this gap.
Solution: Increase your wallet's gap limit, or ensure addresses are used in sequential order. Most modern wallets handle this automatically.
Webhooks & Notifications
Webhooks are on Business (1 endpoint) and Professional (up to 3). Starter has no webhooks: our plugins check payment status through the API instead.
- Open Webhooks in your dashboard and add an endpoint
- Enter a public HTTPS URL
- Save the webhook secret and verify the signature on every request
- Use Send test event to check your handler
See the Webhook Documentation, and the crypto payment webhooks guide for handling events in production.
Every webhook includes an X-GriffNode-Signature header. To verify:
- Get the raw request body (before parsing JSON)
- Compute HMAC-SHA256 using your webhook secret
- Compare computed signature with header value
- Reject webhook if signatures don't match
Example code is in our Webhook Guide.
If your endpoint doesn't return a 2xx status within 10 seconds, we retry automatically with growing gaps: after about 10 seconds, 1 minute, 5 minutes and 30 minutes, then 1, 2, 4 and 8 hours, for up to 24 hours after the event.
If every attempt fails, we email you. You can always check a payment's current state with GET /v1/transactions/{transaction_id}.
Use a tunneling service to expose localhost:
- ngrok:
ngrok http 3000- Get public HTTPS URL - localtunnel:
lt --port 3000 - Cloudflare Tunnel: For permanent development URLs
Then use Send test event in your dashboard to hit the public URL.
payment.created: a payment was created and is waiting to be paidpayment.pending: a payment was seen on-chain and is waiting for confirmationspayment.completed: confirmed and fully paidpayment.overpaid: fully paid, with more than was owedpayment.partial: less than the requested amount arrivedpayment.expired: the 60-minute window closed with no paymentpayment.failed: a system failure stopped the payment completing normallypayment.paid_late: coins arrived up to 6 hours after the window; you decide in the dashboardpayment.needs_review: ETH and ERC-20 only, the payment can't be judged automatically; check your wallet
See the Webhook Documentation for every payload field.
Every event has a stable id, the same on every retry:
- Store each processed
idin your database - Check whether the
idexists before processing - If it exists, return 200 straight away (already processed)
- If it is new, process the event and store the
id
This prevents duplicate order fulfillment from webhook retries.
Use asynchronous processing:
- Return a 2xx status to GriffNode right away
- Queue the webhook for background processing
- Process order fulfillment asynchronously
Don't perform heavy operations (email sending, inventory updates) in the webhook handler. Queue them instead.
- Send test event in Dashboard → Webhooks to check your handler
- Webhook.site or RequestBin to inspect the raw payload
- Your server logs for errors
Common causes: SSL errors, signature checks run on parsed JSON instead of the raw body, and handlers slower than 10 seconds.
Yes. In your dashboard settings, under email preferences, you choose which emails you get:
- Payment received: an email the moment a customer's payment is confirmed
- Invoice notifications
- Security alerts, such as sign-ins and suspicious activity
- Weekly reports (Professional)
- Offers and product news
On Professional you can add up to 3 webhook endpoints, and Enterprise has no limit. Business includes 1 endpoint that receives every event. Starter has no webhooks.
Each endpoint has its own secret for signature verification. Separate endpoints are useful for different services, or for staging and production.
Still Have Questions?
Can't find what you're looking for? Visit our Support page or email us at [email protected]. We usually reply the same day.