Data minimization
Avoid PAN, CVV, cryptographic keys and cardholder financial credentials; use opaque references.
Principles
The workflow is designed around artwork and approval records, not payment credentials.
In the workflow
Designed to stay out
Avoid PAN, CVV, cryptographic keys and cardholder financial credentials; use opaque references.
Separate institution assets, policies, access and logs.
Role-based access and short-lived service credentials.
Encryption in transit and at rest, key and secret management, secure upload validation and malware scanning where appropriate.
Actor, timestamp, policy and model version, decision and asset hash on every review.
Monitoring, incident response, backups, restore tests, rate limits, webhook signing and retry logic.
Contractual data processing roles, retention schedules, deletion workflows and data subject rights handling.
CI/CD controls, code review and dependency scanning, with penetration tests as the program matures.
Traceability
Each review captures who acted, when, under which policy and model version, what they decided and which exact asset they decided on.

Compliance
Requirements vary with the actual architecture, your contracts, applicable laws and card-network program rules. We work through them with your security, risk and compliance teams for each integration.
Minimizing card data can narrow scope, but it doesn't rule out every card-industry obligation. We'll map what applies to your setup together.
We only list a certification or independent report once it's completed and available. Ask us for our current status.
Trust center
Materials we're preparing for due diligence. Items marked "When available" or "When earned" don't exist yet.
Bring your questionnaire, architecture questions or privacy requirements. We'll set up a session with the right people.
Please don't include card numbers, credentials or confidential security details in this form.