Approval starts with a coherent business file
A peptide merchant application is strongest when the reviewer can connect the company, catalogue, product presentation and customer payment flow. Sending a folder of laboratory reports without that connection leaves important questions unanswered. At eLotPay, we assess eligible peptide businesses around the actual products and operating model. This guide provides a practical preparation framework: build one traceable record for each product, then connect those records with the wider business application. Documentation supports an assessment; it does not guarantee acceptance or establish permission to sell a product.
Use a product-to-payment evidence chain
Organise the file around five links: the seller, the product, the supplier, the customer promise and the transaction. For each item, identify the catalogue reference and the records supporting those links. A reviewer should be able to move from a website listing to the relevant supplier and batch information without guessing whether documents concern the same item. This is an organisational framework, not a universal acquirer checklist. The selected provider may request different or additional information after reviewing the business.
1. Establish the seller and the sales territories
Prepare the legal entity information, ownership details and business website. Identify who contracts with the customer, where stock is held and which countries you intend to supply. Separate the entity country from customer locations. If another company fulfils orders or handles part of the sale, explain its role. Include relevant permissions for specialist review rather than assuming that incorporation establishes product eligibility. Keep customer terms and payment-account details consistent with the seller described in the application.
2. Build a catalogue register before attaching reports
Create a simple register with one row per product: internal reference, public product name, supplier, available batch references, website address and intended customer category. Add the document owner and review date. Distinguish active listings from planned additions. If one laboratory report supports only a specific batch, do not silently extend it to every item with a similar name. Where a record is missing or outdated, mark the gap and investigate it. Clear exceptions are more useful than an apparently complete file built on unsupported assumptions.
3. Explain what each laboratory document establishes
For available test reports, record the issuing organisation, date, tested sample or batch and the stated scope of testing. Check that the identifiers correspond to the stock and catalogue being reviewed. Maintain the original document alongside your register so the reviewer can inspect its limitations. A report about a sample is not, by itself, proof of regulatory approval, lawful marketing or suitability for human use. Present evidence for what it actually says, and obtain qualified advice where the product classification or applicable permissions require interpretation.
4. Review the complete product presentation
Compare labels, product pages, advertising and customer communications. A disclaimer should not be treated as a substitute for reviewing the overall presentation. In its 31 March 2026 Gram Peptides warning letter, the FDA explained that evidence on the seller’s website supported its intended-use assessment despite research-use disclaimers. That is a specific enforcement example, not a ruling on every peptide business. The practical lesson for an application is to supply an accurate account of the business, not to conceal intended use or change wording merely to obtain processing.
5. Connect the order with fulfilment and support
Describe the purchase journey from checkout to dispatch and delivery. Identify the information available when a customer reports a missing shipment, incorrect item or refund issue. Connect the order reference with the transaction, product and relevant fulfilment record. State realistic shipping territories and timelines. If a supplier dispatches directly, explain how your team obtains evidence and resolves exceptions. Payment review concerns the operating promise as well as the catalogue: a document file should show how the merchant can investigate what was sold and delivered.
A worked preparation example
Consider a fictional merchant listing twelve products from two suppliers. It holds several reports, but some use supplier names that differ from the store’s catalogue names. Instead of submitting the reports as an unlabelled bundle, the merchant builds a cross-reference register and asks suppliers to clarify the identifiers. It marks two planned products as outside the current application and records an unresolved batch-document gap. The resulting file does not make those products acceptable automatically. It makes the application intelligible and prevents an unresolved item from being presented as already reviewed.
Keep commercial requirements separate from product evidence
Alongside the product file, state expected monthly volume, typical order values, customer countries, payment methods and settlement currencies. Explain existing processing history and previous restrictions candidly. New businesses should distinguish forecasts from observed activity. The product evidence and commercial brief answer different questions; neither replaces the other. Review processing fees, reserves, settlement conditions and integration scope in the written proposal. Do not commit fulfilment or advertising budgets on the assumption that document submission has already produced an approved account.
Frequently asked questions
Does a certificate of analysis guarantee approval? No. It can support a product review, but the entity, catalogue, presentation, markets and provider requirements still need assessment. Is a research-use label sufficient? No label should be treated as a complete eligibility determination; the full business presentation matters. Can an approved merchant add products freely? Confirm the change process in the agreement and review material catalogue or market changes before introducing them. Should identity documents go in the initial brief? No. Confirm the reviewing party and secure onboarding channel before sharing sensitive records.
Start with a business-specific assessment
We offer payment solutions for eligible peptide merchants and review the business behind the transaction. Prepare a concise entity and market summary, a catalogue register and the relevant supporting records. Use our peptide merchant account page to understand our service approach and our assessment brief to organise your requirements. The brief downloads to your device; it is not submitted online. Eligibility, provider availability and final terms remain subject to individual underwriting and applicable requirements.
Sources and related services
Official source reviewed 30 October 2026: FDA: Gram Peptides warning letter, 31 March 2026. This article provides application preparation information, not medical-use instructions or a product-specific legal opinion.