Card payments for honest remote tech support, settled to your wallet.
In 2025, people told the FBI they had lost $2.13 billion to tech support scams, so card processors treat every remote support business as a suspect. Railbed takes card payments for honest help desks and repair services and settles each one to a wallet you control, with nothing held back.
- No application to pass
- Nothing held back
- No setup fee
Press the card to run an example sale.
- Settles to
- Your own wallet, as USDC on Polygon
- Chargebacks
- Settled sales can’t be pulled back. Card disputes go to the provider
- To start
- An email, your website and a payout wallet. No setup fee, no monthly fee
- Buyer ID checks
- Providers decide. Smart Routing picks the one least likely to ask
Can a remote tech support business take card payments?
Yes. Many card processors refuse remote tech support because scams are common in the trade, and federal telemarketing rules have covered tech support sold over inbound calls since January 2025. Railbed takes card payments through independent, licensed card providers and settles each one to a wallet you control, with no underwriting and no application to pass. A business that uses cold calls or fake alerts is breaking the law.
Why honest remote support gets treated like a scam
A remote support business fixes computers it never touches, unlike a repair shop with a counter. A customer calls or books online, lets a technician connect, and pays for the fix. Scammers sell the same thing, with fake alerts, cold calls and invented problems, and they sell it at enormous scale. Card processors see the category, not the business, and many have decided the simplest answer is to refuse it or price it as if every merchant were a scammer.
- $2.13 billionLosses reported to the FBI from tech support scams in 2025
- 47,794Tech support scam complaints the FBI received in 2025
- 6xHow much more likely people 60 and over were to report losing money to these scams in 2023
- Jan 2025When federal telemarketing rules began covering tech support sold over inbound calls
Legitimate tech companies won’t contact you by phone, email, or text message to tell you there’s a problem with your computer.
The rules are written down. Stripe’s prohibited and restricted businesses list names “Telemarketing” and “Suspicious remote technical support” among the businesses it won’t serve, and “suspicious” is a judgment a risk team makes about your whole trade, often from the first line of your website. Google’s advertising policy on third-party consumer technical support says flatly that “Technical support for consumer technology products and online services offered by third-party providers is not allowed”, which closes the biggest channel an honest independent technician would use to be found.
The card networks add their own layer. Visa’s integrity risk programme lists outbound telemarketing, merchant category 5966, and subscription “negative option” merchants, 5968, among its high integrity risk merchants, which acquirers must register before serving. A support company coded as computer repair, 7379 in Visa’s merchant data standards manual, can still be moved into those codes once an acquirer sees phone sales or yearly plans that renew on their own.
What that leaves an honest support business with in practice
- A checkout that closes on a keyword. An account that took payments for years can close once a risk team reads “remote access” or “virus removal” on your site, with your money held while it closes.
- Fees and reserves priced for fraud. The processors that do take the trade charge high-risk rates and hold back a share of each payment for months against the disputes scammers generate.
- Disputes from customers who later get scared. A customer who reads about scams after a genuine session can ask their bank for the money back, and at a conventional processor that dispute comes out of your balance with a fee on top.
- No way to show you’re different. A risk team sees the same words on your site as on a scammer’s, and there is rarely anyone to explain your business to.
Honest support and the scam it gets mistaken for
Railbed is built for the honest business, and this page is too. A business that cold-calls people to tell them their computer is infected, shows fake security alerts, or invents problems to sell a fix is breaking the law, whichever way its customers pay. The Federal Trade Commission’s advice to consumers puts the line where every honest technician already stands: “Legitimate tech companies won’t contact you by phone, email, or text message to tell you there’s a problem with your computer.” It also says “Real security pop-up warnings and messages will never ask you to call a phone number.”
The difference shows in how each one sells:
| An honest support business | A tech support scam |
|---|---|
| The customer finds you and asks for help | The scammer calls, emails or shows a pop-up first |
| You diagnose the problem the customer reports | The scammer invents a virus, a hack or an expired licence |
| A price is agreed before work starts | The price rises once the scammer has remote access |
| Payment by card, with a receipt | Payment by gift cards, wire transfer, a payment app or crypto, which the FTC calls “like using cash” |
| The customer ends the session when they like | The scammer keeps access or installs tools to return |
| One sale, or a plan the customer chose with clear terms | A plan that renews without a clear agreement |
Railbed adds no rules of its own, and there’s no application to pass before you sign up. Staying within the law is your job, and Railbed stops new payments only when the law requires it.
How Railbed takes payment for support
Railbed is card checkout that never holds your money. A customer pays for their session with the card they already have, an independent, licensed card provider charges it and buys USDC with it, and the USDC is forwarded to the Polygon wallet you saved in Railbed, usually minutes after they pay. There is no balance with Railbed for anyone to freeze after a risk review.
| What goes wrong today | With Railbed |
|---|---|
| A processor refuses remote support or closes the account without warning | No underwriting and no application to pass. Railbed stops new payments only when the law requires it |
| High-risk rates, monthly minimums and setup fees | Provider fee and spread, a 1% network fee and the Railbed fee from 0.9%, with no setup or monthly fee |
| A reserve held back from every payment | Nothing is held back from your sales |
| A worried customer disputes a genuine session and the processor debits you | Settled sales can’t be pulled back from your wallet; card disputes go to the provider that charged the card |
| A customer’s card is declined at the end of the call | Smart Routing sends each customer to the card provider most likely to approve them |
Railbed checks that the right amount reached the right wallet before it marks a payment Paid. Then it tells you three ways: the payment shows in your dashboard, a signed payment.paid webhook reaches your ticketing system if you’ve connected one, and an alert can go to your team in Telegram or Slack. The technician on the session sees the payment land without leaving the call.
It is a payment tool, not a support platform. Railbed doesn’t open remote sessions, run your help desk or manage devices. It takes the payment, settles it to you and sends the receipt, and leaves the support to the tools you already use.
The FTC’s rule for tech support sold over the phone
The Telemarketing Sales Rule has covered calls that sellers make for decades. Calls a customer makes in answer to an ad were mostly left out, and tech support scammers built their business on that gap: a fake pop-up gave a number, the customer called it, and the call wasn’t telemarketing under the rule. On 10 December 2024 the FTC published a final amendment that closed the gap. Since 9 January 2025 the rule has applied to inbound calls “in response to an advertisement through any medium or direct mail solicitation in which technical support products or services are offered for sale”.
The rule’s definition is broad. A technical support service is “any plan, program, software, or service that is marketed to repair, maintain, or improve the performance or security of any device on which code can be downloaded, installed, run, or otherwise used, such as a computer, smartphone, tablet, or smart home product, including any software or application run on such device.” If you advertise and customers call you to buy, your calls are inside it.
What that means for an honest business taking calls:
- Disclose and don’t mislead. The rule bans misrepresenting what you sell, its price, its terms or its effect, and requires the material terms to be disclosed before the customer pays.
- Take payment the normal way. Under 16 CFR 310.4, a telemarketing seller may not take payment by “a cash-to-cash money transfer or cash reload mechanism”, or create “a remotely created payment order”. A card payment on a checkout page is none of those.
- Keep records. The rule’s recordkeeping duties apply to covered calls, so keep your scripts, ads, prices and customer records.
- Watch who helps you. The rule makes it a violation to give substantial assistance to a seller when you know “or consciously avoid knowing” it’s breaking the rule. Marketing partners, call centres and lead sellers who use fake alerts put you at risk too, and the same rule is why payment companies grow nervous about the whole trade.
Calls you make yourself to people who never asked are a separate matter. Cold calls to consumers are covered by the rule’s do-not-call and calling-hour provisions, and telling someone their computer has a problem you haven’t seen is a deceptive practice in any form. Honest support businesses don’t make those calls.
Business customers are covered too. In March 2024 the FTC extended the rule’s ban on misrepresentations to calls made to businesses, so a support company selling to small offices is held to the same honesty standard on the phone.
Tech support enforcement, year by year
The FTC and its partners have pursued tech support scams for more than a decade. Each round of enforcement has made the trade harder for scammers, and harder for honest businesses to explain to a processor.
- May 2017
The FTC and federal, state and international partners announce Operation Tech Trap, a crackdown on tech support scams.
- Mar 2024
Restoro and Reimage agree to pay $26 million over fake Windows pop-ups that pushed people into buying repairs.
- Mar 2024
The FTC extends the telemarketing rule’s ban on misrepresentation to calls made to businesses.
- Dec 2024
The FTC publishes the final rule bringing inbound tech support calls under the telemarketing rule.
- Jan 2025
The inbound tech support amendment takes effect.
- Mar 2025
The FTC sends more than $25.5 million in refunds to people who paid Restoro and Reimage.
- Apr 2026
The FBI’s report for 2025 counts 47,794 tech support scam complaints and $2.13 billion in losses.
The Restoro case shows the pattern regulators look for. The FTC charged that people “were lured or alarmed by fake Microsoft Windows pop-ups”, told their computers were infected, and urged to “scan” them “To avoid more damage”, before being sold repairs they didn’t need. An honest business that never uses alarms or pop-ups is on the other side of that line, and should be able to show it.
What you sell, and how each sells through Railbed
| What you sell | How it sells | Notes |
|---|---|---|
| A one-hour remote session | A checkout page for the session, or a link you send during the call | The example sale on this page: $89 |
| A fixed-price fix: virus removal, a new computer set up, data moved | A checkout page per service at a set price | Agree the price before you connect |
| Prepaid blocks of hours | A checkout per block, credited to the customer’s account from the webhook | Write down how unused hours are handled |
| A yearly support plan | An invoice each year, paid in full or in parts | Railbed has no recurring billing; each year is a fresh choice |
| Antivirus and software licences you resell | A checkout per licence, with the key sent by your system after payment | Resell only with the publisher’s permission |
| Monthly support for a small office | An invoice per month or quarter, with reminders | For managed services, see IT services |
| An on-site visit | An invoice after the visit, paid on the customer’s phone through a QR code | Railbed is online checkout, not a card terminal |
A session priced at $10 or more gives the customer the widest choice of card providers, and each provider has a minimum, about $2 at the lowest. Prices can run to 100,000.00, in US dollars, euros, pounds, Canadian or Australian dollars, Indian rupees or Swedish kronor.
How a remote session gets paid
The customer finds you, on your website, in a directory or through a referral, and books or calls. You agree the problem and the price before anyone connects.
You send the checkout: a page for the service, a link in your booking confirmation, or an invoice after the work. The customer enters an email address and anything else the checkout asks, such as a ticket number.
Smart Routing sends them to the card provider most likely to approve their card, in their country, for that amount. The provider decides whether to ask for identity details, and Smart Routing tries the providers least likely to ask first; light checks such as a name, date of birth and address can still happen.
The provider buys USDC with the card payment, and it’s forwarded to your wallet on Polygon. Railbed checks the amount and the wallet before it marks the payment Paid, and the customer gets a receipt.
Railbed sends a signed
payment.paidwebhook to your ticketing system and, if you’ve set it up, an alert to Telegram or Slack. The technician starts or finishes the session.
Before a real card is charged, run the whole thing in Test mode: simulate paid, underpaid and failed payments, and check that a test ticket is marked paid exactly once.
Before or after the fix: when to charge
When a customer pays shapes how they feel about you, and honest businesses tend to charge in one of three ways:
- After the fix. Common for a single session: the technician finishes, the customer is happy, and the invoice goes out while they’re still on the call. Unpaid invoices are the risk, so Railbed’s invoice reminders do the chasing.
- Before the session. Common for fixed-price services booked online. The customer pays for a known service at a known price, and the session starts once the payment shows as Paid.
- A deposit, then the rest. For larger jobs, such as recovering data or setting up an office, an invoice can be paid in parts, with a smallest first payment you set, and the rest on completion.
Whichever you choose, say it before the customer pays, and make the price the price. A total that rises once the technician has access is the clearest sign of a scam, and customers know it.
Remote access customers can trust
Remote access is the most sensitive thing a customer gives you, and how you handle it decides whether they come back, recommend you or call their bank. These habits keep honest businesses visibly different from scammers:
- Let the customer start the session. They download your tool from your website, read out a code and watch the screen. Never ask a customer to install something because a stranger told them to.
- Show everything. Work with the customer watching, explain what you find, and never open files, email or banking that the fix doesn’t need.
- End the session cleanly. Disconnect, show the customer how to confirm it’s closed, and remove any tool you installed unless they asked you to leave it.
- No unattended access without written agreement. If a plan includes access when the customer isn’t there, put it in writing and make it easy to withdraw.
- Card first, with a receipt. Never insist on gift cards, wire transfers, payment apps or crypto. The FTC lists each of them among scammers’ favourite ways to be paid.
- Your name everywhere. The same business name on your website, your remote tool, your checkout and the customer’s card statement.
The checkout helps with the last two. Customers pay by card on a page with your name and logo, and the receipt lists what they bought, from whom and for how much.
Serving older customers well
Many of the people who need remote help most are older, and they are the people scammers target hardest. The FTC’s final rule notes that in 2023 consumers 60 and over were six times more likely than younger people to report losing money to tech support scams, and that reported losses that year came to about $242 million, with a median loss of $1,400. An honest business with older customers carries the weight of that history on every call.
A few habits make the difference:
- Slow down at the payment. Read the price aloud, say what it covers, and let the customer pay on their own screen in their own time.
- Welcome a second opinion. If a customer wants a family member to look before paying, wait. A scammer hurries people; you don’t need to.
- Write it down. Send the quote by email before the session and the receipt after, so the customer and their family can see exactly what was bought.
- Make it easy to come back. The same phone number, the same website and the same name on every receipt let a customer recognise you next time, and tell you apart from anyone who calls them pretending to be you.
None of this costs a sale. It is how a support business earns referrals, which matter more in a trade the big ad platforms won’t take.
Before your first paid session
None of this is an application. It is the list a support business gets in order once, most of it before any payment company is involved.
Honest marketing. Ads and pages that describe your services, your prices and who you are, with no alarms, no fake warnings and no suggestion that you are a device maker’s own support.
Published prices and terms. Session rates, fixed prices, what a plan covers and how refunds work, where the customer sees them before paying.
A remote access policy. How sessions start, what you will and won’t access, how they end, and how a customer withdraws unattended access.
Call records, if you take calls from ads. Scripts, ads and customer records kept the way the telemarketing rule asks.
A payout wallet. Save the Polygon wallet payments should settle to. Use a wallet you hold the keys to, not an exchange deposit address.
Payments that land once. Put the ticket number in the reference and record each event ID, so a retried webhook can’t mark the same ticket paid twice.
Licence rights for anything you resell. Written permission from each software publisher whose licences you sell.
Refunds and disputes
Some fixes don’t work, and some customers change their minds. Railbed can’t reverse a settled payment, so refunds are yours to make: send USDC back or agree another arrangement with them, such as another session at no charge. Write down when you refund, how much, and what happens with unused prepaid hours, and show it before anyone pays.
A dispute is a different thing. A customer who asks their bank for the money back raises it with the card provider that charged the card, under that provider’s terms and the card networks’ rules, and nothing comes out of your wallet. At a conventional processor the same dispute counts against you, and remote support sees more of them than most trades, because a customer who reads about scams after a genuine session can start to doubt it.
Good records make disputes rarer. A receipt with your name, a ticket with what you did, and a customer who watched the whole session leave little room for doubt, and a card provider may decline future payments from a customer who disputes.
What stays your responsibility
Railbed’s acceptable use policy says you are responsible for the laws that apply to your business and your buyers, “including any licences, age checks or tax registrations your markets require”, and that Railbed doesn’t check them for you. For a remote support business that means:
- Honest marketing and sales, under the FTC Act, the telemarketing rule where it applies, and state consumer protection laws.
- Privacy and security of everything you see during a session, and of the customer data you keep.
- Any licence your state requires for computer repair or data recovery, and sales tax on services and software where it applies.
- Software licences for the tools you use and the products you resell.
- The work itself, and making it right when a fix doesn’t hold.
Fees and getting paid
Every fee is shown before anyone pays. Fees come out of the USDC that arrives: the card provider’s own fee and exchange spread, which the customer sees on the provider’s page, a 1% network fee, and the Railbed fee, from 0.9%, shown in your dashboard. There’s no setup fee, no monthly fee, no volume minimum and no chargeback fee.
The customer pays the price you set, so an $89 session is $89 on their card. Payments settle almost always as USDC on Polygon to your own payout wallet, in dollars, not a volatile coin. To move money to a bank account, send USDC to an exchange and withdraw it there, whenever suits your payroll.
Railbed compared with what support businesses use today
| Mainstream processor | High-risk merchant account | Railbed | |
|---|---|---|---|
| Getting started | Refused, or closed without warning | Weeks of underwriting, processing history and a personal guarantee | An email, your website and a payout wallet |
| Fees | Standard rates, until the account closes | High-risk rates, setup fees and monthly minimums | Provider fee and spread, 1% network fee, Railbed fee from 0.9% |
| Reserve | Funds held when the account closes | A share of each payment often held for months | Nothing is held back from your sales |
| Disputes | Debited from your balance with a fee | Debited from your balance with a fee | Settled sales can’t be pulled back from your wallet; card disputes go to the provider |
| Support plans | Recurring billing, if allowed | Recurring billing, under close watch | Invoices you send for each period |
| Card terminal | Usually available | Usually available | None: online checkout and QR codes |
When Railbed is not the right fit
Railbed suits a support business that sells honestly and needs a card checkout that won’t close because of the trade it’s in. It is the wrong tool in a few cases:
- You need plans that charge automatically every month. Railbed has no recurring billing; send an invoice for each period instead.
- You want customers to pay by bank transfer or cheque. Railbed takes cards. Customers pay on the card provider’s page.
- You need a card terminal in a shop. Railbed is online checkout. Walk-in customers pay on their own phones through a QR code.
- You never want to hold USDC. Payments settle as USDC to your wallet, and moving them to a bank is a step you take yourself through an exchange.
Words worth knowing
The terms regulators, card networks and the support trade use.
- Telemarketing Sales Rule
- The FTC’s rule for selling by phone. It bans misrepresentations and some payment methods, and since January 2025 it covers inbound tech support calls from ads.
- Inbound call
- A call the customer makes to the seller, usually in answer to an ad, a pop-up or a mailing. Tech support scams relied on inbound calls being outside the rule.
- Technical support service
- The rule’s term for any plan, program, software or service marketed to repair, maintain or improve a device that runs code.
- Assisting and facilitating
- Giving substantial help to a seller you know, or consciously avoid knowing, is breaking the telemarketing rule. It is a violation in itself.
- Remotely created payment order
- A cheque or payment order created by the seller from a customer’s bank details, without a signature. Telemarketing sellers may not use them.
- Cash reload mechanism
- A way to load cash onto a prepaid card or account, often through a PIN read over the phone. Telemarketing sellers may not accept it.
- Unattended access
- Remote access a technician can use when the customer isn’t at the device. Honest businesses get written agreement first.
- MCC 7379
- The merchant category code for computer maintenance, repair and services not classified elsewhere.
- MCC 5966
- The merchant category code for outbound telemarketing, which Visa lists among its high integrity risk merchants.
- Negative option
- A plan that keeps charging until the customer cancels. Visa lists subscription negative option merchants as high integrity risk.
Questions
Stripe closed my remote support account. Can I use Railbed?
Yes. Railbed has no underwriting or application, so a past closure doesn’t rule you out. Selling honestly is the law’s requirement: a business that uses fake alerts or invented problems is breaking it, whichever way it takes payment.
Does the FTC’s Telemarketing Sales Rule apply to my support business?
It applies to tech support sold over calls customers make in answer to your ads or mailings, since 9 January 2025, and to calls you make yourself. If customers only book and pay online without a sales call, the rule’s call provisions may not reach you, but the FTC Act’s ban on deception always does. Ask a lawyer about your own sales process.
Can I take card payments over the phone during a support call?
Send the customer a checkout link or an invoice during the call and let them pay on the page. Railbed doesn’t take card numbers read over the phone, which keeps you out of handling card details at all.
Can customers pay with gift cards or crypto?
Gift cards, no: Railbed takes cards, and crypto only if you turn on crypto payments in Settings. For remote support, card is the better default anyway. The FTC lists gift cards, wire transfers, payment apps and crypto among the payment methods scammers insist on, so a card payment with a receipt helps customers trust you.
Can I sell yearly support plans?
Yes, as a single payment or an invoice each year, paid in full or in parts. Railbed has no recurring billing, so each renewal is a fresh payment the customer chooses, which also keeps you clear of negative option rules.
Can I resell antivirus and other software licences?
Yes, with the publisher’s permission. Sell each licence through a checkout and send the key from your own system once the payment shows as Paid.
Will my customers be asked for ID when they pay?
Sometimes. The card provider decides whether to ask for identity details, and Smart Routing sends customers to the providers least likely to ask first. Light checks, such as a name, date of birth and address, can still happen.
What happens if a customer disputes a session?
The dispute goes to the card provider that charged the card, under its terms and the card networks’ rules. Settled sales can’t be pulled back from your wallet, and there is no chargeback fee. Refunds you choose to make are yours to send in USDC.
Can I advertise my support business on Google?
Google’s advertising policy doesn’t allow ads for third-party technical support for consumer technology products and online services. Read the current policy for your services before you plan around search ads, and lean on your own website, directories and referrals.
What merchant category code does remote tech support use?
Computer repair and services usually take code 7379. Processors may move a business into outbound telemarketing, 5966, or treat yearly plans as negative option billing, both of which Visa lists among its high integrity risk merchants. With Railbed you don’t apply for a code: an independent, licensed card provider makes the card charge.
Can I invoice small business clients for monthly support?
Yes. Send an invoice per month or quarter with terms, reminders and part payments, or one invoice for a block of hours. For managed services contracts, see the IT services page.
How quickly does a payment reach my wallet?
Usually within minutes of the customer paying. The provider buys USDC with the card payment and it’s forwarded to your Polygon wallet, and Railbed marks the payment Paid once it has checked the amount and the wallet.
Do I need a card terminal for on-site visits?
No. Railbed is online checkout, so a customer pays an invoice or checkout on their own phone through a QR code, on site or afterwards.
Sources
- FBI Internet Crime Complaint Center: 2025 Internet Crime Report, April 2026, checked 20 November 2026
- Federal Register: Telemarketing Sales Rule, final rule on inbound technical support calls, 10 December 2024, effective 9 January 2025, checked 20 November 2026
- Stripe: Prohibited and restricted businesses, last updated 22 September 2026, checked 20 November 2026
- Google: Third-party consumer technical support advertising policy, checked 20 November 2026
- Visa: Visa Integrity Risk Program guide, 2023, checked 20 November 2026
- Visa: Visa Merchant Data Standards Manual, checked 20 November 2026
- Federal Trade Commission: How to spot, avoid and report tech support scams, checked 20 November 2026
- eCFR: 16 CFR 310.4, abusive telemarketing acts or practices, checked 20 November 2026
- Federal Trade Commission: FTC implements new protections for businesses against telemarketing fraud, March 2024, checked 20 November 2026
- Federal Trade Commission: FTC, federal, state and international partners announce major crackdown on tech support scams, May 2017, checked 20 November 2026
- Federal Trade Commission: Tech support firms will pay $26 million to settle FTC charges, March 2024, checked 20 November 2026
- Federal Trade Commission: FTC sends more than $25.5 million to consumers impacted by tech support firms’ scam, March 2025, checked 20 November 2026
Last updated .
PaidA one-hour remote session, settled to your wallet$89.00
Fixed remotely, paid by card.
Settled before you log off.
Set up in under a minute. Your first payment can settle today.
- No application to pass
- Nothing held back
- No setup fee
Moving a lot of volume? Talk to our team