This Guidance shows how payment institutions can use new data types, streaming data, data lakes, and machine learning (ML) on AWS to make rapid credit decisions, reach new consumers, and deliver on customer expectations of multiple payment options.

 

Architecture Diagram

Download the architecture diagram PDF 

Well-Architected Pillars

The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.

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.

  • This Guidance can be scripted using an AWS CloudFormation template. To integrate and deploy changes, use a source control system like AWS CodeCommit to manage code and other artifacts, such as version-controlled AWS CloudFormation templates of your infrastructure. When responding to incidents and events, you can send logs directly from your application to Amazon CloudWatch using the CloudWatch Logs API, or send events using AWS SDK and Amazon EventBridge.

    Read the Operational Excellence whitepaper 

  • For secure authentication and authorization, AWS Identity and Access Management (IAM) roles are in place for all service interactions in the environments. All data is fully encrypted in transit and in storage. AWS services provide HTTPS endpoints using TLS for communication, thus providing encryption in transit when communicating with the AWS APIs.

    Read the Security whitepaper 

  • To support a highly available network, all components scale automatically; account limits should be clearly defined for the supported product range. To adapt to changes in demand, the solution is modular and can scale with user adoption.

    Read the Reliability whitepaper 

  • Serverless architectures help to provision the exact resources that the workload needs. Strategies for storage lifecycle management and ensuring auto capacity scaling are used for ingestion and read and write access patterns. To meet the requirements of scaling, traffic and data access patterns, serverless architectures help to provision the exact resources that the workload needs.

    Read the Performance Efficiency whitepaper 

  • This Guidance is designed to be fully optimized for cost, using only resources where necessary and only accessing data using the services appropriate for the business need.

    Read the Cost Optimization whitepaper 

  • By using managed services and dynamic scaling, you minimize the environmental impact of the backend services. This Guidance uses technologies that support data and access storage patterns that need to be monitored. Doing so ensures that assets, such as data, are stored in the optimum solution based on the read and write access patterns, with close attention to scaling of compute resources closely aligned to the demand.

    Read the Sustainability whitepaper 

Sample Code

Start building with this sample code. [Text]

Open sample code on GitHub
Go to Readme

Related Content

AWS for Industries
Blog

How AWS is supporting Buy Now Pay Later (BNPL)

The concept of purchasing an individual item in multiple installments is not new. Large department stores have offered this for decades in what is called layaway. The notion of Buy Now Pay Later (BNPL) is similar, the only difference is that the merchant releases merchandise at first deposit, with intention to receive multiple installments paid thereafter. 
 
This post demonstrates how financial Services institutions can leverage AWS to create BNPL journeys.
Read the full blog post 

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.