The complete guide to RUO peptide payment processing

How an RUO peptide merchant account works

Research-use-only (RUO) peptide payment processing is the business of accepting card payments for a disclosed research-product storefront. Your checkout sends payment requests through a gateway or another approved connection. The processor handles the transaction, and the acquiring arrangement determines how cleared funds are paid to your business under your agreement.

Begin with the sales channel you actually operate. A website checkout, a wholesale invoice, and a phone order can look different to a reviewer and require different setup. Describe who buys from you, where each order is placed, and how your business confirms, ships, and supports the order.

What underwriting reviews

Underwriting evaluates the legal business and owners, the proposed card activity, and the products and policies a customer sees. A reviewer may request records to verify the application, assess earlier processing, or understand a fulfillment arrangement. The details depend on the business and the proposed account.

• Identify the legal entity, trading names, operating domains, and contact person who can answer review questions.
• Describe your catalog, sales channels, customer base, shipping process, and refund and support workflow.
• Provide actual processing history when available. Label projections as forecasts and explain the assumptions behind them.
• Use the application or secure upload channel supplied by the reviewer for identity and banking records.

What to compare in written terms

Compare proposals against the same expected sales mix. Read the merchant agreement together with the pricing schedule, any gateway agreement, and any reserve or funding schedule. Clarify which document controls if the descriptions differ.

• Fees: recurring charges, transaction charges, statement and gateway fees, and any charges tied to refunds, disputes, or early termination.
• Cash flow: funding timing, batch cutoffs, reserve treatment, release conditions, and how adjustments appear in reporting.
• Scope: covered websites, product categories, channels, transaction sizes and volume limits, if any.
• Operations: who owns checkout setup, support escalation, settlement reports, and the process for changes after approval.

Go live with a checkout and reconciliation plan

Confirm the approved scope and technical setup before routing live traffic. Run the applicable provider-supported tests for a successful order, a decline, a void or refund, and an interrupted checkout. Confirm that payment status reaches the order system and that support can find the transaction using an order reference.

When the first real payments settle, reconcile the order, capture, settlement report, and bank deposit. Record fees, refunds, reserve movements, and any batch or funding differences. Set an owner for exceptions so the team can diagnose a missing deposit or a duplicate order promptly.

Keep the account current as the business changes

Keep the approved agreement, the current domain and catalog list, and a record of material changes in one place. Contact your processor or acquiring contact before a change when the agreement calls for review, and keep written confirmation of the scope and any conditions.

Bring a short business summary and a current website URL when you begin the Lunar Payments pre-application. The next questions depend on the business details, sales channels, and records you submit.