Peptide sellers are some of the businesses most often turned away by payment providers. A research supplier, a compounding pharmacy, and a clinic that prescribes peptides through telehealth sell very different things under very different rules, but they tend to meet the same answer: a declined application, or an account that is approved and later closed.
This post covers why that happens in general terms, how a peptide business can accept orders with 402pay by card and crypto in one checkout, how to release an order on a signed webhook, and how to keep the books straight. It also says plainly what stays with you, because a payment processor can't take that part on.
Why peptide sellers lose processing
Most processors and banks place peptides in a restricted category. The products sit close to drug, pharmacy, and supplement rules that differ by country and by state, and the same compound can be sold for research, under a prescription, or not at all depending on where the buyer is. A provider that holds your money takes on part of that uncertainty, so it prices it in:
| Declines | Many providers decline the category outright, before they look at the business itself. |
|---|---|
| Closures | Accounts that are approved can be closed after a review, often when order volume grows. |
| Reserves and holds | A provider that keeps the account may hold back a share of sales, or freeze the balance while it decides. |
No processor can change how the category is seen, and 402pay doesn't claim to. What you can change is how much of your money sits with someone else while a decision is made. Our post on payments for businesses processors turn away covers the wider pattern.
What stays with you
402pay processes payments. It doesn't review your catalog, your buyers, or where you ship, and it doesn't decide whether a product is legal where you sell it. Those decisions are yours:
- Labeling, including whether a product is sold for research use only and how that is presented.
- Prescription status, and the license, prescriber, and patient checks a prescription product needs.
- Which compounds you list, and which countries and states you ship them to.
- What your product pages say. Keep them free of health and treatment claims you can't support.
Our Unacceptable Risk Policy
Prescription drugs and controlled substances sold without the license or prescription the law requires are prohibited under our Unacceptable Risk Policy. If the rules for a product or a destination are unclear, ask a lawyer who knows them before you sell it.
Your wallet, not a held balance
Every payment arrives in a self-custody wallet whose keys stay in your browser, and every transfer out needs your password. 402pay holds no balance for you, so there is no reserve to build, no rolling hold, and no payout schedule to wait on. The money is in your wallet when the payment confirms.
Self-custody also means the recovery phrase is yours to keep, and nobody can reset it for you. Save it before your first order, as creating your wallet explains. Our comparison of self-custody and custodial processing covers the trade-off in full.
Cards and crypto in one checkout
Buyers don't all hold crypto, so one hosted checkout offers both. A buyer who chooses crypto pays in the coin and network they hold, to an address made for that checkout, with the rate locked for 15 minutes by default. A buyer who chooses card pays by Visa, Mastercard, American Express, Apple Pay, or Google Pay on a card provider's secure page.
There is no merchant account to apply for. 402pay routes each card payment to a card provider that serves the buyer's country, currency, and amount. The buyer may be asked to verify their identity there, and the provider delivers the payment to your wallet in crypto. If a card is declined, the buyer can try another provider without leaving checkout, and where no provider serves their region, they pay in crypto instead. A card payment costs nothing during the public beta, then 4% + 30¢ per transaction, and the provider may add its own fee, which checkout shows the buyer before they pay.
For a new business, the switch in Settings → Payments, under Card, starts on, and you can turn it off. The card help article covers availability, and card declines and retry routing explains what happens after a decline.
Release orders on a signed webhook
A buyer returning to your site isn't proof of payment. Release an order for packing when your server receives a verified, signed payment.succeeded webhook. A card payment completes when its transfer reaches your wallet, like any crypto payment, so the same event covers both.
Verify the signature before you trust the event, then fulfill once per payment, since a delivery your server doesn't accept is retried. Our posts on verifying webhook signatures and idempotency keys and safe retries cover both, and the accept a payment guide walks through the API.
Pack on payment.succeeded, once, and on nothing else.
Underpayments and references
Crypto buyers sometimes send a little less than the total, usually because an exchange took its withdrawal fee out of the amount. Your underpayment tolerance, 0.5% by default, decides what still counts as paid in full:
| Within tolerance | The payment succeeds as if it were exact, and you receive payment.succeeded. |
|---|---|
| Short by more | You receive payment.underpaid, and checkout asks the buyer for the rest. Hold the order until it succeeds. |
| Window closed | You choose to request the rest or accept what arrived, from the payment in the dashboard or through the API. |
For your books, create each payment through the API with your order number as its reference, up to 64 characters, and add up to 20 metadata pairs for anything else, such as a lot number or a sales channel. In Payments, Export downloads a CSV with each payment's reference, transaction hash, and customer. See underpayments and overpayments and reconciling crypto payments for the details.
A confirmed crypto payment is final, so a refund is something you agree to and send from your own wallet. The refunds and disputes article covers it. For how this looks for each kind of seller, see the pages for research peptides and SARMs, hormone therapy programs, and telehealth and online pharmacies.
Common questions
- Yes, for products and sales our Unacceptable Risk Policy allows. Buyers pay by card, Apple Pay, Google Pay, or crypto in one hosted checkout, and each payment lands in the seller's own wallet. The seller stays responsible for labeling, prescription status, and the law where it sells.
- No. 402pay doesn't review your catalog, your buyers, or where you ship. Research-use labeling, prescriptions, and the rules in each country and state you sell to are yours to follow.
- Yes, where a card provider serves the buyer's country and the order amount. There's no merchant account to apply for, the payment arrives in your wallet in crypto, and a buyer no provider serves pays in crypto in the same checkout.
- When your server receives and verifies the signed payment.succeeded webhook, once per payment. Hold an order whose payment is underpaid until it succeeds.
- No. Payments go to your self-custody wallet and 402pay holds no balance for you, so there is no reserve, no rolling hold, and no payout schedule.
See what 402pay can do for you.
Discover how 402pay helps your business accept any card and get paid in crypto, straight to a wallet you control.







