Skip to content

4 min read

Accepting payments for supplements and nutraceuticals

How supplement, nutraceutical, and beauty brands can accept card and crypto orders, ship on a signed webhook, handle reorders and disputes, and keep funds in their own wallet.

Capsules scattered beside a receipt, one capsule half greenCapsules scattered beside a receipt, one capsule half green
On this page

Supplement, nutraceutical, beauty, and wellness brands sell products people reorder, often to customers in many countries, and often through ads. Payment providers tend to treat that mix as high-risk, which shows up as stricter reviews, extra paperwork, and money held back.

This post covers why that happens in general terms, how a brand can accept orders with 402pay by card, Apple Pay, Google Pay, and crypto, how to ship on a signed webhook, and how to handle reorders, disputes, and finality without surprises.

Why these brands get flagged

A provider that holds your money takes on your risk, so it prices that risk in. For this category three things usually drive it:

DisputesCustomers who don't recognize a charge, or feel a product didn't match what they expected, may ask their bank to reverse it.
ReordersA repeat purchase the customer forgot about is one of the most common reasons for a dispute.
ReservesA provider worried about the first two may keep a share of your sales for a period, which slows your cash flow.

None of that goes away by switching providers, and no processor can promise it will. What you can change is how much of your money sits with someone else while it plays out. Our comparison of self-custody and custodial processing covers that difference.

One checkout for every way to pay

A brand's customers don't all pay the same way, so checkout shouldn't force one. A single hosted checkout accepts cards, Apple Pay, and Google Pay on a card provider's secure page, where the payment is converted and arrives in crypto. It also takes crypto in many coins and networks, with an address for each checkout. Linked processors work through Orchestration.

You start from a payment link, which needs no code, or from the API when your store creates a payment for each cart. While a customer pays, the rate is locked. If they send too little, checkout asks for the rest. Checkout shows in the customer's language, which helps a brand that ships across borders, and a customer who isn't the one paying can send a pay request so someone else does. Each paid order gets a receipt page the customer can keep and come back to, so there are fewer where's-my-order messages. See receipts for what it shows.

The product pages for nutraceuticals, collagen and beauty supplements, and herbal remedies show how this looks for each kind of shop.

Ship on a signed webhook

A customer returning to your site isn't proof of payment. Ship when your server receives a verified, signed payment.succeeded webhook, and your store never has to check orders by hand:

A row of five steps: the customer picks a way to pay, pays in checkout, the payment succeeds, a signed webhook reaches your store, and the order ships.A row of five steps: the customer picks a way to pay, pays in checkout, the payment succeeds, a signed webhook reaches your store, and the order ships.
The webhook is the signal to ship, whichever way the customer paid.

Verify the signature first, then fulfill once per payment, since a webhook can be delivered more than once. Our posts on verifying webhook signatures and idempotency keys and safe retries cover both, and the accept a payment guide walks through the API.

Reorders without a subscription

402pay has no subscriptions and no recurring billing, so nobody is charged again unless they choose to pay. For a brand that sells a product people run out of, that means sending a payment link for each reorder: by email, by message, or from a reminder when a bottle should be running low.

Treat that as a plus. A customer who pays on purpose each time can't say they didn't sign up for it, which is how many disputes in this category start. The cost is one extra step for the customer, so make the link easy to find and the reminder timely. Our guide to payment links covers sharing them, and payment links versus API checkout helps you decide when to move to the API.

Every reorder is a payment the customer chose to make.

Disputes, refunds, and finality

A card payment is backed by a card, so the cardholder can dispute it with their bank, as with any card payment. You'll be asked for evidence if they do. A crypto payment is final: once it confirms, nobody can reverse it, so a refund is something you agree to and send yourself. Either way, refunds are sent from your wallet, in the coin and amount you choose. The refunds and disputes article walks through both.

The best defense against a dispute is a customer who knows who to call and what they bought:

  • Use clear product names in each link's name and description, in words customers will recognize on a statement.
  • Publish a refund policy on your site, where the customer sees it before they pay.
  • Add a support email to your business profile, so customers come to you before their bank.

Keep your claims honest

Describe your products accurately and don't overstate what they do. Misleading claims are against our Unacceptable Risk Policy, and they also bring disputes. 402pay doesn't review what you say about a product, so that responsibility is yours.

Your wallet, with no reserve

Payments arrive in a self-custody wallet whose keys stay in your browser, and a transfer out needs your password. 402pay holds no balance for you, so there is no reserve to build and no payout schedule to wait on. The money is in your wallet when the payment confirms.

A card payment costs nothing during the public beta, then 4% + 30¢ per transaction, on your fee statement and never taken out of the deposit. The zero-fee beta waives it for now. The pricing page lists every fee. For the product in one place, see the supplement payments page, and for how card payments reach you, card payments from day one.

Common questions

  • Yes, for products and claims our Unacceptable Risk Policy allows. Customers pay by card, Apple Pay, Google Pay, or crypto in one hosted checkout, and each payment lands in the brand's own wallet.
  • No. There is no recurring billing. A brand sends a payment link for each reorder, so the customer chooses every payment.
  • Yes. A card payment is backed by a card, so the cardholder can dispute it with their bank, and the business is asked for evidence. Clear product names, a refund policy, and a support contact help.
  • No. Crypto payments are final once they confirm. If you agree to a refund, you send it from your wallet.
  • When your server receives and verifies the signed payment.succeeded webhook, not when the customer returns to your site.
  • No. Payments go to your self-custody wallet and 402pay holds no balance for you, so there is no reserve or 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.