Guides, articles and payment education
The resource library is organized by what a piece of writing is, because the kinds carry different guarantees. A guide explains how something works and is written to stay true. An article is dated writing: it says what it said on the day it published, and carries the day it was last reviewed. A case study is a worked scenario by business type, not a customer reference. Comparisons run on a published scoring model, and the glossary defines the terms the rest of the library uses.
Browse by content type
Guides
Four shelves — pricing, terminals, online payments, security and compliance — and three ideas underneath all of them. Settle those first and the rest of the collection reads as variations rather than as separate subjects.
ExploreArticles
Guides explain how something works and are written to stay true. An article is dated writing: it says what it said on the day it was published, and carries the day it was last reviewed as well.
ExploreCase studies
Every case study here is a worked scenario rather than a customer reference. Read one the way you would read a worked example: the value is in the order of operations.
ExploreProcessor comparisons
Side-by-side comparisons of pricing, contract and support models, so you can decide on your own numbers rather than an advertised rate.
ExplorePayments glossary
Plain definitions for the vocabulary on a merchant statement, in a processor contract and in a card network rule.
ExplorePayment processing FAQ
Straight answers to what merchants worldwide ask before and after they start accepting cards: how pricing models differ, what actually lands in the bank account, how long a switch takes and who is liable when a payment is disputed.
ExplorePOS guides
Choosing a point-of-sale system is four decisions, not one: three follow from what your floor runs — tables, lanes or a stockroom — and the fourth is the hardware under all three. Start on the shelf that matches the floor; the questions underneath are the same on all four.
ExplorePOS comparisons
Side-by-side comparisons of the point-of-sale systems restaurants worldwide, retailers and supermarkets actually run, on software cost, payment processing and day-to-day operations.
ExploreStatement review
A merchant statement review reads your existing processing statement line by line and reduces it to one number: your effective rate. That is total fees divided by total volume, and it is the only figure that compares honestly across providers and pricing models.
Explore
Latest resources
Guides, articles and case studies for merchants worldwide.
Printed statements and a calculator on a desk, with a phone, pen and glasses alongside Why Payment Processors Hold Funds, and How to Get Yours Released
Processors hold funds when a transaction pattern looks riskier than the profile they underwrote: a sudden volume spike, an unusually large ticket, a surge of card-not-present sales or rising disputes. The hold protects the processor from chargebacks that could arrive after paying you out. Most holds resolve quickly once you supply invoices, delivery proof or an explanation; the durable fix is keeping your processing profile current.
Explore
Hands holding a payment card above a laptop keyboard Text to Pay: How to Get Paid by Text Message (and Why It Works So Well)
Text to pay sends a secure payment link by SMS: the customer taps, a checkout opens with the amount pre-filled, and they pay by card or wallet in under a minute. It works because texts get seen almost immediately and acted on quickly, while emailed invoices queue behind everything else in an inbox. The fit is any moment where payment should happen now: field-service balances, appointment deposits, curbside orders and overdue-invoice nudges.
ExploreHands holding a payment card above a laptop keyboard QR Code Payments: The Complete Merchant Guide
A payment QR code encodes a link to a secure checkout: the customer scans with their camera, a payment page opens with the amount or catalogue ready, and they pay by card or wallet on their own phone. Static codes point to a fixed destination and cost nothing to print; dynamic codes are generated per transaction with the amount embedded. The pattern's power is deploying checkout where hardware is impractical: tables, counters, vehicles, posters, invoices and events.
Explore
A laptop showing a dashboard beside a hand holding a phone 7 PCI Compliance Myths That Cost Merchants Money (or Get Them Breached)
PCI DSS applies to every business that accepts cards, regardless of size, and the most expensive misunderstandings are consistent: believing the processor's compliance covers the merchant, treating the annual questionnaire as the whole obligation, storing card numbers 'temporarily', and paying non-compliance fees instead of completing a form. The realistic good news: with hosted payments and validated terminals, most small merchants' actual obligations are modest.
ExploreHands holding a payment card above a laptop keyboard How to Collect Past-Due Invoices: 8 Tactics That Actually Get You Paid
Most overdue invoices are not refusals; they are friction. The fixes attack the friction in order: attach a payment method to every invoice so paying takes one click, automate a polite reminder sequence, take deposits before work starts, move repeat clients to autopay, offer instalments before threatening escalation, charge (disclosed) late fees, make the phone call at day 30, and know when handing the file to collections beats carrying it. Businesses that systematize this shorten collection cycles dramatically.
ExploreHands holding a payment card above a laptop keyboard Dunning Management: How Subscription Businesses Recover Failed Payments
Dunning is the systematic recovery of failed recurring payments: classifying each decline, retrying soft failures on an intelligent schedule, refreshing expired cards through an account updater, and messaging customers in a tone that assumes good faith. It matters because involuntary churn, customers lost to failed cards rather than decisions, typically accounts for a large share of all subscription churn, and it is the most fixable revenue problem a recurring business has.
Explore
Frequently asked questions
How is the resource library organised?
By what you are trying to find out. Guides explain a subject end to end; articles cover one question each and are shelved by topic; the comparison hubs put RapidCents beside a named processor or POS; the glossary defines the terms the other pages use. Each hub lists what it holds.
Are the articles written for every market you sell in, the United States or both?
Both, and each one says which. Rules that come from law or an industry code are identified as such; rules that come from the card networks apply wherever those networks do. The site shows the edition for the country you are browsing in.
How current is the information?
Every article carries a published date, and the comparison pages carry the date their competitor claims were last checked against the public record. Pricing figures are deliberately not repeated in articles; they live on the pricing page, where they are maintained.
Can I ask a question the library does not answer?
Write to [email protected] or call +1 (844) 957-2743. Questions that come up more than once become articles, which is how most of this library was written.
