Hosting in Peru

Peruvian WordPress hosting for orders that get paid days later.

A large share of Peruvian checkouts end with a voucher the customer takes to a shop or an agent. The order is real, the money is not there yet, and your store has to hold that state safely.

Long pending windowsVouchers reconciledBuilt for mobile data
Cash-voucher awareReachable callbacksMobile-firstDaily backupsFree SSL24/7 support
Built for how Peru pays

A checkout that finishes somewhere else.

Card is not the default here. PagoEfectivo vouchers, bank transfers and wallet payments all complete outside your site, at their own pace.

Orders that wait without expiring

A voucher can take up to three days to be paid. Pending windows are set to the payment method's real lifetime rather than to a default that cancels the order before the customer reaches a shop.

Method-aware expiry

Confirmations that always arrive

The payment provider tells your site when a voucher is paid, at a URL that must never be cached, challenged or rate-limited. Those endpoints are excluded from all three.

Excluded from cacheProvider IPs allowed

Reconciliation that catches the gaps

If a confirmation is ever missed, orders are reconciled against the provider rather than left pending forever, so paid customers are not waiting on a status nobody will change.

Fast on mobile data

Most traffic arrives on a phone, often outside Lima on a variable connection. Pages serve from the edge with the round trips kept down, because latency here is not a rounding error.

Daily backups, replicated

Orders, customers and content in a nightly snapshot held off the origin server and restorable from the dashboard in one action.

Operations

Watch the pending queue.

In a voucher market the health of the store is the age of its pending orders. A queue that stops draining means confirmations are not arriving.

  • One-click admin login, no shared passwords
  • Callback endpoint reachability tracked
  • Plugin and core updates with per-item status
  • Restore any daily backup from the dashboard
WordPress core
Up to date
6.7
Payment callbacks
Delivered and acknowledged
200 OK
Pending queue
Draining normally
healthy
Voucher reconciliation
Platform-driven
running
Performance

Built for the connection people actually have.

Traffic here is mobile-first and often far from the capital, so the round trips a page needs matter more than the raw speed of any single one.

14
edge regions
Redis
object cache, on by default
NVMe
storage on every plan
MagicWP260 ms
Origin-only, no regional edge1400 ms
Uncached checkout on mobile data900 ms

Illustrative comparison of a product page on a Peruvian mobile connection. Your numbers depend on network and page weight.

Configuration

What we change for a Peruvian store

These differ from a standard store on the same plan, and each follows from the fact that the payment completes hours or days after the order is placed.

SettingWhat we doWhy
Pending order lifetimeSet to the voucher's real validity rather than a default cancellation windowA cash voucher is commonly paid a day or two after checkout, so a store using the usual short hold cancels orders that customers are still walking to a shop to pay for.
Payment callback endpointsExcluded from page cache, bot challenges and rate limiting, with provider ranges allowedConfirmation of a voucher payment arrives as a single server-to-server call, and an endpoint that challenges or throttles it leaves a paid order sitting unpaid with nothing in the store to indicate why.
Reconciliation jobPending orders checked back against the provider on a fixed system cron scheduleAny callback-based flow eventually misses one, and without an active check the store's only record of a completed payment is a message it never received.
Stock reservationHeld for the pending window rather than released immediatelyInventory promised to an order awaiting a voucher payment has to survive that wait, or the customer pays for something the store has since sold to somebody else.
Round tripsAssets consolidated and served from the nearest edge regionPeruvian traffic is heavily mobile and frequently outside the capital, where each additional request costs far more in latency than it does on a fixed connection.
Plans

Simple, transparent pricing.

Every plan includes free migration, daily backups, SSL and 24/7 support.

MonthlyYearly
Starter
For personal sites, blogs, and portfolios.
$20/mo
Billed $240 yearly · save $60
  • 1 WordPress site
  • 10 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Support tickets
Start free trial
Pro★ Most popular
For growing businesses and busy stores.
$80/mo
Billed $960 yearly · save $240
  • 5 WordPress sites
  • 50 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Priority support tickets
Start free trial
Enterprise
For agencies and high-traffic platforms.
$250/mo
Billed $3000 yearly · save $600
  • 20 WordPress sites
  • 200 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Dedicated support
Start free trial
FAQ

Questions, answered.

Why are my Peruvian orders cancelling before payment?
The pending window is almost certainly too short. Vouchers are often paid a day or two after checkout, so a default hold cancels orders customers are still on their way to pay.
How do voucher payments confirm?
The provider calls your site once when the voucher is paid. That endpoint has to sit outside caching, bot challenges and rate limiting, or the payment completes and your store never learns about it.
What if a confirmation never arrives?
Pending orders are reconciled against the provider on a schedule. Every callback-based flow misses one eventually, and without an active check a paid customer waits on a status that will never change.
Is stock held while an order is pending?
Yes, for the length of the pending window. Otherwise the customer pays their voucher and the store has already sold the item to somebody who checked out with a card.
Do you have a datacentre in Peru?
No, and we would not claim one. Sites serve from the nearest of our 14 edge regions with round trips kept low, which is what actually determines page speed on a mobile connection here.

Run a Peruvian store that waits for the voucher.

Free migration, pending windows that match reality, and payments reconciled either way.