Getting Paid and Getting It Delivered: The Operational Half of Adult E-Commerce

Getting Paid and Getting It Delivered: The Operational Half of Adult E-Commerce

In short. Building an adult store is the part everybody plans for. The part that closes stores is the part nobody budgets: a card processor that accepts the category, a carrier that will carry the goods, and a returns policy that survives a product nobody can resell. Each of the three has rules specific to this category, and each has a failure mode that stops trade outright rather than merely slowing it. Below: how the money actually reaches you, how the parcel actually reaches the customer, and what to settle before either is a problem.

This page is about operations. For the storefront itself — catalogue structure, product pages, search and the build — see the complete adult e-commerce guide.

Why payment is the first constraint, not the last step

In mainstream retail, payment is a component you add near the end. Here it is the constraint that shapes everything before it, because the providers that serve ordinary shops decline this category as a matter of policy rather than on the merits of your business. Applying anyway costs weeks and, worse, a declined application on record.

What replaces them is the high-risk acquiring market, and it works on different terms.

⚠ The reserve is the number that catches people out. It does not reduce revenue, it delays it, which is a different problem and often a worse one: a store can be profitable on paper and unable to restock. Work out the delay before you plan inventory, not after.

Cash actually available this month = settled turnover − reserve withheld + reserve released from earlier periods
Working capital needed at launch ≈ reserve rate × expected turnover × holding period in months

The second line is the one to run before signing anything. A reserve that sounds tolerable as a percentage turns into a real sum once multiplied by the months it is held, and that sum has to exist somewhere while the store buys stock.

Reducing disputes before they happen

Disputes in this category have a distinctive cause: the purchase is private, and a charge the cardholder cannot place, or would rather not explain, gets disputed instead of queried. Most of the fix is presentational and costs nothing.

• Say the descriptor on the payment page. Literally: "this will appear on your statement as ___". It converts a future dispute into a decision made now.
• Make subscription and re-billing terms unmissable. Anything recurring — a subscription box, a membership — needs its renewal date and price stated where the customer is looking, not in the terms page.
• Answer fast and refund without argument. A refund costs the goods. A dispute costs the goods, the fee, and a point against the ratio that decides whether you keep the account.
• Keep delivery evidence. For physical goods, the tracking record is the whole of your defence.

Shipping: the constraint nobody reads until it bites

Payment failures are loud. Shipping failures are quiet: the parcel is refused, or held, or returned, and you discover the rule only after the customer complains. Three separate sets of rules apply, and they do not agree with each other.

The practical consequence is that the shipping destinations you can serve are narrower than the countries you can take money from, and the two lists must be reconciled in the checkout rather than in the head of whoever packs the boxes. A store that accepts an order it cannot legally deliver has created a refund, a dispute risk and an unhappy customer in one click.

Discretion is the other half. It is not a nicety here, it is a product feature: plain outer packaging, a sender name that says nothing, no branding on the label, and no itemised contents visible from outside. Say all of that on the product page, because the customer is deciding whether to buy from you partly on whether they trust the parcel not to embarrass them.

Returns: the category where the usual answer does not apply

Ordinary retail returns assume the goods can be resold. Intimate products generally cannot be, once opened, and consumer law in many places recognises this: sealed goods unsuitable for return on health or hygiene grounds are commonly exempt from the usual distance-selling right of withdrawal once the seal is broken.

⚠ That exemption is not automatic and not identical everywhere. It depends on your jurisdiction and your customer's, and it only works if the store is set up to use it. Which means, concretely:

• Goods ship sealed, and the seal is visibly a seal. No seal, no exemption.
• The policy is written before the sale, in plain words, on the product page as well as in the terms.
• Faulty goods are a separate path. A defective item is not a hygiene question, and treating it as one turns a warranty claim into a dispute.
• The policy is checked against the law where you sell, by someone qualified to do that. This page tells you the mechanism exists; it cannot tell you your rights.

Where the age gate actually belongs

In a content site the age gate guards the door. In a shop it has a second job: the sale itself may be age-restricted, and the moment that matters is checkout rather than entry. Two separate decisions follow, and conflating them is the usual mistake.

• At entry: a light confirmation, remembered, so browsing is not interrupted.
• At checkout: whatever the sale genuinely requires where you are selling, which may be more than a button.
• At delivery: in some places, age verification on handover, which is a carrier service you have to buy deliberately.

The compliance picture as a whole — age gates, records, data protection, payment rules — is covered in the legal compliance guide.

Signs the operational side was not planned

• The reserve was discovered after the first settlement rather than before signing.
• Checkout accepts addresses in countries you cannot ship to.
• The statement descriptor is a company name no customer recognises.
• Discreet packaging is real but is not mentioned anywhere a buyer would see it.
• The returns policy was copied from a mainstream shop and says nothing about seals.
• Nobody can say this week's dispute ratio without asking the provider.

What to settle before launch

• Written confirmation that every product category you sell is permitted by the acquirer.
• Reserve rate, holding period, and the working capital that combination requires.
• The descriptor text, and that it appears on the payment page too.
• The shippable-destinations list, enforced in checkout rather than by hand.
• Carrier rules for batteries and liquids, if the catalogue includes them.
• A returns policy written for sealed intimate goods, reviewed for the markets you sell into.
• A weekly view of the dispute ratio that you can read without asking anyone.

How adults.dev approaches it

We treat payment and delivery as design inputs rather than integrations bolted on at the end. In practice that means the checkout knows where it can ship before it takes the money, the store keeps its own record of every financial event rather than relying on the provider's dashboard, and the dispute ratio is visible on a screen instead of arriving as bad news.

Most stores that come to us already trade. The first piece of work is usually not the storefront at all — it is finding where the money is delayed, which orders should never have been accepted, and which disputes were created by the store's own wording.

Talk through payments and fulfilment:
Telegram: @adultsdev
E-mail: info@adults.dev