Skip to main content

Guidance for Payment Connectivity, Gateway, Orchestration & Routing on AWS

Transform your global payments network with today's technology

Overview

This Guidance helps financial institutions implement a quick response (QR) code and payment processing on AWS for their digital customers. With the managed serverless solutions, you do not need to own, run, or manage the compute infrastructure, allowing you to focus on payment processing.

How it works

This reference architecture displays how a quick response (QR) or wallet payment traverses through various components.

Well-Architected Pillars

The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.

To enable fast iteration and consistent deployment, you can use AWS Cloud Development Kit (AWS CDK) version 2, AWS CloudFormation, and Terraform. The recommended services are built with observability in mind, with process level metrics, logs, and dashboards. Extend these mechanisms to meet your needs and create alarms in Amazon CloudWatch to notify your on-call team of any issues.

Read the Operational Excellence whitepaper 

The payment backend is protected with API Gateway resource policies to allow your API to be securely invoked from known resources. When you choose managed services, you can be sure that all AWS API calls are done through HTTPS endpoints using TLS communication, which will protect your data in transit.

Read the Security whitepaper 

All components scale automatically, and the account limits should be clearly defined for the supported product range to avoid affecting reliability. To further increase reliability, consider implementing a disaster recovery plan for your solution by initiating cross-region failover using Route 53 for the whole infrastructure. 

Read the Reliability whitepaper 

Managed serverless solutions can help you avoid having to worry about scaling requirements. Fargate removes the need to own, run, and manage a compute infrastructure, allowing you to focus on payment processing. Network Load Balancer distributes incoming traffic across multiple targets, which can handle millions of requests per second.

Read the Performance Efficiency whitepaper 

This Guidance is designed to help you build a serverless architecture that keeps costs down. You pay only for the time and resources used to process payments. With managed and serverless services, you can set attributes that ensure sufficient capacity. You must set and monitor these attributes so that you minimize excess capacity and maximize performance. 

Read the Cost Optimization whitepaper 

To reduce the amount of hardware required for provisioning, consider using managed container services, such as Fargate, instead of implementing your own container infrastructure.

Read the Sustainability whitepaper 

Disclaimer

The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.