Link
Send a URL. That is the whole integration.
Send it. Your customer pays by card, bank transfer or a local method. You settle in USDC, final on-chain.
Cards get disputed weeks after you shipped the order, and the chargeback comes straight out of money you already spent. A rolling reserve holds back a slice of every sale, just in case.
Getting approved to accept payments at all can mean a KYC gauntlet before your first sale, then a decline with no real reason after it.
Five steps, and you only build the first one.
Send a URL. That is the whole integration.
Card, bank transfer or a local method, on the hosted checkout.
The paid state is checked against the payment processor's own servers before anything trusts it.
USDC lands in your payout wallet. Settlement is final on-chain.
Your own system hears about it the moment it settles, signed so you can trust it.
Every step is server-verified. The upstream callback is never trusted by itself.
Live demo
This is a real payment lifecycle, not a mockup. Keep scrolling and watch it move from created to paid to sent, with the webhook firing at the end.
See every link, every status, every payout, without asking anyone. Nothing here needs a support ticket.
2 percent platform fee, no monthly fee.
Drop the plugin in and start taking payment links from your own store. Download the plugin
Every paid state is checked against the payment processor's own servers before your dashboard shows it.
USDC lands in your wallet without a rolling reserve holding part of it back.
Put the checkout on a domain your customers already know.
The facts
Create a payment link from the dashboard, the API or WooCommerce.
Send it to your customer.
Your customer pays on the hosted checkout by card, bank transfer or a local method.
USDC lands in your wallet and a signed webhook fires.
Card (Visa, Mastercard, Maestro), Apple Pay, Google Pay, SEPA and ACH bank transfer, and local methods where available. The methods on offer depend on the customer's country and the amount; the checkout picks them automatically.
| Platform fee | 2% of each payment |
|---|---|
| Monthly fee | None |
| Setup fee | None |
| Rolling reserve | None |
| You receive | 97% of each payment. The remaining 1% is the payment provider's. |
| Minimum payment | Varies by payment method. The lowest is around 2 USD; some methods start much higher. |
| Settlement | USDC on Polygon, sent to your own wallet. |
Download the plugin and upload it to your WordPress site.
Create an API key in your StealthPaid dashboard and paste it into the plugin.
Copy the plugin's webhook URL into your dashboard, then copy the secret it gives you back into the plugin.
Choose the order status to apply once a payment is confirmed paid.
Save, enable the gateway, and test with one small order.
No. Your customer pays by card, bank transfer or a local method. You receive USDC automatically; you never have to buy or hold any yourself.
It is the USDC (Polygon) address your settlements are sent to: any wallet you control that supports USDC on the Polygon network. Set it once in your dashboard before creating your first link.
Settlement happens on-chain within seconds of your customer's payment being verified server side. There is no rolling reserve holding part of it back.
No chargebacks: settlement is final on-chain. There is no refund flow through the platform, so a refund is something you arrange with your customer directly.
A payment that arrives below 98% of the amount you charged settles as underpaid rather than paid. You still receive the funds that came in; your dashboard and webhook show the amount received against the amount expected so you can decide how to proceed.
You can price a payment in 22 currencies. Which payment methods a given customer sees depends on their country and the amount; the checkout selects among them automatically.
No. Creating a StealthPaid account and setting a payout wallet is the whole setup; payment processing is already part of your account.
We retry delivery at 1 minute, 5 minutes, 30 minutes, 2 hours, 12 hours and 24 hours, about 39 hours in total. You can also read a payment's status directly from the API at any time, so a missed webhook never leaves you without the answer.
Settlement is final on-chain, so refunds are handled by you, off the platform, not by StealthPaid. We would rather say that plainly here than have you find out at the worst moment.