Stripe froze payouts this morning, and the store is still live. Dropshipping payment processing fails in that window because a late supplier and a mismatched listing already turned yesterday’s sales into disputes. The cardholder never heard of the store name on the statement.
That’s the search owners type while ads keep spending. The cart still takes cards until the processor kills the keys. The supplier still wants payment for the last batch. The risk engine has already decided the file looks like open exposure.
Open Sign Payments is an ISO. We place the file with an acquiring bank that boards this category. The bank underwrites it and settles the funds. If no acquirer we know of will take the file, we tell you that.
Why dropshipping files get frozen
An aggregator freezes a dropship store when disputes, refunds, and where-is-my-order tickets cluster around the same SKU and the same warehouse. You charged the card. A third party packed the box. The bank still pays the chargeback if the buyer never gets what the listing promised.
The freeze is a cluster. A Shopify store sells a blender as ships in three to five days. The overseas supplier prints a label on day twelve. The product page uses a studio photo. The unit that arrives is a cheaper mold with a different plug. One buyer files item not received. Two more file item not as described. The risk model reads the pile and pauses payouts.
Why Stripe and Square close accounts follows the same logic. Those platforms underwrite a shared pool. They’re built around merchants who pick, pack, and scan their own inventory. Dropshipping puts delivery in someone else’s warehouse. The account can go dark overnight. Nobody from underwriting calls to walk the supplier delay with you.
Category makes the cluster worse. Phone gadgets, beauty devices, fitness gear, and bottles with supplement-style claims already draw more not-as-described disputes than a shop selling its own stock. A long ship window on a week of heavy ads moves that dispute load fast.
PayPal can hold funds for up to 180 days when an account is limited or closed. That ceiling sits in the PayPal User Agreement. It’s a maximum PayPal may apply. If Stripe closed the account with a balance, treat the morning as a records morning. Save the email, the payout export, and the dispute list. Then read what to do when your processor drops you before you paste the API keys into another aggregator.
A termination for cause can also land the business on the MATCH list. Mastercard’s database of merchants terminated for cause stays for five years from the date the acquirer adds the listing, then Mastercard purges it automatically. Only the acquirer that placed the listing can remove it sooner, and only in the cases Mastercard publishes. Stripe walks through that process in its MATCH guide. Paying a removal vendor doesn’t move the record.
Pause the ads that still charge cards you can’t capture. Keep shipping and refund policies up for buyers who already paid. Opening a second aggregator on the same catalog, the same ads, and the same warehouse is how a bad week becomes a MATCH problem.
Delivery time, supplier, and the cardholder
An underwriter reads three clocks on a dropship file. How long the listing says shipping takes. How long the supplier actually takes. How long the cardholder waits before calling the bank.
Delivery time is risk because the bank eats a chargeback if the buyer is gone and the product never showed. A long ocean shipment is a long window for never-received disputes. A dispute already filed stays filed after tracking finally appears. The supplier’s warehouse is the real fulfillment desk. If that warehouse substitutes a SKU, ships without a tracking ping, or goes quiet during a holiday, your dispute load moves. You never touched the box.
The cardholder is the person who files. They bought from a Facebook ad or a TikTok shopfront that used a brand name. The charge posts as a billing descriptor they don’t recognize. They call the issuer printed on the card. That path is faster than emailing your support alias. A descriptor that matches the live store name and the ad keeps more of those calls from starting. A random DBA on the statement sends the buyer to the issuer. The same mechanics sit in how the billing descriptor drives chargebacks.
Supplier identity is the other half of delivery. “We use a few marketplace sellers” is a file an underwriter can’t price. Name the agent or the warehouse. Name the country the carton leaves. Say whether you inspect product, or whether the first time you see it is a customer review. Say what happens when the supplier is out of stock: cancel and refund, or substitute. Substitution is how not-as-described spikes.
The listing has to match the unit. If the page says stainless steel and the carton is plated plastic, the dispute writes itself. If the page says in stock, ships today, and the factory is on backorder, the cardholder has a calendar. Underwriters open the live URL, read the advertised ship window, and sample recent tickets. They’re asking whether upcoming volume will look like the week that froze the last account.
Customer support sits on that same clock. A tracking link on the day the label prints, a delay email when the warehouse slips, and a refund that actually posts, keep some buyers off the issuer’s phone. Silence during a long transit is how a paid order becomes a dispute the bank already funded.
What to put on the application
Write the business the way the store actually runs. Dropshipping is the fulfillment model. Say that. An underwriter who finds a third-party warehouse after you described in-house stock treats the rest of the file as untrustworthy.
Put these on the application as they exist today.
- You dropship. A third party ships each order, and you don’t hold that inventory yourself.
- You name the supplier or agent, the country they ship from, and the delivery window printed on the product page.
- You name the products as the live site names them, with the real photos and the real claims, including subscriptions if you rebill.
- You attach the shipping policy, the refund policy, and a payout or statement export from the closed aggregator account.
The closed account is part of the story. Bring the termination email, the reason they gave, the dispute codes, and the refund volume. If payouts are sitting, say so. Hiding a Stripe or PayPal close ends a review faster than the close itself. If MATCH is in play, say that too. Only the acquirer that added a listing can take it off, and only in the cases Mastercard allows.
Don’t recast the catalog to look like a safer shop. Don’t split the same ads across new legal entities to duck a monitoring program. Don’t describe a supplement as a wellness accessory because a friend said the category would read easier. Honest disclosure is the only version of this file that survives a live-site check.
Volume should match ads and fulfillment. A store that processed a quiet month and then bought a traffic spike will look like the surge an aggregator already punished. Explain the spike. Name the offer that drove it. Name whether the supplier kept up.
We read that package with you and tell you what an underwriter will see. We place the file. The acquiring bank decides. A merchant sees the full schedule, including any reserve, before signing. A reserve exists because the bank eats a chargeback on a store that disappears after the ads stop. Dropshipping, with its lag between charge and delivery, is the shape that reserve is built for.
A dedicated account after an aggregator close
After an aggregator close, the next structure is a dedicated merchant account with an acquiring bank. That’s a payment aggregator versus a merchant account decision, and it matches this model. The bank issues the account, underwrites the dropship file, and settles funds. You’re a named merchant inside that bank’s book.
The Shopify store can stay. Checkout is still the cart. The frozen piece is the processor behind the pay button. For how Shopify talks to a processor that will board a harder category, see high-risk payment processors for Shopify. This morning is the freeze, the supplier, and the cardholder.
A dedicated account still carries risk terms. The bank may set a reserve. The bank may ask for supplier invoices, tracking samples, and a written chargeback process before live volume. Funding follows the acquiring bank’s underwriting and the signed schedule.
| What the bank looks at | Aggregator | Dedicated merchant account |
|---|---|---|
| Who underwrites the store | A shared risk pool and an automated model | An acquiring bank reading this file |
| How a freeze starts | An overnight hold, often with a form email | A review, usually with a person attached |
| Dropshipping on day one | Easy to skip in a short signup | Written on the application as the fulfillment model |
| After a close | Payouts can sit while the platform investigates | Settlement follows the schedule the merchant already signed |
High risk dropshipping processing is the label on a file the bank agrees to read as dropshipping. A dropshipping payment processing application that names the supplier, the ship window, and the live catalog is the one that gets a fair reading. A new aggregator login with the same ads and the same warehouse is how the second freeze starts.
If we can’t place the file with any acquirer we know of, we say no. That’s the honest outcome on a catalog we can’t board, a MATCH record an acquirer won’t touch, or a fulfillment story that still doesn’t match the site.
Frequently asked questions
Why do dropshipping stores get frozen by Stripe or PayPal?
Disputes and refunds cluster when a supplier ships late or the product doesn’t match the listing. Aggregators run a shared pool and can pause the account overnight when that cluster appears. The cardholder who doesn’t recognize the statement name files faster than your support queue can answer.
Do I need a dropshipping merchant account after a freeze?
A dedicated merchant account is the structure that matches this model after an aggregator close. An acquiring bank underwrites the file as dropshipping. Open Sign Payments places that file. The bank decides whether to issue the account.
What does an underwriter want from my supplier?
A named warehouse or agent, the country the carton leaves, the advertised delivery window, and proof that the live listing matches the unit that ships. Tickets, tracking samples, and a written substitution policy tell the same story. A vague stack of marketplace sellers doesn’t.
Can I leave dropshipping off the application and fix it later?
No. Describe the fulfillment model as it runs. An underwriter who finds a third-party shipper after an in-house story will treat the file as misrepresented. That path ends the review.
What happens to money still sitting in Stripe or PayPal?
Follow the platform’s close process and keep every email. PayPal’s User Agreement lets PayPal hold funds for up to 180 days when an account is limited or closed. That’s a maximum they may apply. Stripe’s remaining balance follows Stripe’s own close and dispute process. We don’t hold those funds. The platform that froze you does.