Formula-create-own-path-2 icon

Peak season readiness

Learn what Adyen does and what you can do to be ready for the busiest period in the year.

Peak season is a critical period when businesses experience the highest volume of sales. For retail and ecommerce, that is typically from late October through early January. Other industries can have other or additional peak periods, like the summer holidays.

This part of the documentation provides information about what you can do to prepare for peak season spikes in sales. Most of the information applies to any peak period.

Adyen's operational readiness

Especially in the months before peak season, we often get questions like:

  • How many transactions per second (TPS) can your system handle?
  • How does Adyen prepare for peak season load?
  • How does Adyen ensure minimal disruption to the customer?

Our system is designed to handle large spikes in the number of transactions. Our active/active, stateless architecture allows us to distribute transactions across a pool of highly available resources. The utilization rate of those resources is low, generally less than 30%, which means there is plenty of capacity to handle large increases in volume.

Adyen does not have maintenance windows with scheduled payment processing downtime. Releases, patches and upgrades are continuously applied without interruption of service to the payment functions.

We periodically load test this system with merchants who hold transactions and then release the transactions in bulk.

Peak season preparation is an ongoing project that we work on throughout the year. We are constantly analyzing our capabilities, adding additional resources, and so on. However, during the typical retail and ecommerce peak season we have a modified release schedule and additional support hours.

Service-Oriented Architecture

All components, where possible, are stateless, meaning that no data is stored within a session on a particular piece of hardware. This ensures that in the event that components need to be swapped out and replaced or extra components need to be added, no data is lost and transaction processing can continue without impact. This setup is replicated in all the Adyen data centers to ensure maximum availability.

With load balancers in front of every data center, transactions can be equally processed through any available data center. In the event that a data center is unavailable, these load balancers also manage the failover to the other data centers. Again, due to the fact that the service is stateless, payment processing is not interrupted at any point.

Modified release schedule

We do not want to risk introducing bugs or performance regressions in production during the critical peak season. We therefore freeze our code deployment around the following peak season days:

  • Singles Day
  • Black Friday
  • Cyber Monday
  • Giving Tuesday
  • Christmas Eve, Christmas Day, and Boxing Day
  • New Year's Eve and New Year's Day

During code freezes we only allow new code deployments if it is a critical bug fix that went through code review by multiple senior engineers, and was approved by our operational leads. In this way, we prevent changes to your workflows.

What you can do

To get the most benefit out of the spike in sales during peak season, there are several actions you can take. For example:

  • You can optimize conversion rates, authorization rates, and costs, for example, by modifying settings related to risk or payment routing, or by adding features to your integration like local payment methods or accepting in-person payments offline when your network is down.

  • You should make sure that your team keeps an eye on the performance of your integration, and knows what to do and how to contact Adyen in case of an issue with the payment processing.

  • A spike in sales also means a spike in refunds and disputes. Therefore, you should ensure that your refund reserve remains topped up to an adequate level, and that your team is trained in dispute handling.

Read the next pages for our recommendations about all the above actions and more. Note that some of the recommended actions to get ready for peak season, require time to implement. You should plan such actions well in advance so that you can properly test and fix any errors.

We do not recommend implementing new features and doing major upgrades right before peak season.

Webinars and other resources

In addition to the documentation provided here, there are other resources you can consult. These resources typically provide a high-level overview, or have a more commercial focus.

Check the following webinars:

Other resources:

Next steps