Invoices in seconds
Create an invoice with amount, description, reference, and expiry. Get a hosted payment URL you share with the customer. No customer account required — they pay from any wallet that can sign a USDC transfer.
Stablecoin invoicing
for merchants.
Create an invoice in seconds. Share the payment link. Your customer pays in USDC. Webhook fires when payment confirms. Funds settle to your wallet — Primeborg never holds them.
What you get
5 things that distinguish Primeborg Pay
Webhooks with HMAC signing
Subscribe to invoice_paid, invoice_expired, and invoice_cancelled events. Webhooks are HMAC-SHA256 signed with your per-endpoint secret. Delivery is retried with exponential backoff and audited in a delivery log you can inspect.
REST API + API keys
Programmatic access via Bearer tokens (pk_live_…). Create, list, fetch, and cancel invoices. API keys are scoped, last-used-tracked, and revocable. Full docs at /pay/docs.
Merchant dashboard + analytics
Lifetime revenue, 30-day revenue, open invoices, recent activity. Drill into per-invoice receipts and customer payment details. Export to CSV for accounting.
Non-custodial settlement
Customer USDC payments go to YOUR wallet on confirmation, not to a Primeborg-controlled account. We see the on-chain transaction and fire the webhook. Funds never sit on a Primeborg balance.
Frequently asked
Honest answers, not marketing
How is this different from Stripe?
Stripe handles fiat (cards, ACH) and is custodial — Stripe holds your money for days before payout. Primeborg Pay handles stablecoins (USDC) and is non-custodial — the customer's payment goes straight to your wallet, settled on-chain in seconds. No payout schedule, no rolling reserve, no 1.5-2.9% card fees.
How is this different from BTCPay Server?
BTCPay Server is self-hosted and Bitcoin-first. Primeborg Pay is hosted (no infrastructure to run) and stablecoin-first (USDC on Base by default). Both are non-custodial. If you want the self-hosted route, BTCPay Server is excellent; if you want zero-ops, Primeborg Pay is the tradeoff.
What chains and tokens does Pay accept?
USDC on Base in v1. Roadmap: USDC on Solana, USDT on Tron (the dominant stablecoin rail in many emerging markets), and native ETH/SOL/BTC via THORChain bridging. Each invoice declares its accepted chain + token; customers must pay on the right rail.
What's the fee?
A flat platform fee per paid invoice (visible in the dashboard before you create the invoice). No monthly fee, no per-API-call fee, no minimum volume. The customer pays the chain's gas; that fee goes to validators, not Primeborg.
How do refunds work?
Refunds are an on-chain transaction FROM your wallet TO the customer's wallet. Primeborg cannot move funds back — only you can sign the refund. The dashboard offers a one-click refund flow that pre-fills the customer's original payment address and lets you sign from your wallet.
Do I need KYB to accept payments?
Not in v1. The merchant_verification_status field exists for future KYB enforcement, but defaults to verified for all signed-in users today. When KYB ships, it will be required for higher-volume merchants or for merchants in regulated jurisdictions; small-volume use will likely remain permissionless.