Support

Questions and Answers

Find practical answers about merchant onboarding, checkout integration, payment flow, fees, and account readiness.

Does CryptMeUp hold customer or merchant funds?

No. CryptMeUp is designed around direct wallet-to-wallet payment flows. We provide checkout screens, payment requests, QR pages, and verification tooling, while merchant funds do not sit in a CryptMeUp custody balance.

What does non-custodial checkout mean in practice?

It means payer and merchant wallets stay central to the payment. CryptMeUp helps format payment context, guide the payer, and verify the result, but the platform does not become a bank account or exchange account between both parties.

Which payment type should I use first?

Use Basic Payment for one invoice, order, or one-time request. Use Permanent QR when the same receiving flow should be reused many times. Use Commerce Checkout when your backend needs to sign and sync payment context.

Why does CryptMeUp need merchant checks?

Merchant checks protect the public payment surface from obvious abuse and help keep checkout flows safer for customers and counterparties. Live merchant access depends on account readiness, wallet setup, and required compliance state.

How are platform fees handled?

Fee handling depends on the network model. Supported onchain-fee networks use transparent fee logic during payment execution, while networks without direct fee splitting use prepaid payment capacity instead. The pricing page explains both models.

Can customers pay from any wallet?

Wallet support depends on the selected chain and payment method. Current live support should be checked on the chain and wallet support page, because planned wallets are not the same as live wallets.

What should I include when asking for support?

Include the account email, transaction identifier, payment identifier, chain, and wallet address when relevant. Describe what you expected to happen and what happened instead. Never send private keys, seed phrases, or wallet recovery material.

How can developers integrate CryptMeUp cleanly?

Start with the payment type that matches your business flow. Use signed Commerce Checkout when payment context must come from your backend. Use redirect and webhook handling so your system can track final payment state, and keep identifiers in your own order records so reconciliation stays clear.

Need direct help?

Send enough context for us to help. Useful details include account email, transaction identifier, chain, wallet address, or integration notes.

We use essential cookies for site functionality. These cookies are necessary to keep the site working properly.