Finance & Insurance
Server infrastructure for Payment Processing
Sized from the workload rather than sold as a plan name: what Payment Processing actually run, what that needs, and which tier it belongs on.
Recommended builds by size
Three sizes of operation, each sized from an assumed traffic figure.
Small
1–10 people · ~5,000 visits a month
VDS
- 2 Cores
- 24 GB RAM
- 100 GB storage
A single site or team, with traffic that arrives in a predictable working-hours pattern.
Medium
11–50 people · ~50,000 visits a month
VDS
- 4 Cores
- 64 GB RAM
- 250 GB storage
A growing business running several systems, where an outage now costs real money.
Large
51+ people · ~500,000 visits a month
Dedicated Server
- 16 Cores
- 256 GB RAM
- 900 GB storage
Multiple sites or a busy platform, with traffic that spikes and an obligation to stay up.
Which tiers suit Payment Processing
| Infrastructure | Verdict | Why |
|---|---|---|
| Shared Hosting Managed space on a shared server | Not this one | Persistent connections and custom ports are exactly what a shared platform does not permit. |
| VPS Flexible virtual infrastructure with full root access | Workable | Enough for a small server or a test instance, though a noisy neighbour shows up immediately as jitter. |
| VDS Virtual server with resources pinned to you alone | Recommended | Pinned cores are what keep tick rate and call quality steady; on a contended instance they are not. |
| Dedicated Server An entire physical server, configured to your specification | Recommended | Single-tenant hardware removes the last source of variance, which is what these workloads are judged on. |
| Bare Metal Physical compute for sustained, demanding workloads | Workable | For operators running many instances at once on hardware they control. |
Payment Processing workloads you can host
Authorisation is measured in milliseconds and settlement is a nightly batch — two workloads with opposite shapes on one platform.
- Authorisation routing
- Tokenisation vault
- Settlement batching
- Chargeback handling
- Fraud scoring
Payment Processing hosting by city
Each page names the closest of our 24 data centres and how far away it actually is.
- New York
- Toronto
- Los Angeles
- Montréal
- Chicago
- Vancouver
- Calgary
- Houston
- Edmonton
- Phoenix
- Ottawa
- Philadelphia
- San Antonio
- Winnipeg
- Québec City
- San Diego
- Dallas
- Hamilton
- Austin
- Kitchener
- Halifax
- San Jose
- Jacksonville
- Victoria
- Saskatoon
- Seattle
- Denver
- Regina
- Boston
- Mississauga
- Atlanta
- Brampton
- Miami
- San Francisco
- ‘Ewa Beach
- ‘Ewa Gentry
- Abbey Wood
- Abbotsford
- Aberdare
- Aberdeen
- Aberdeen
- Aberdeen
- Aberdeen
- Aberystwyth
- Abilene
- Abingdon
- Abington
- Abington
- Abu Hayl
- Accrington
- Acocks Green
- Acton
- Acton
- Acworth
- Ada
- Adams Morgan
- Addison
- Addison
- Adelaide city centre
- Adelaide Hills