Wallet Design
CryptMeUp is built to move customer funds directly to the merchant receiving wallet. That design removes the need for wallet connect access, wallet reading, or wallet control on the merchant side.
Simple payment path
Merchant does not connect a wallet to let CryptMeUp inspect balances, approvals, or transaction history. Merchant only configures a wallet address that belongs to the merchant, and that wallet becomes the receiving destination for customer payments.
No wallet reading
We do not need access to merchant wallet contents. We do not need token balances, NFT data, approvals, or signature-based account reads, because that information is outside the job CryptMeUp is solving.
Why this matters
CryptMeUp helps customer choose from supported stablecoins and blockchain-native coins. CryptMeUp formats the payment request and checkout flow so onchain payment is easier to complete, while the actual payment still runs fully onchain from customer side to merchant receiving side.
Why not later
Wallet connect would add access patterns we do not need. It would push more wallet complexity into merchant onboarding without improving the core receiving flow, and our model stays stronger when merchant only sets an owned receiver wallet and nothing more.
What merchant controls
Merchant decides which wallet receives funds and which supported chains and assets make sense for the business. CryptMeUp stays focused on easy checkout, route clarity, and public onchain verification.