Overview
Once internet top-up orders are fulfilled, retrieve card codes and transaction numbers from the API and deliver them securely to customers. Card codes must be handled with care as they represent value.Security Critical: Card codes are valuable credentials. Always encrypt during storage and transmission.
Card Data Structure
Fulfilled orders contain three key fields:- card_code: The rechargeable code to enter (primary credential)
- num_trans: Algérie Télécom transaction number (proof of purchase)
- date_traitement: Processing timestamp
API Reference
GET /v3/internet/check-id/{id}
Retrieve fulfilled card details
Secure Storage
Always encrypt card codes before storing in your database:Delivery Methods
1. Email Delivery
2. In-App Display
3. SMS Delivery
Complete Delivery Flow
Audit Logging
Log delivery events without exposing card data:Usage Instructions by Type
Provide clear instructions for each service type:Best Practices
Encrypt at Rest
Always encrypt card codes before storing in database
Use HTTPS Only
Never transmit cards over unencrypted connections
Verify Ownership
Check user owns order before showing card
No Plain Text Logs
Never log card codes in plain text
Include Instructions
Always provide clear usage instructions
Audit Trail
Log delivery events without sensitive data
Security Checklist
1
Generate Encryption Key
Create a secure 32-byte encryption key and store in environment variables
2
Encrypt Before Storing
Always encrypt card_code before database insertion
3
Verify User Ownership
Check user ID matches order before displaying card
4
Use HTTPS
Ensure all delivery methods use encrypted transport
5
Audit Logging
Log delivery events without including actual card codes
6
Clear Instructions
Provide step-by-step usage instructions for each service type

