payments-dashboard/package.json

{
  "name": "payments-dashboard",
  "version": "1.0.0",
  "type": "module",
  "description": "Payments CSV ingestion to Slack App Home dashboard",
  "files": [
    "src/"
  ],
  "dependencies": {
    "@aws-sdk/client-dynamodb": "^3.600.0",
    "@aws-sdk/client-s3": "^3.600.0",
    "@aws-sdk/client-ssm": "^3.600.0",
    "@aws-sdk/lib-dynamodb": "^3.600.0",
    "csv-parse": "^5.5.0"
  }
}
Initial SAM stack: payments CSV to Slack App Home Two Lambda functions: - processPaymentCsv: S3 trigger, parses CSV, stores dashboard in DynamoDB - slackAppHome: API Gateway endpoint for Slack events, publishes Home tab view 2026-04-09 13:29:28 -04:00			`{`
			`"name": "payments-dashboard",`
			`"version": "1.0.0",`
			`"type": "module",`
			`"description": "Payments CSV ingestion to Slack App Home dashboard",`
Log BoA submissions to DDB and surface in Slack App Home Capture response headers, body, and transactionId on every check-issue API call; persist as boa_txn#<ts>#<action> records with 90-day TTL. Add "Recent BoA Submissions" section to App Home showing the last 10 with click-to-copy transactionId. Motivation: BoA support asked for a transactionId from a past successful call and we had no way to recover it from CloudWatch summary logs alone. Also adds simulate-csv.cjs (dry-run preview) and stampli-uploader.sh (launchd-invoked S3 uploader), and gitignores debug artifacts. 2026-04-20 17:40:55 -04:00			`"files": [`
			`"src/"`
			`],`
Initial SAM stack: payments CSV to Slack App Home Two Lambda functions: - processPaymentCsv: S3 trigger, parses CSV, stores dashboard in DynamoDB - slackAppHome: API Gateway endpoint for Slack events, publishes Home tab view 2026-04-09 13:29:28 -04:00			`"dependencies": {`
			`"@aws-sdk/client-dynamodb": "^3.600.0",`
			`"@aws-sdk/client-s3": "^3.600.0",`
Add VPC/NAT for static IP, dedup payments by check number, SSM token - VPC with NAT Gateway for static outbound IP (52.86.95.107) for BoA API - Payments stored as individual DynamoDB items keyed by check number - Slack bot token fetched from SSM at runtime instead of CF parameter - Slack Lambda scans payment items instead of reading single blob 2026-04-09 14:27:34 -04:00			`"@aws-sdk/client-ssm": "^3.600.0",`
Initial SAM stack: payments CSV to Slack App Home Two Lambda functions: - processPaymentCsv: S3 trigger, parses CSV, stores dashboard in DynamoDB - slackAppHome: API Gateway endpoint for Slack events, publishes Home tab view 2026-04-09 13:29:28 -04:00			`"@aws-sdk/lib-dynamodb": "^3.600.0",`
			`"csv-parse": "^5.5.0"`
			`}`
			`}`