fsi-payments-credit-card

Design AWS microservices architecture for migrating credit card issuer systems.

6|Updated Jun 23, 2026
One-click install
npx skills add https://github.com/aws-samples/sample-fsi-reference-architecture-jp --skill fsi-payments-credit-card
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fsi-payments-credit-card
Source: https://github.com/aws-samples/sample-fsi-reference-architecture-jp/tree/main/skills/fsi-payments-credit-card
Command: npx skills add https://github.com/aws-samples/sample-fsi-reference-architecture-jp --skill fsi-payments-credit-card

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This skill addresses the complexity of migrating mission-critical credit card issuer workloads from on-premises to AWS, ensuring high availability and performance while managing regulatory compliance.

Core Features & Use Cases

  • Reference Architecture: Provides a blueprint for a microservices-based, multi-region Active-Active credit card processing system.
  • Performance Optimization: Offers guidance on using request hedging to mitigate DynamoDB tail latency and selecting appropriate databases for specific transaction needs.
  • Use Case: Use this skill when designing or reviewing a credit card authorization and reconciliation system that requires 99.99% availability and 5,000 TPS throughput.

Quick Start

Use the fsi-payments-credit-card skill to generate a design review checklist for a new credit card issuer workload migration.

Frequently Asked Questions about fsi-payments-credit-card

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I architect a multi-region Active-Active credit card issuer system on AWS?

Architect a multi-region Active-Active credit card issuer system by adopting a microservices-based design on AWS. This approach uses strategic AWS service selection to achieve 99.99% availability and high-TPS authorization workflows while maintaining on-premises settlement.

What is the best way to mitigate DynamoDB tail latency in high-TPS credit card authorization workflows?

Mitigate DynamoDB tail latency in credit card authorization workflows by applying request hedging patterns. This performance optimization technique ensures high throughput and consistent response times required for mission-critical payment processing.

Can I maintain on-premises settlement while migrating credit card authorization to AWS?

Yes, you can maintain on-premises settlement during credit card authorization migration. The reference architecture supports a hybrid model, allowing resilient AWS microservices to handle authorization while integrating with existing on-premises settlement systems.

Does this architecture support PCI DSS compliance for credit card processing workloads?

Yes, the architecture satisfies strict PCI DSS compliance requirements for credit card processing workloads. It achieves this through strategic AWS service selection and specific architectural patterns designed for highly regulated financial environments.

How do I design a credit card reconciliation system for 5,000 TPS throughput?

Design a credit card reconciliation system for 5,000 TPS by selecting appropriate databases for specific transaction needs and utilizing a microservices architecture. This ensures the required high throughput and 99.99% availability.

When do I need request hedging for payment microservices on AWS?

You need request hedging for payment microservices on AWS when high-TPS authorization workflows demand strict performance guarantees. It specifically mitigates DynamoDB tail latency, ensuring the system maintains its required throughput and availability.