Under Nigeria's NDPA 2023, storing Paystack payment data (customer email, phone, amount, reference) is lawful under the "contractual necessity" basis — you need it to fulfill the transaction. You must: (1) only store what you need (data minimisation), (2) delete payment records after your retention period, (3) notify the NDPC and affected customers within 72 hours of a data breach, (4) register with the Nigeria Data Protection Commission (NDPC) if you process data for more than 2,000 persons annually, and (5) never store raw card numbers — Paystack prevents this by design.
The Nigeria Data Protection Act 2023 covers any personal data — information that identifies or can identify a person. In your Paystack integration, this includes:
It does not include anonymised or aggregated data where no individual can be identified.
The lawful basis for storing this data is contractual necessity (NDPA Section 25(1)(b)) — you need to process the data to fulfill the payment contract with your customer. You do not need a separate consent form for storing payment records. However, your privacy policy must disclose that you collect and store this data.
1. Data minimisation
Only store what you need. For a completed transaction, you need: reference, amount, status, customer email, and timestamp. You do not need to store the full webhook payload indefinitely.
2. Retention limits
Define and enforce a retention period. For financial records in Nigeria, 5-7 years aligns with FIRS (Federal Inland Revenue Service) requirements. After this period, delete or anonymise payment records.
3. Security measures
Encrypt sensitive fields at rest. Use TLS for all data in transit. Restrict access to payment tables — only staff who need transaction data for their role should be able to query it.
4. NDPC registration
If your business processes personal data of more than 2,000 Nigerians per year, register with the Nigeria Data Protection Commission (ndpc.gov.ng) and appoint a Data Protection Officer (DPO) or retain a licensed Data Protection Compliance Organisation (DPCO).
5. Breach notification
If your payment database is breached, you must:
Get weekly developer tips
Join 25,000+ developers. Practical guides, job tips, and new content — straight to your inbox.
No spam. Unsubscribe anytime.
This guide is part of the Paystack security and compliance guide.
KES 2,999
The definitive guide to building payment systems with Paystack — from your first transaction to production-grade payment infrastructure across Africa. 9 modules, 47 lessons. Free preview available.
Start Paystack Course