Security and Amazon Integration Readiness

Last updated: 9 October 2026. Public Amazon seller access remains subject to approval and completion of the required security assessment.

Current service

GenPrint has a public HTTPS website and a browser application. The application includes named user accounts, owner/operator roles, functional access areas and seller/store access checks. Kaching Group has 30 personnel; access must be individually assigned rather than assumed for all personnel.

Public Amazon onboarding

The intended public integration uses seller OAuth and approved SP-API roles. Restricted fulfillment data processing depends on Amazon approval and completion of the required assessment. Public developer registration and production application registration are separate steps.

Readiness requirements

Before restricted public onboarding, verify encrypted storage and key recovery, MFA and password controls, managed endpoints, access reviews, complete seller isolation, buyer-data deletion including backups, third-party data handling, security log review and annual penetration testing of the public application. Existing code and policy documents are evidence inputs, not a certification that every requirement is met.

Vulnerability and change management

The repository includes dependency, secret and data-directory-permission scanning plus a remediation ledger. The public application, identity flows, tenant boundaries and staff endpoints must also be included in the security assessment. Findings require an owner, first-detection date, remediation deadline and retest evidence.

Reporting

Report suspected exposure privately to Tony Trieu at aistartup.vn@gmail.com. Do not include access tokens or buyer personal information in an initial report. The incident process must contain access, preserve sanitized evidence, determine affected records, notify Amazon within 24 hours of detection and verify remediation.