Solutions · NoxPos Payments
Pay Button SDK
Embed stablecoin checkout wherever you already ship code
The Pay Button SDK is the geek path: drop it on a billing page, landing, bot, or internal tool. Customers pay USDT/USDC to your wallet; NoxPos takes 0.3% from your fee account. No WordPress or Shopify required.
Script · Session · Reconcile
Geek-sized SDK
for stacks without a cart CMS
Embed amount + QR on any billing page, bot, or CLI. Create sessions with your Integration API Key; unlock when the chain confirms. Flat 0.3% from your fee account.
- Front-end mount
- 1 script
- Backend / host
- Any
- Held by NoxPos
- 0%
- Platform fee
- 0.3%
Front-end mount
Backend / host
Held by NoxPos
Platform fee
Sessions · Builder
1,024.00 USDC
- SaaS · Pro seat29.00 USDC
- API · Credit pack50.00 USDT
Stablecoin received
29.00 USDC · SDK · Paid
Builder playbook
Scenario · Seat unlock
SaaS billing pages
Custom pricing page outside Stripe Checkout. Buyer pays USDC/USDT; your app provisions the workspace when the session settles.
- Custom pricing UI — no full cart CMS.
- Provision seats when the session flips paid.
- API key stays server-side only.
Scenario · Usage meters
API credit top-ups
Metered APIs and AI endpoints. Embed a top-up button on the developer portal; credits land after on-chain confirm.
- Embed top-up on the developer portal.
- Credits mint after on-chain confirm.
- Works with metered AI / API products.
Scenario · Access keys
Membership & community gates
Sell Discord roles, Notion hubs, or private repos. Pay once → bot or webhook grants the role. No Woo theme required.
- Pay once → webhook grants Discord/Notion access.
- No Woo theme required.
- Exact session amount for role tiers.
Scenario · Chat commerce
Telegram / Discord shop bots
Bot sends a pay link or QR for a SKU. Customer pays; bot delivers the file, invite, or license in-thread.
- Bot sends pay link or QR in-thread.
- Deliver files or invites after paid.
- Same Integration fee account as web.
Scenario · Tooling
CLI & docs paywalls
Paid npm packs, CLI licenses, or gated docs. Print a QR in the terminal or open a tiny local page — geek UX by design.
- QR in terminal or tiny local page.
- License npm packs and gated docs.
- Built for geek UX, not storefront themes.
Scenario · One-off bills
Freelancer invoice pages
Static invoice URL per client: amount, memo, Pay Button. Client pays USDT; you reconcile with TxID instead of chasing bank wires.
- One URL per client invoice.
- Client pays USDT; you keep the TxID.
- Skip slow international wires.
Scenario · On-chain culture
NFT mint / allowlist deposits
Collect a deposit or mint fee before allowlist mint. Session amount matches the drop; your mint backend listens for paid.
- Deposit or mint fee before drop.
- Mint backend listens for paid sessions.
- Anti-mix amounts for noisy mempools.
Scenario · Support links
Creator tip jars
Link-in-bio or stream overlays with a sticky pay button. Tips settle to your wallet; platform fee stays off-chain.
- Link-in-bio or stream overlay button.
- Tips settle to your wallet.
- Platform fee stays off-chain.
Scenario · Event SKUs
Indie game & hackathon merch
Weekend jam stores, itch.io add-ons, conference stickers. Spin a landing, embed the SDK, tear it down after the event.
- Spin up a landing for the weekend.
- Tear down after the event.
- No long-lived cart CMS required.
Scenario · Ops tooling
Internal cost-center charging
Charge sister teams for GPU time or staging envs with a private billing page — crypto settlement without opening a public cart.
- Private billing for sister teams.
- GPU / staging cost recovery.
- Crypto settle without a public store.
Scenario · No CMS cart
Static / Jamstack storefronts
Astro, Hugo, or plain HTML shops. Host on CDN; only the session API and SDK need a backend stub.
- Astro, Hugo, or plain HTML.
- CDN-hosted pages + thin session API.
- SDK mounts where you already ship.
Scenario · Redirect fallback
Hosted-page hybrid handoff
Prefer in-page SDK for happy path; fall back to Hosted Pay Page redirect for email invoices or apps that cannot embed scripts.
- In-page SDK for the happy path.
- Hosted Pay redirect when embed fails.
- One merchant, two surfaces.
Integration sketch
Server creates the session; browser shows the button/QR; your app unlocks after reconcile.
- 1
Mint an API key
Profile → API on noxpospay.com. Keep the key on the server only — never in client bundles.
- 2
Create a checkout session
Your backend calls NoxPos with amount, currency, and return/webhook hooks.
- 3
Render Pay Button / QR
Front end mounts the SDK against the session; guest pays from Phantom, OKX, Trust, TronLink, etc.
- 4
Unlock on confirm
Poll or webhook when status flips paid — then grant seats, credits, downloads, or ship goods.