Accept payments
The gateway is the part you actually use every day. It should not be an afterthought.
Virtual terminal, tokenized vault, recurring billing, hosted payment pages, invoicing, batch upload, real reporting and webhooks that fire into your own systems. Configured for your business rather than handed over with a login and a shrug.
- Virtual terminal for phone, mail and keyed orders
- Recurring billing with retry logic and dunning
- Hosted payment pages and emailed invoices
- Webhooks and exports into your accounting stack
What you get
Payment gateway, set up properly.
Six things that actually matter, and what each one does for your business.
Virtual terminal
A browser screen that takes a card without any hardware. Built for phone orders, mail orders, deposits and anything your staff has to key in. Permissions per user so you can see who ran what.
Tokenized vault
Store customers as tokens instead of card numbers. Repeat billing, saved cards and one-click reorders all work, and you stay out of scope for storing card data yourself.
Recurring and subscription billing
Plans, trials, proration, scheduled retries on soft declines and dunning emails when a card genuinely fails. Retry logic is where most subscription revenue is silently lost.
Hosted payment pages and invoicing
Send a payment link by text or email, or attach one to an invoice. The customer pays on a secure page, funds land in your account, and the invoice marks itself paid.
Batch and keyed entry
Upload a file of transactions for bulk billing cycles, or key single transactions with full AVS and CVV capture. Useful for B2B shops running monthly billing runs.
Reporting and webhooks
Settlement, interchange detail, decline reasons and chargeback status, all exportable. Webhooks push events to your own system so your database is never guessing at payment state.
Gateway, processor, bank — who does what
The gateway is the software that captures the transaction and talks to the networks. The processor moves the transaction and settles the money. The sponsor bank underwrites the risk and holds the merchant account. Three roles, sometimes three companies, and the distinction matters when something goes wrong.
Most complaints owners have about their processor are actually gateway complaints: bad reporting, no vault, no recurring billing, no way to email a payment link. Those are fixable without moving your money.
Gateway-only setups
If your processing rates are already competitive but your software is a decade behind, we can place a modern gateway on top of your existing merchant account. That is a genuinely common arrangement and it avoids the migration entirely.
The reverse is also true — if the gateway is fine and the pricing is not, we quote the processing side alone. There is no reason to change both just because one is broken.
Watch the gateway fees
Gateway costs usually show up as a monthly platform fee plus a per-transaction fee, and sometimes a separate fee per vault record or per batch. On a low-ticket, high-count business those per-transaction pennies can outweigh the headline rate.
We show gateway cost as its own line on any quote, so you can see what the software costs separately from what the processing costs. Bundled numbers hide exactly this.
Accounts placed through our processor and banking network
Free statement analysis
Let's get payment gateway right on your account.
Send one recent statement and we will show you what changes, in writing, with the arithmetic on the page. No contract and no obligation either way.
Terrab Solutions is a registered agent/ISO partner. Rates and approval subject to underwriting. Estimates are not a binding quote.
Straight answers
Payment gateway questions
Usually yes. Card networks and gateways support vault migration between PCI-compliant providers, so your saved customers move as tokens without asking anyone to re-enter a card. It has to be requested and scheduled, not improvised.
Related solutions