Crypto-native productsNatural fit
in-product checkout
Let wallet-native products unlock the next state instantly.
Hosted links, embeds, and API flows can feel like part of the product instead of a borrowed card checkout.
Use cases
Wallet-first checkout
Crypto-native products
Wallets, DeFi tools, gaming studios, NFT launches, OTC desks, and Web3 apps that want payment links, embeds, API flows, and webhooks.
Live
Embed
API
Webhook
Wallet
User
Best for
Wallet apps
NFT platforms
Web3 games
DeFi tooling
Payment examples
NFT mints
Gaming purchases
Wallet add-ons
Web3 SaaS billing
Quick view
Best moment
Account top-up, premium access, NFT service fee, OTC invoice, or Web3 product checkout.
Payment flow
Embedded checkout, hosted payment page, or API-created payment.
Who checks it
Product, operations, or support team.
Practical guide
Give wallet-native customers a checkout that feels like part of the product, not a manual transfer.
Crypto-native products sell to people who already understand wallets, networks, and stablecoins. The challenge is not convincing them that crypto can pay for things; it is making the checkout operationally clean.
A wallet app, DeFi tool, NFT product, OTC workflow, or Web3 SaaS product needs a payment request that ties back to the customer, order, campaign, or account action.
wallet-native userlive status
Live
Why crypto-native users still need structure
Wallet users are comfortable sending funds, but a business cannot run on unnamed transfers. The product needs to know who paid, what they paid for, and what action should follow.
A clean payment object keeps the payment connected to the product workflow, whether the next step is access, credit, delivery, review, or support.
Raw transfers do not scale
Support teams should not identify payments from screenshots.
Product actions need status
A paid event can unlock access, add credit, or move an order forward.
Brand still matters
Even Web3 users notice when checkout feels disconnected from the product.
Where MakePay fits in a Web3 stack
A team can start with hosted links for manual invoices or campaigns, then move into embedded checkout and API-created payments for product-native flows.
Webhooks can carry the paid state back into the app so the product, not support, decides what happens next.
Hosted or embedded
Choose the surface that fits the product moment.
Self-custody settlement
Route settlement toward the wallet strategy the crypto team already uses.
Developer-friendly status
Use API and webhooks to keep payment logic out of chat and spreadsheets.
What product teams should prepare
Decide which product action happens after payment, what metadata is required, and how support can inspect a payment without developer help.
Keep network and asset choices narrow at launch. Too many options can make reconciliation and customer support harder than necessary.
Define metadata
Attach user IDs, order IDs, campaign IDs, or invoice references.
Limit first assets
Start with the assets your customers already request and your team can reconcile.
Test failure states
Know what customers see when a payment expires, underpays, or needs retrying.
Scenario
NFT mints, wallet add-ons, game purchases, Web3 SaaS, DeFi tools, and OTC desks.
When your users already live in wallets, MakePay becomes a simple branded checkout layer. Teams can launch hosted links quickly, embed checkout in-product, or build fully custom flows through the API.
Proof layer
A checkout surface that gives the team a real payment state.
Checkout that matches crypto-native customer behavior
API and webhook support for custom product flows
Embedded modal for in-app payment experiences
Major assets and stablecoins through payment-link rules
Card checkout feels out of place for wallet-native users
Teams need payment events inside product systems
Custodial processors add trust and platform risk
Account top-up, premium access, NFT service fee, OTC invoice, or Web3 product checkout.
Embedded checkout, hosted payment page, or API-created payment.
Product, operations, or support team.
Checkout that matches crypto-native customer behavior
API and webhook support for custom product flows
Checkout that matches crypto-native customer behavior
API and webhook support for custom product flows
Embedded modal for in-app payment experiences
Major assets and stablecoins through payment-link rules
Card checkout feels out of place for wallet-native users
Teams need payment events inside product systems
Custodial processors add trust and platform risk
Account top-up, premium access, NFT service fee, OTC invoice, or Web3 product checkout.
Embedded checkout, hosted payment page, or API-created payment.
Product, operations, or support team.
Checkout that matches crypto-native customer behavior
API and webhook support for custom product flows
Product, operations, or support team.
Embedded checkout, hosted payment page, or API-created payment.
Account top-up, premium access, NFT service fee, OTC invoice, or Web3 product checkout.
Custodial processors add trust and platform risk
Teams need payment events inside product systems
Card checkout feels out of place for wallet-native users
Major assets and stablecoins through payment-link rules
Embedded modal for in-app payment experiences
API and webhook support for custom product flows
Checkout that matches crypto-native customer behavior
Checkout that matches crypto-native customer behavior
API and webhook support for custom product flows
Product, operations, or support team.
Embedded checkout, hosted payment page, or API-created payment.
Account top-up, premium access, NFT service fee, OTC invoice, or Web3 product checkout.
Custodial processors add trust and platform risk
Teams need payment events inside product systems
Card checkout feels out of place for wallet-native users
Major assets and stablecoins through payment-link rules
Embedded modal for in-app payment experiences
API and webhook support for custom product flows
Checkout that matches crypto-native customer behavior
Checkout that matches crypto-native customer behavior
API and webhook support for custom product flows
Setup path
Start with one clear payment moment.
Launch the first flow, prove the status handoff, then expand into nearby payment moments once the team trusts the signal.
1
Choose the product moment
Pick the payment action that most needs a cleaner flow.
2
Create the payment path
Use a link, embed, or API-created payment tied to the user or order.
3
Listen for status
Connect paid events to access, credit, delivery, or operations.
4
Review support load
Adjust copy and metadata so fewer payments need manual research.
Questions
Is MakePay only for non-crypto merchants?
No. Crypto-native teams often need better payment operations even when customers already know wallets.
Can this be embedded in a product?
Yes. MakePay supports hosted and embedded checkout paths along with API and webhook flows.
Does this replace a wallet stack?
No. It provides the payment request, checkout, and status layer around the merchant's settlement setup.
Wallet-first checkout
Build the first payment flow around wallet users.
That lets product teams avoid the awkward gap between a raw wallet transfer and a full custom payment system built from scratch.
in-product checkout
ready
API