Payments are the one part of a system that cannot have a bad day. Money moves, ledgers must reconcile, and every touch sits inside PCI-DSS scope and audit review. Debtrak is an ISO 27001 and PCI-DSS collections platform, and the requirement was never an integration project — it was an owner for the gateway configuration, the reconciliation path, the incident response and the compliance evidence, continuously.
We manage the payment gateway layer end to end: merchant and gateway configuration, tokenised card storage so raw card data never enters application scope, hosted and redirect payment flows, scheduled instalment and arrangement handling, surcharge and fee logic, failed-payment retry and dunning rules, chargeback and dispute workflow, and daily settlement reconciliation against the debtor ledger. Exceptions are surfaced the same day rather than found at month-end. Nothing ships without a reconciliation path and a complete audit trail.
Debtrak (ISO 27001, PCI-DSS) · tokenised card storage · hosted and redirect payment flows · instalment and arrangement scheduling · surcharge and fee logic · retry, dunning, chargeback and dispute handling · daily settlement reconciliation · Power BI reconciliation and exception dashboards · signed webhooks with idempotency keys.
The environments run on AWS and the architecture is built for the compliance posture payments demand: VPC isolation with private subnets for anything touching cardholder scope, KMS-managed encryption at rest and TLS in transit, Secrets Manager for gateway credentials with automated rotation, IAM least-privilege roles and no shared accounts, WAF and Shield in front of public endpoints, API Gateway with throttling and request validation, Lambda for event-driven settlement and webhook processing, SQS with dead-letter queues so a failed payment event is never silently lost, Step Functions for multi-stage arrangement workflows, RDS with encrypted automated backups and point-in-time recovery, S3 with object-lock retention for statements and audit artefacts, CloudTrail and CloudWatch with alarming for a tamper-evident audit trail, GuardDuty and Security Hub for continuous threat detection, and multi-AZ deployment with tested restore procedures. Infrastructure is defined as code, so the control environment is reviewable and reproducible rather than described in a document nobody has read.
Anomaly detection over settlement and failed-payment data so an unusual pattern is flagged the same day, and assisted drafting of operational correspondence inside strict guardrails. Human approval is mandatory on anything affecting an account, and every automated step is logged.
Extending anomaly detection across gateway routing performance, and grounded assistants that answer internal questions about arrangement and settlement status from the client’s own records — with a hard refusal boundary on anything that would move money or alter an account.