Home › Blog › Digital Infrastructure
Digital Infrastructure

Payment Gateway Load Testing Singapore: Protect Your Checkout Before Cyber Monday 2026

Payment Gateway Load Testing Singapore: Protect Your Checkout Before Cyber Monday 2026

If you want your checkout to hold through Cyber Monday, do three things this week: work out the highest number of customers who will be paying in the same minute, confirm that your site and your payment gateway can both carry roughly three times that number, and agree a written fallback for the moment they cannot. The whole exercise takes a few hours. It has to happen between now and Sunday 22 November, because once the sale is running the only thing left to do is watch the orders fail.

Black Friday 2026 falls on Friday 27 November and Cyber Monday on Monday 30 November. For most Singapore online sellers the single busiest stretch is not the whole weekend but a twenty to forty minute window - the minutes after a promotional email or a WhatsApp broadcast lands. That is the window your checkout has to survive.

Why does checkout fail when the rest of the site is fine?

Because browsing and paying are not the same workload. A product page can be cached and served to a thousand people from memory at almost no cost. A checkout cannot. Every single order writes to your database, locks a stock record, validates a discount code, calls out to the payment gateway, waits for the bank, writes the result back, then fires off a confirmation email and a courier booking.

So your site looks perfectly healthy right up to the moment people start buying, and then the slowest step in that chain becomes the ceiling for everything. We have seen stores where the bottleneck was the confirmation email being sent before the customer saw the thank-you page. Twelve orders a minute was fine. Sixty was not.

How many orders a minute should you plan for?

Start with evidence rather than a guess. Open last year's sales report and find your busiest single hour, then your busiest ten minutes inside it. Multiply the ten minute figure by six to get an orders-per-hour rate at true peak. Then multiply that by whatever growth you have had since, and again by three for headroom.

The headroom is not pessimism. Checkout traffic is lumpy, and a well-performing campaign can double its own forecast in the first five minutes. If you are a first-year seller with no history, take the number of people on your mailing list or broadcast list, assume two to four percent of them buy within an hour of the send, and use that.

Write the final number down. It is the only figure that makes the rest of this week's testing meaningful.

How do you test the checkout without risking the live store?

Use your staging site, your payment provider's test mode, and a load testing tool that drives the full path a customer takes. Tools such as k6 or Locust are free and a competent developer can have a realistic script running inside half a day.

The script has to do the whole journey - land on the product page, add to cart, apply a discount code, fill the address, and submit a test card. A test that only hits the homepage proves nothing. Run it at your target rate for ten minutes and watch three numbers: how long the payment step takes, how many requests return an error, and how hard your server is working while it happens.

Then tell your payment provider what you are planning. Most gateways used here - Stripe, 2C2P, HitPay, Shopify Payments - apply a rate limit per account, and several will raise it for a known sale period if you ask in advance. That email costs you five minutes and removes an entire category of failure.

What are the three failures that cost the most money?

Double charges on retry. When the gateway is slow, your server times out and tries again, and the customer is charged twice. The fix is an idempotency key on every payment request, so a repeated attempt is recognised as the same order rather than a new one. This is the single most expensive bug on this list, because it costs you the refund, the gateway fee and the customer.

Paid orders that never arrive. The customer pays, the gateway confirms, but the notification back to your system gets lost in the queue and no order is created. Money in, nothing to ship, and an angry message on Monday. Check that failed notifications are retried and that somebody is alerted when the queue backs up.

Overselling. Two customers buy the last unit within the same second because the stock check and the stock deduction are separate steps. At normal volume this almost never happens. At peak it happens constantly.

What is your fallback when the gateway goes down?

Assume it will, for ten minutes, at the worst possible time. The fallback does not need to be clever, it needs to exist and be agreed before the weekend.

The practical version for a Singapore SME is a simple order form plus a PayNow QR code, published on a page that is already written and already tested, with a named person who decides to switch it on. Add a second payment method as a standing option if you only have one today - a card gateway and PayNow rarely fail together.

Decide now who is watching the checkout on the night, how they will know it has broken within two minutes rather than two hours, and who they are allowed to wake up.

What should be done before Sunday 22 November?

Six items, in order. Calculate your peak orders per minute from last year's figures. Run a full checkout load test on staging at three times that rate. Email your payment provider to confirm or raise your rate limit. Verify idempotency keys and payment notification retries with your developer. Publish and test the manual PayNow fallback page. Name the person on duty and the alert that reaches them.

None of this is strategy. It is a checklist, and the week to clear it is this one.

Frequently asked questions

Can I load test my live site instead of staging?

Only with your provider's agreement and in their test mode, and even then it is a poor idea during a sale period. Driving real traffic at a production checkout creates fake orders, distorts your stock, and can get your account flagged for suspicious activity at exactly the moment you need it working. Build the staging copy. If you do not have one, that is the first job.

We are on Shopify or WooCommerce. Does this still apply?

Partly. Shopify carries the hosting and checkout load for you, so your exposure moves to apps and custom scripts running at checkout, and to your stock sync with any warehouse or marketplace. WooCommerce runs on your own hosting, so every item above applies in full, and the usual bottleneck is the database on a shared or undersized server.

How much should a small seller expect to spend on this?

For a typical ten to thirty person Singapore business, half a day to a day and a half of developer time covers the test, the idempotency fix and the fallback page. Set against a single hour of failed checkout during Cyber Monday, it is one of the cheaper pieces of insurance available to you this month.

Ready to Transform Your Business?

Let Digital Perpetual help you automate, streamline, and grow.

Get Started with Digital Perpetual →
cyber monday 2026 payment gateway checkout peak week readiness singapore ecommerce load testing