First RUO Account: No Payment History

Can you request review before your first sale?

Yes, you can ask for a startup review. Pine Payments explicitly discusses new peptide stores without processing history in its startup guide. That is a provider-specific example of an available review conversation, not evidence that every RUO business qualifies or that MerchantBridge has a relationship with that provider.

MerchantBridge analysis: the useful question is whether a prospective provider will evaluate your actual catalog, buyer model and launch stage. A request for processing statements should prompt an honest explanation that none exist. Do not submit another business's statements or describe a sales forecast as completed transactions.

Sources: Pine Payments: How to Start a Peptide Business and Sell Online: A 2026 Guide; Stripe: Prohibited and Restricted Businesses List FAQs; MerchantBridge Advisors: RUO Peptide Merchant Account Readiness Checklist

Build a forecast the reviewer can understand

Start with estimated order count and average order value for a stated period. Explain the basis: planned inventory, an existing business audience or an intended marketing launch, for example. Identify assumptions that have not been tested. A projection is useful because it describes the requested account capacity; it does not prove demand.

Consider a hypothetical prelaunch seller estimating 80 orders at $125 each in its first full month. That produces a $10,000 monthly forecast. The submission should say that all three figures are estimates and explain what the order total includes. These numbers are an illustration, not an approval threshold or a forecast for your store.

• Give a launch date or target window and label it tentative when appropriate.
• Separate an average order estimate from the largest order you expect to accept.
• Describe any planned ramp in volume and the assumptions behind it.
• If another business activity already has sales, identify it separately rather than blending its history into the new RUO operation.

Show what exists today and what is still planned

Prepare a short status note alongside the website. For example: catalog loaded; shipping policy complete; buyer verification designed but not yet active; checkout awaiting provider review. This gives a reviewer a clearer picture than calling an unfinished store ready to process.

Stripe's peptide FAQ illustrates why the buyer model matters: its research-peptide guidance calls for preventive measures against purchases for nonresearch purposes. This is Stripe's policy, not a universal approval checklist. Explain your actual controls and ask the proposed provider what it needs to assess them. An RUO label alone is not evidence of lawful sales or payment eligibility.

Use a short startup brief for the first inquiry

MerchantBridge analysis: a useful opening brief might read, "We are a prelaunch U.S. research-product seller seeking our first card-processing review. Our catalog is available at the supplied website. We intend to sell to identified research buyers, with the proposed screening process described below. Monthly volume and ticket sizes are forecasts. We have no processing statements for this business." Adapt every detail to the facts.

Add the actual entity location, intended destinations, fulfillment plan and checkout platform. The broader RUO readiness checklist covers website and business preparation; this startup brief explains the missing-history portion. Begin with business basics and provide sensitive supporting records only through a requested private upload.

Confirm the next stage before committing to launch

Ask which items can be assessed now, which must be completed before onboarding and whether another review is needed after the site is ready. Confirm the proposed payment method and exact integration before paying for implementation. A conversation, a submitted application and an approved live account are different milestones.

Keep a list of unresolved items with an owner and completion date. Ask the provider to explain any proposed volume limits, funding terms or additional documentation in writing. The absence of processing history does not justify a promise of approval, a launch deadline or particular account terms.