72 Hours After Your Peptide Merchant Account Is Frozen

The moment you see the email: your merchant account is frozen. You cannot process payments. Orders are piling up. Customers are messaging with questions. Your cash flow stops. This is exactly when you need to act fast, strategically, and without making things worse. Most guides tell you why accounts get frozen: high chargebacks, suspicious activity, or processor errors. Nobody publishes what to DO in the critical first 72 hours, which can mean the difference between recovering quickly or facing weeks of chaos. This guide is for operators mid-crisis, with a clear recovery sequence designed to minimize damage and get operations back on track.

Hour 0 to 6: Document Everything, Do Not Call the Processor Yet

Your first instinct is to pick up the phone and call your processor. Resist it. The moment you are notified of a freeze, your priority is preparation, not communication. Here is what to do in these first few hours.

Document everything immediately. Gather all recent transaction records, customer data, chargeback details, and any communications from the processor. Save copies securely. If there was an email notification, preserve it with timestamps. Documentation is your lifeline during disputes.

Identify funds held and the hold duration. Check your account dashboard to see exactly how much money is frozen and for how long. Processors often outline this in their notifications, but confirm every detail you see there. Some freezes are 7-day holds; others involve rolling reserves that last months. Verify the exact structure of whatever hold applies to your account. Note the figures: the frozen balance, the hold duration, and any stated conditions for release.

Do not call the processor yet. Processors often provide generic responses or stall when contacted emotionally. Your first contact should be strategic, prepared, and supported by evidence. Wait until Hour 6 to make contact, after you have gathered your documentation. Every minute counts, but acting without preparation will cost you later.

Hour 6 to 24: Determine Whether This Is a Freeze or a Termination

By Hour 6, you should have a clearer picture of the situation. The most important distinction is whether this is a temporary freeze (a hold pending review) or an account termination. These require entirely different responses.

Freeze indicators: The processor has placed a temporary hold pending review. They may have flagged an unusual activity spike, elevated chargebacks, or a compliance flag. They will usually request documentation within 7 to 10 business days. A freeze is typically reversible with evidence.

Termination indicators: The processor has closed your account. The notification language will say something like "account closed," "relationship terminated," or similar. Terminations involve a separate question: what happens to funds already processed. This depends on your processor agreement. Common structures involve a rolling reserve held for a set period after termination, but the exact duration and percentage vary by processor and agreement. You need to read your actual processor contract for the specific terms that apply to your account.

At this stage, contact the processor in writing. State that you have received the notification, that you are gathering documentation, and that you want written confirmation of the account status, the amount and structure of any hold, and the timeline for resolution or fund release. Keep every exchange in writing from this point forward.

Hour 24 to 48: Freeze Path and Termination Path Diverge

If You Are on the Freeze Path

Prepare the documentation package the processor will request:

• Proof of order delivery for disputed transactions (tracking records, carrier confirmations)
• Customer communication logs showing you fulfilled the orders
• Any fraud prevention measures you have in place (address verification records, CVV match logs)
• Evidence that your product labeling and sales process complied with your stated RUO requirements

When you submit documentation for chargebacks: provide counter-evidence for each dispute individually. Show proof of delivery, customer order confirmation, and any records showing the customer received what was ordered. Processors evaluating a freeze want to see that individual disputes have factual counter-evidence, and that your operations as a whole carry acceptable risk.

Processors look for specific signals in the documentation package, not just the aggregate chargeback count. The dispute pattern matters as much as the rate. A cluster of disputes from a single fulfillment window points to a logistics failure. Disputes spread across months with no common product or shipping window point to a different problem. Provide a breakdown showing the distribution of disputes, not just the total, so the reviewer can see the structure of your situation clearly.

For each individual dispute you are contesting, the standard for adequate chargeback defense documentation is higher than many operators expect. A complete response package for each dispute should include: the original order confirmation with timestamp, proof of delivery with a carrier-level tracking scan at the delivery address, and the product description the customer saw at checkout. If the customer contacted your support team before filing the dispute, include those communication records in full. If they filed without contacting support first, note that explicitly, because it is material to the dispute assessment. Processors also look for evidence of your fraud prevention controls: address verification match records, CVV verification results, and IP consistency data where available. A dispute where your screening data shows strong positive indicators is significantly easier to contest than one where screening data is absent or incomplete. Response windows are short, typically 7 to 30 days depending on the card network and the dispute reason code, so have this documentation assembled before you submit, not assembled in response to a second request from the processor.

What not to do during a freeze dispute: Do not admit fault in writing. Do not offer blanket refunds as a settlement tactic without understanding how the processor will interpret it. Do not ignore documentation requests or miss the stated deadline for submitting evidence.

If You Are on the Termination Path

Read your processor contract for the rolling reserve clause. This is the clause that governs what percentage of processed funds are held post-termination and for how long. The specific percentage and duration vary by processor and by your individual agreement. Contact the processor in writing to get confirmation of the exact reserve structure that applies to your closed account.

For customers who have pending orders: you are still obligated to fulfill or refund them, regardless of the processor situation. Map out which orders are in transit, which are unfulfilled, and what the refund exposure is. If you have any accessible funds, prioritize fulfilling orders that are already packed and ready to ship. For refunds you cannot immediately process through your frozen account, contact the processor to ask whether customer refunds can be initiated against the held reserve. Get the answer in writing.

Hour 48 to 72: Engage Your Backup Processor and Communicate with Customers

On backup processor activation: If you had a second merchant account already in place, activate it now. Test a small transaction before routing live customer orders through it. If you did not have a backup processor in place before this crisis, understand this clearly: the 48-to-72-hour window is not enough time to get a new high-risk merchant account approved from scratch. Application processing for peptide merchant accounts takes time. You are likely looking at fulfillment gaps regardless. The correct lesson for after this crisis is that a second processor should have been active and tested before any freeze occurred.

If you are in the application process with a second processor right now, be straightforward in the application: provide complete documentation, a complete chargeback history, and complete compliance records. Incomplete applications extend approval timelines.

Communicating with customers: Be factual and calm. Tell them there has been a payment processing issue affecting your ability to ship or refund on the normal timeline. State the revised timeline you expect. Do not blame the processor by name. Do not make promises about timelines you cannot confirm. If you have customers with unfulfilled orders and no path to fulfillment in the immediate term, issue refunds to the extent you can and document each one.

When drafting the customer message, use language that is factual without creating additional liability. A workable structure: "We are currently experiencing a payment processing interruption that has temporarily affected our ability to ship and process refunds on our standard timeline. Your order is recorded, and we will provide you with an update by [specific date you are confident you can meet]." This language is factual, does not name the processor, does not concede fault, and does not make promises about funds you have not confirmed access to. Avoid generic terms like "technical difficulties" without more context. Customers interpret vagueness as evasion and file disputes faster than they file complaints.

If a customer asks directly whether you can process refunds right now, tell them refund processing is temporarily affected and give a specific date only if you are confident you can meet it. If you cannot confirm a date, do not offer one. A missed refund date generates a second dispute. A delayed but accurate date does not. For customers requesting cancellations: honor each request in writing and document it. Even if you cannot process the refund immediately through your frozen account, a written cancellation confirmation creates a record that the customer agreed to wait, which is material if a dispute is filed later.

After 72 Hours: Dispute Prevention and Operational Upgrades

Once the immediate window has passed, the priority shifts to making sure this does not happen again.

Dispute prevention: Review your chargeback rate. If it was elevated before the freeze, the root cause matters more than the rate itself. Common operational sources are unclear product descriptions, unclear RUO labeling, shipping delays that generate disputes, and customer service response gaps. Fix the underlying cause, not just the rate.

Documentation upgrades: Every transaction should have a retrievable record: order confirmation, tracking, carrier scan, and customer communication. When a dispute is filed, the response window is short. If your documentation system requires manual hunting across inboxes and spreadsheets, build something that lets you pull a complete transaction file in under five minutes.

Backup processor setup: If you did not have a second processor before this crisis, set one up now, before you need it. This means applying, getting approved, integrating the gateway, and running test transactions. A backup processor that is not tested is not a backup.

Setting up a second peptide merchant account from scratch requires a complete documentation package prepared before you submit the application. Processors underwriting high-risk accounts will ask for: three to six months of processing statements from your primary processor, a current chargeback ratio report, your product catalog with research-use labeling documentation for each SKU, your fulfillment process documentation, and a summary of the fraud prevention controls you have in place. Submitting an incomplete application does not move faster. It generates a documentation request that comes back days or weeks later, extending the overall approval timeline by exactly that delay.

After approval, integration requires its own time and testing. The gateway connected to the second processor needs to be integrated with your checkout system, tested end-to-end in a staging environment, and verified against live test transactions before you route real customer orders through it. Once integrated, run a small volume of real transactions through the backup account each month to keep it active. A high-risk account that sits idle for months with no transaction volume may be reviewed or closed when you suddenly route high volume through it during an emergency, which is the exact scenario a backup account is supposed to prevent.

Reserve monitoring: If your account was terminated and you have a rolling reserve outstanding, log the hold amount, the hold start date, and the expected release schedule. Follow up in writing on the stated release dates. Processors do not always release reserves automatically on the expected date.

If you are rebuilding your payment processing setup from the beginning, the guide at /start walks through the full process for establishing new operations, including processor selection, documentation requirements, and chargeback management baselines specific to research-use-only peptide storefronts.