Quick Answer
Describe a rip site by its five elements: prepaid credit, a randomized outcome, delayed physical fulfillment, stored balances and buybacks. Pair each with the policy that controls it, not a trading-card retail label.
That wording gives the application its best chance of boarding on the first pass instead of being re-rated later. Rate is the smaller question. As one 2023 r/sales commenter put it, "Every business already has credit card processing," so a cheaper quote alone rarely moves anyone. Fit does. And fit starts with the first sentence of your business description.
Key Points
- SeamlessChex's underwriting team said in September 2026 that processors price prepaid credit, a randomized outcome, delayed physical fulfillment, stored balances and buybacks, not trading cards.
- The April 2026 Visa Core Rules require the acquirer to assign the MCC "that most accurately describes its business," and that code influences interchange and other fees.
- Scaleupally's 2025 fee guide described processors holding 5-20% of transactions for 6 months or longer, with high-risk merchants facing chargeback penalties at just 0.5%.
A rip site's application is judged by how the money moves, not by the cards on the table.
For a rip site, the costly failure is rarely the rate. It is an account boarded as a card shop that gets re-rated, held or closed once the real model surfaces.
Conventional wisdom says merchants change processors to save on fees. The evidence points somewhere else. In a 2023 r/sales thread, a rep in a large bank's merchant processing department said they had sold one account in 2 years after handing out 10+ bids, each showing thousands of dollars a year in savings. Another commenter in that thread noted that prospects often carry a competing bid back to their current processor just to get their own rate cut.
Savings, on their own, rarely move a merchant. Stability does.
A rip site has more reason than most to think this way. In my view, the decision that matters is whether the processor understands what it is actually boarding: prepaid credit, a randomized outcome, delayed physical fulfillment, stored balances and buybacks. Processors that already board platforms shaped like Courtyard or Rips by Triumph have seen that combination before, while a processor that has only ever priced hobby retail will meet it for the first time at review. Leave one element out of the application and the gap tends to surface later, when customer balances are already sitting on the platform and cards are already promised.
That is the cost worth avoiding.
So the rest of this piece works on the wording itself: one plain sentence for each element, the policy that controls it, and the reserve, hold and dispute terms to confirm before anything gets signed, starting with what an underwriter is really pricing when your application lands on the desk.
Most rip-site operators fill in the business description field the way a hobby shop would. Trading cards, collectibles, sealed product. It feels accurate. To an underwriter, it describes a different business.
A card rip, mystery-pack or live break platform moves money in a pattern no card shop shares. The customer funds a balance first, buys an outcome they cannot choose, waits for a card that ships later or sits in a vault, and may sell that card back to the platform for credit. SeamlessChex's underwriting team breaks that pattern into five elements: prepaid credit, a randomized outcome, delayed physical fulfillment, stored balances and buybacks. Courtyard and Rips by Triumph are two public examples of the same shape.
My argument in this guide is simple, and it starts with one question: which of the five does your platform actually run, and what written policy controls each one? The research section below walks through what happens when they go unsaid.
What follows is how the underwriter reads each element, what goes wrong when the description misses them, and the wording I would put in front of a reviewer instead, line by line, starting with the question every acquirer asks first.
Questions this article answers
What does an underwriter actually price on a rip site?
An underwriter prices five elements on a rip site: prepaid credit, a randomized outcome, delayed physical fulfillment, stored balances and buybacks. The trading cards are close to incidental.
Before you write a word of the application, check your own model against each element:
- Prepaid credit: does the customer fund a balance before buying a pack or a break spot?
- Randomized outcome: does the purchase deliver a card the customer cannot pick in advance?
- Delayed physical fulfillment: does the card ship later, or stay vaulted until the customer asks for it?
- Stored balances: does customer money sit on the platform between purchases?
- Buybacks: does the platform repurchase pulled cards, giving the customer a cash-out path?
Our underwriting team summed up the shape in September 2026: the processor is "pricing prepaid credit, a randomized outcome, and delayed physical fulfillment, with stored balances and buybacks in the middle." Courtyard, which sells digital packs of vaulted, graded cards, shares that shape. So does Rips by Triumph with its mystery packs. A local card shop does not.
The reason starts with the merchant category code. PaynoPain explains that the acquirer assigns the MCC based on the merchant's main activity, and that the code describes the general category of the business rather than the specific product sold. The same glossary notes that the MCC influences interchange and other fees, because some sectors are considered higher risk for issuers and acquirers.
The common assumption is that a rip site is a collectibles store with a fun checkout. It is not. For a rip platform, the main activity is selling a chance at an unknown card, funded from a prepaid balance, with a repurchase offer waiting at the end. Describe only the cards, and the code assigned at boarding reflects a business you do not actually run.
Risk tooling built on these codes concedes the gap. Its own documentation lists generic miscellaneous-retail codes and miscoded merchants among the known weaknesses, which is why reviewers look past the code to transaction patterns. Combining 4 sources points to one practical step: write the business description for the person assigning that code, not for your customers.
Aggregators think the same way. In a 2024 r/stripe thread, a merchant processing several million dollars a year through Stripe named account maturity and the specific business type as the factors that decide closure risk. Business type, again, means the money flow.
A candid caveat. No source in this research shows how often a retail-described rip site gets re-coded after boarding, and I won't guess at that rate. What the evidence does show is the mechanism.
Each element raises its own question. Prepaid credit and stored balances point to refund exposure. The randomized outcome invites a classification review. Delayed fulfillment opens the door to non-receipt disputes, and buybacks draw money-movement scrutiny. The first useful thing to ask any provider of merchant payment processing solutions is whether it already boards platforms of this shape, because that tells you whether those questions get asked at the application stage or months into processing, when the answers cost far more to give.
What happens when a rip site is boarded as a collectibles retailer?
The mismatch shows up after approval. Transactions reveal prepaid balances, random pulls and buybacks the application never mentioned, and the processor answers with holds, refunds or a closure notice.
Closures in this pattern often arrive with no disputes on the account at all. In a 2022 r/stripe thread, a merchant posted the notice they received: "Stripe can only support businesses with a low risk of customer disputes." The notice went on to say the business "presents a higher level of risk than we can currently support." The poster's reply was blunt: "I don't have a single dispute or a refund."
Read that twice. Note what the notice did not cite. So ask any processor directly what, beyond your dispute rate, would trigger a review of your account.
The money side is harder still. A separate r/stripe discussion from 2024 opened with a merchant alarmed that, on closure, Stripe can refund all customers, which the poster called "giving away our earned money." Another commenter said they had followed every rule and supplied every document, yet were "on the verge of insolvency due to their holds and refunds to customers." A third framed closures as "guilt by association," since a merchant's risk grade depends partly on customer behavior it cannot control.
Now picture that refund landing on a rip platform. Packs have been opened, cards pulled and vaulted, buyback credits issued, balances sitting on the ledger. A forced reversal does not just return revenue. It tangles every one of the five elements at once, and the operator is left reconciling inventory that already changed hands.
Volume can trigger action on its own. In 2016, a high-risk processor's own blog warned that processors can freeze funds when a merchant receives an unusually large number of payments in a short time, and that many processors reject applications at first. A rip site lives on spikes: a hot release, a live break, a weekend drop. If the application described a steady retail shop, a launch-night surge reads as an anomaly instead of an expected pattern.
Even a calm re-rating has a price. One ecommerce platform's statistics roundup claims high-risk processors typically require 5-15% rolling reserves, a capital lockup it says restricts cash flow. One POS vendor's 2024 statement guide advises reconciling each deposit summary against your bank statement, because delayed settlement hurts cash flow, and on a reserve that check shows exactly what is being held.
The damage also travels. A termination for compliance reasons can place a business on the MATCH list, the shared database processors use to screen applicants, and from there every new application starts from a deficit. Operators already in that position need a provider that offers MATCH list merchant account approval, not another aggregator signup that ends the same way.
None of these outcomes requires bad intent. The next section traces where that gap shows up once money starts moving.
Where does a rip site's risk go when the application leaves it out?
Every card payment carries a four-digit label chosen at boarding. We followed that label from the application to the payout to see what it can hide, and for how long.
Start with who picks the label. Visa's rulebook gives the job to the acquiring bank: "an Acquirer must assign to a Merchant Outlet the MCC that most accurately describes its business," says the April 2026 edition of the Visa Core Rules. A payments company's glossary explains how the bank decides. The code is assigned when a merchant registers to accept cards, "based on its main activity," and it names a broad business category. It says nothing about the specific product.
Once assigned, the code travels. It is "included in every transaction," the glossary notes, and it "influences interchange fee and other fees" because some sectors count as riskier than others. Visa also requires two or more codes for a single outlet in certain cases, including when separate lines of business operate together and Visa designates one of them as high-integrity risk. A rip site that boards as a card shop puts a card shop's label on every sale.
The label is written once, but it is not the only thing anyone reads. "MCC codes aren't perfect," says Whistl, a consumer app that uses card codes to flag spending its users want to watch. Its engineers list wrong codes, and generic ones such as "miscellaneous retail," among the known weak spots. To get around them, the app matches merchant names and flags patterns: round amounts, rapid repeat purchases, late-night timing, sudden spikes. Whistl works at the opposite end of the payment chain from an underwriter. Its example shows that a transaction carries more than its label. It cannot tell us how any processor reviews an account.
Our own underwriting team describes what that extra information looks like for this business. A processor "isn't really pricing 'trading cards'," a team member said in September 2026. It prices prepaid credit, a random outcome, delayed physical fulfillment, stored balances and buybacks. Each of those five moves money, so each leaves a trace in the transaction data no matter what the application said. We board rip and break platforms ourselves, so we have a stake in how this question gets answered.
What happens when a processor decides an account is the wrong type of business? Two Reddit threads about one large online payment platform give a sense of it. In 2022, a merchant posted the closure notice it received: "your business presents a higher level of risk than we can currently support." The merchant added: "I don't have a single dispute or a refund." In a 2024 thread, another merchant said they had supplied every document requested and were "on the verge of insolvency due to their holds and refunds to customers." A third commenter explained the refunds as the platform protecting itself when an account balance might not cover future disputes.
Both posts are anecdotes. Other commenters said only rule breakers get closed, and neither merchant said what they sold. The threads cannot show how often this happens. They do show that in these cases a clean dispute record did not save an account the platform had judged by its type.
The alternative is to disclose the risk up front, so the cost shows up as written reserve and hold terms. Vendor estimates of those terms conflict with each other, and the vendors have commercial angles of their own.
Fit Small Business, which ranks high-risk providers, cautions that actual fees "are always custom-quoted," so treat any published figure as a range and not a quote. Its advice to merchants is short: "If you're launching a new product or entering a new market, let them know in advance."
Two ways the same risk gets paid for
Named at boarding: the application describes the five elements, the acquirer picks a code to match, and reserve and hold terms are set before signing, where they can still be negotiated.
Left out at boarding: the code says card shop, the transactions show balances, random pulls and buybacks, and the processor reacts afterward. The closure stories above show what that reaction can look like.
Seen in order, the evidence shows a mismatch in timing. The code is fixed once, from what the merchant says. The money keeps showing what the business actually does. The five elements carry their cost either way. What the application decides is whether that cost appears in a contract you read before signing or in a notice you read after.
- Ask any processor, us included, whether it has already boarded platforms that run prepaid balances, random pulls, vaulted cards and buybacks.
- Ask which category code the acquirer plans to assign, and whether buybacks or stored balances could count as a separate line of business that needs its own code.
- Ask what happens to customer balances and pending refunds if the account is ever closed, and get the answer in writing.
- Get the reserve percentage and the hold length in the agreement, and ask what processing history would shorten the hold.
- Tell your processor before you add a new product, such as live breaks or a buyback program, so the change is reviewed before it shows up in your transactions.
How we checked this
We read the primary Visa rule on code assignment, a payments glossary, a consumer app's engineering explainer on category codes, two Reddit merchant threads, two vendor pieces on high-risk fees and a provider ranking. The five-element description comes from our own underwriting team. The reserve figures come from vendors, they conflict with each other, and none cites underlying data. The Reddit posts are individual accounts about one platform, and the posters did not say what they sold. Swell sells ecommerce software, Whistl sells a spending app, and we board rip and break platforms, so each of us has a stake. Still unknown: how often rip sites boarded as retailers are later re-rated, and how particular acquirers code buybacks or stored balances.
- Visa, Visa Core Rules and Visa Product and Service Rules, section 1.5.1.11, April 2026 edition.
- PaynoPain, glossary entry on merchant category codes, March 2026.
- Whistl, merchant category code analysis explainer, March 2026.
- Reddit merchant discussion threads on account closures, December 2022 and April 2024.
- Swell, high-risk payment gateway statistics, January 2026.
- Suprabhat Sen, ScaleupAlly, guide to high-risk merchant account fees, April 2025.
- Andrea Herrera, Fit Small Business, high-risk merchant account rankings, June 2026.
- SeamlessChex underwriting team, internal note on rip, mystery-pack and break merchants, September 2026.
How should a rip site word its business description?
Write one plain sentence per element, pair each with the control that limits its risk, and confirm reserve, hold and dispute terms before you sign anything.
Our underwriting team's view is direct: an application that calls the business a card shop misdescribes it. The description should name the five-part shape and say how each element is controlled. The table below gives starting wording. Fill the brackets with your real policies, and keep only the lines that are true of your platform.
| Element | Wording that invites re-rating | Wording that matches the shape |
|---|---|---|
| Business overview | Online trading card and collectibles store. | Online platform selling randomized digital packs and live break spots that resolve to physical graded cards, funded from a prepaid customer balance. |
| Prepaid credit | Customers can add funds. | Customers load a card-funded balance before purchase. Balance terms, refund rules and [expiry policy] are published in our terms of service. |
| Randomized outcome | Mystery packs. | Each pack or break spot delivers one physical card from a disclosed pool. Pool contents and [odds or value ranges] are shown before purchase. |
| Delayed fulfillment | Ships soon. | Pulled cards are vaulted for the customer or shipped on request within [stated window], with tracking on every shipment. |
| Stored balances | Wallet feature. | Customer balances are held in [account type] and reconciled [frequency]. Balances cannot be transferred between users. |
| Buybacks | We buy cards back. | Customers may sell a pulled card back at [published rate] of listed value. Proceeds are paid to [original funding method or platform credit], subject to [limits]. |
Notice what the right column does. Every line answers the question an underwriter would otherwise ask later. Nothing is hidden, so nothing surprises anyone.
I would not treat these lines as a script with proven results. Nobody has published approval rates for element-based versus retail-style descriptions, and I won't invent one. They are built from how the underwriter prices the model, which is the better starting point.
Which account terms should you confirm before signing?
The offer that comes back matters as much as the application. Scaleupally's 2025 fee guide described processors holding 5-20% of transactions for 6 months or longer, with rolling reserves of about 90 days for lower-risk merchants and 180+ days for higher-risk ones. It also noted that hold periods often shorten as processing history builds. Ask for each of these in writing:
- Reserve terms: the percentage held, the hold period, and what history earns a step down.
- Dispute thresholds: the same 2025 guide put standard monitoring at a 1% chargeback ratio, with high-risk merchants facing penalties at just 0.5%.
- Volume expectations: the monthly volume you were approved for, and what happens during a release spike.
- Redundancy: one merchant services vendor argued in 2024 that once a business passes $100k a month it should not rely on a single account.
That last point deserves weight for any operator whose launches drive heavy weekends. Our high-volume credit card processing services are built for that pattern. SeamlessChex works with established businesses processing at least $25,000 per month, so the volume history you bring becomes part of the case, and the stronger that history, the more room there is to negotiate the reserve line before it is ever set.
What should a rip site do before it submits the application?
Rewrite the description around the five elements, attach the policy behind each one, and choose a processor that already underwrites this shape rather than one that will discover it later.
The stakes compound. The category assigned at boarding follows every transaction, and in 2025 one fee guide put the highest-risk categories at 8-16% in fees, against 5-9% for moderate high-risk sectors. A description that lands you in the wrong bucket is expensive. Ask, too, whether the processor will confirm in writing the category it intends to assign before you go live.
Aggregator closures are not slowing down either. In the same 2022 r/stripe thread, one commenter warned that Stripe was closing accounts for many businesses "even if it's not high risk." Rip and break platforms sit closer to the line than most.
Expect rate pitches along the way: one 2026 r/sales commenter said owners hear a save-on-fees pitch about 10 times a week, which is reason enough to judge each offer on fit. Before you submit, divide your total fees by your total sales on recent statements, a check one merchant services vendor's 2022 podcast walked through, so the volume history you attach carries a real cost baseline.
Frequently Asked Questions
What else do rip site operators ask about their merchant application?
Most remaining questions come down to classification, cost and speed. Each one resolves faster when the application describes the five elements plainly instead of leaving the underwriter to guess.
Will an underwriter treat my rip site as gambling?
That is a classification question, and the processor answers it, not you. The acquirer assigns a merchant category code (MCC), a four-digit code for the type of business, based on the merchant's main activity rather than the specific product sold. Your job is to describe the randomized outcome honestly, alongside the other four elements, so the code fits the business you actually run.
Does the code really change what I pay?
Yes. The MCC travels with every transaction and influences interchange and other fees, because issuers and acquirers treat some sectors as higher risk. Scaleupally's 2025 fee guide said card processing fees typically ran between 1.5% and 3.5%, with high-risk merchants likely paying double or triple that. The same guide noted that hold periods often shorten as processing history builds.
Why does delayed shipping matter if the customer already paid?
Paid is not delivered. Think of a concert ticket bought months ahead: the money moves today, the show happens later, and if the show never happens, someone has to send that money back. A vaulted or later-shipped card works the same way, which is why an underwriter reads delayed fulfillment as exposure to not-received disputes.
How do I know a processor has boarded this shape before?
Ask directly. Our underwriting team puts it simply: a processor already comfortable with Courtyard or Triumph has underwritten this shape before. A vague answer is your signal to keep looking.
How quickly can SeamlessChex review a rip site application?
SeamlessChex offers same-day onboarding with no contracts, with credit card processing first and ACH available as a second rail. Send your five-element description through seamlesschex.com/contact, along with the refund, vault and buyback policies that sit behind each line.
Written by
Jonathan Albert
Co-Founder, SeamlessChex
Jonathan Albert is Co-Founder of SeamlessChex, a credit card processing and fintech payments platform recognized on the Inc. 5000.
Connect on LinkedInSeamlessChex works with established businesses processing a minimum of $25,000 per month.