Compliance attestation
PCI-DSS — Self-Assessment Questionnaire A
Hechadao Pte Ltd · Reviewed 2026-05-12
Summary
Hechadao Pte Ltd operates under PCI-DSS SAQ-A scope. We are an e-commerce / point-of-sale merchant who has fully outsourced all cardholder-data functions to validated, PCI-DSS-compliant third-party service providers (Fiuu, with NETS and direct-payment-rail integrations underway). SuperBizFlow never sees, stores, processes, or transmits cardholder data on its own systems.
What this means in plain English
- We don't see card numbers. When a customer pays by card on a SuperBizFlow-built tenant page, the browser POSTs the card data directly to Fiuu's PCI-DSS-certified hosted page. Our server only receives a callback with a tokenised transaction id.
- We don't store card numbers. Saved-card / recurring billing uses Fiuu's tokenisation — we hold the token, not the PAN.
- We don't key in card numbers at the POS. Counter payments use either: cash, NETS QR (no PAN), PayNow QR (no PAN), Fiuu hosted form (no PAN on our wire), or an integrated EFTPOS terminal (PAN flows directly between the terminal and the bank — never through SuperBizFlow).
Compliance scope
SAQ-A applies because
- SuperBizFlow accepts only card-not-present (CNP) e-commerce transactions.
- Cardholder data is handled entirely by Fiuu (and forthcoming NETS-direct, Stripe Terminal integrations), each of which holds an independent PCI-DSS attestation.
- SuperBizFlow has no electronic storage of cardholder data.
- SuperBizFlow has no physical receipt-storage policy that captures PAN.
Out of scope
- Cardholder Data Environment (CDE) — SuperBizFlow has none.
- Network segmentation for cardholder data — SuperBizFlow has no such network.
- Quarterly ASV scans — only required when a CDE exists.
In scope
- Vendor selection due diligence (Fiuu, NETS, Stripe Terminal AOC verified annually).
- Hosted-page integration: documented, tested for redirection integrity.
- Annual self-attestation refresh against SAQ-A questionnaire (this document).
Supporting controls (beyond SAQ-A)
- Encryption at rest — Postgres database (Railway managed) encrypts all data at rest with AES-256.
- Encryption in transit — TLS 1.3 enforced on every endpoint; Strict-Transport-Security header sent.
- Webhook signature verification — Fiuu skey verification on every inbound callback; same pattern for the in-progress NETS / Stripe integrations.
- Tamper-evident audit log — every refund, void, and payment event recorded in a SHA-256 hash chain. Tampering attempts surface as broken-chain incidents in the Ops Center.
- Tenant fail-closed — public payment routes resolve tenant context before any read or write, so a guessed reference id cannot leak data across tenants.
- Quarterly penetration tests — scheduled in the SuperBizFlow risk-management calendar (first test: month 2 of Hechadao production deployment).
Third-party service providers
| Provider | Function | Compliance evidence |
|---|---|---|
| Fiuu (Razer Pay) | Card + PayNow + e-wallet acceptance | PCI-DSS Level 1 AOC, refreshed annually |
| NETS (planned) | NETS QR + NETS Terminal | PCI-DSS via NETS' in-house attestation |
| Stripe Terminal (planned) | Integrated EFTPOS | PCI-DSS Level 1 service provider |
| Railway | Cloud infrastructure | SOC 2 Type II |
| Twilio | SMS + WhatsApp delivery | SOC 2 Type II, ISO 27001 (no cardholder data handled) |
Request the signed attestation
For procurement / IMDA / banking due-diligence requests, email [email protected] with the requesting entity, the engagement reference, and the scope of the audit. We will return the signed SAQ-A and Attestation-of-Compliance (AOC) within two business days.
Document control
- Document owner: Hechadao Pte Ltd · Compliance Officer
- Reviewed: 2026-05-12
- Next review due: 12 months from review date (annual SAQ-A refresh)
- Triggers for re-review: any new payment processor / any change to cardholder-data flow