What a payment gateway does
The gateway collects the card, wallet or bank details at checkout and encrypts them immediately. It replaces the raw card number with a token, runs the fraud and address checks you have enabled, and passes the authorization request onward.
Seconds later it returns an approval or decline to your checkout page and stores the token so you can bill again, refund, or keep a card on file without ever holding the card number yourself.
Capture
Hosted checkout page, embedded fields, invoice link or virtual terminal — the surface where the customer enters payment details.
Protect
Encryption in transit, tokenization at rest, plus AVS, CVV and rules-based fraud screening.
Authorize
Sends the request to the processor and returns the result to your site or app in real time.
Manage
Card-on-file, recurring schedules, partial captures, refunds and dispute evidence all live in the gateway's records.
Gateway vs processor vs merchant account
These three are often sold together, which is why they get blurred. They do different jobs.
The gateway captures and secures the payment. The processor routes the authorized transaction through the card networks to the customer's issuing bank. The merchant account, held at an acquiring bank, is where settled funds land — and it is the piece that goes through underwriting.
You can have a gateway you like paired with a processor that is a poor fit for your business, or the reverse. Reviewing them separately is usually the fastest way to see where a proposal is weak.
Do you need a gateway at all?
If every sale happens in person on a terminal or POS, the device handles capture and you may never touch a gateway directly. The moment you invoice, take an order online, store a card for a repeat client, or key in a phone order, a gateway is doing that work.
Many businesses run both: terminals at the counter and a gateway behind the website, invoices and virtual terminal, with reporting brought together in one place.
Ecommerce checkout
Cart or booking tool posts to the gateway, which returns an approval before the order confirms.
Invoicing
A pay-now link on the invoice opens a hosted page, so no card details reach your inbox.
Virtual terminal
Your staff keys a phone or mail order into a browser instead of a physical device.
Recurring billing
Stored tokens bill on a schedule and retry politely when a card updates or expires.
What to check before you choose one
Most gateway regret comes down to integrations and day-two operations, not the checkout page itself.
Integrations you already use
Confirm support for your specific cart, booking system, invoicing tool and accounting platform — not just the platform family.
Payment types
Cards, digital wallets, ACH or eCheck, card-on-file and partial payments if your workflow needs them.
PCI scope
Hosted fields and tokenization keep card data out of your systems, which usually simplifies your PCI validation. Ask what your SAQ type becomes.
Refunds and disputes
How refunds are issued, how chargeback notices arrive, and how evidence is submitted.
Reporting and reconciliation
Whether gateway activity ties cleanly to your deposits and your in-person batches.
Support after setup
Who answers when a checkout stops approving on a Saturday, and whether your account gets reviewed over time.
How pricing is usually structured
Gateway and processing costs are typically quoted together, and the structure matters more than any single advertised number. Interchange plus, flat rate and tiered models each behave differently depending on your average ticket, card mix and how much of your volume is keyed or card-not-present.
BSV Solution reviews your existing statement and tender mix before recommending a gateway and processor pairing. Programs are quoted individually and remain subject to underwriting approval.
Frequently asked questions
What is a payment gateway in simple terms?
It is the software that securely captures a payment when the card is not swiped in person — on your website, an invoice or a virtual terminal — encrypts and tokenizes the details, and returns an approval or decline to your checkout.
Is a payment gateway the same as a payment processor?
No. The gateway captures and secures the transaction. The processor routes it through the card networks to the issuing bank. They are often sold together but do separate jobs.
Do I need a merchant account as well as a gateway?
Yes, in most setups. The merchant account at an acquiring bank is where settled funds land, and it goes through underwriting review before it is opened.
Does a gateway reduce my PCI responsibilities?
Using hosted fields and tokenization keeps raw card data out of your own systems, which typically simplifies your PCI validation. Your specific SAQ type depends on how the gateway is implemented.
Can one gateway handle my website, invoices and phone orders?
Usually yes. Most gateways expose a hosted checkout, invoice payment links and a virtual terminal from the same account and reporting.
What does a payment gateway cost?
Gateway and processing costs are quoted together and depend on your volume, average ticket and card mix, so we review your statement rather than publish a rate.
Want a second opinion on your setup?
Tell us how you take payments today and a BSV Solution specialist will walk through the options with you. Eligibility and processor selection are reviewed individually, subject to underwriting approval.