{"repo":"aws-solutions-library-samples/guidance-for-payment-systems-using-event-driven-architecture-on-aws","free":true,"listed":false,"github":"https://github.com/aws-solutions-library-samples/guidance-for-payment-systems-using-event-driven-architecture-on-aws","clone":"git clone https://github.com/aws-solutions-library-samples/guidance-for-payment-systems-using-event-driven-architecture-on-aws.git","description":"This guidance focuses on the part of payments processing systems that post payments to recieving accounts. In this phase, inbound transactions are evaluated, have accounting rules applied to them, then are posted into customer accounts.","language":"HCL","stars":25,"topics":["distributed-systems","event-driven-architecture","payments","serverless"],"license":"MIT-0","category":"auth-billing-email","readme_excerpt":"Guidance for Building Transaction Posting Systems Using Event-Driven Architecture on AWS This guidance focuses on payment processing subsystems responsible for posting payments to recieving accounts. In this phase of payment processing, inbound transactions are evaluated, have accounting rules applied to them, then are posted into receiving accounts. The accounting rules dictate the work that needs to happen to successfully process the transaction. Inbound transactions are assumed to have been authorized by an upstream process. In traditional architectures, the upstream system writes transactions to a log. The log is periodically picked up by a batch-based processing system system, processed in bulk, then eventually posted to customer accounts. Transactions (and customers!) must wait for the next batch iteration before being processed, which can take multiple days. Instead, this sample architecture uses event-driven patterns to post transactions in near real-time rather than in batches. Transaction lifecycle events are published to an Amazon EventBridge event bus. Rules forward the events to processors, which act on the events, then emit their own events, moving the transaction through its lifecycle. Processors can be easily added or removed as organization needs change. Customers get a more fine-grained account balance and can dispute transactions much sooner. Processing load is offloaded from batch systems during critical hours. Table of Contents 1. Overview - Architecture ","default_branch":null,"files":null,"tree":[],"storefront":"/r/aws-solutions-library-samples","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/aws-solutions-library-samples/guidance-for-payment-systems-using-event-driven-architecture-on-aws/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}