Paystack payment method for RISE CRM

✨ Key Features

• Invoice Payments: One-time payments from RISE invoice pages with automatic “paid/partially paid” updates.
• Subscriptions: Supports recurring invoices/plans (where your RISE workflow uses recurring billing) with Paystack authorization/charge flows.
• Multiple Channels: Cards, bank transfer, USSD, and mobile money where regionally available.
• Regional Currencies: Uses Paystack’s supported currencies per account/region (e.g., NGN, GHS, ZAR, and USD where applicable).
• Test & Live Modes: Toggle between sandbox and production using separate keys.
• Webhooks with Signatures: Handles asynchronous events; verifies signature header for authenticity; retry-safe processing.
• Refunds Flow: Admin tools to record/reflect refunds initiated from Paystack dashboard.
• Payer Experience: Lightbox/redirect checkout, automatic reference mapping, and return/thank-you pages inside RISE.
• Logs & Audits: Response logging for debugging; invoice activity timeline entries for finance audits.
• Localization: Currency symbol, thousand/decimal formatting, and translatable strings.

⚙️ Technical Stack

• Platform: RISE CRM (PHP) with payment method extension points.
• Backend: PHP 8.x compatible; uses cURL/JSON for Paystack REST APIs.
• Security: HMAC-style webhook signature check; HTTPS required; CSRF protection on local forms.
• Server Requirements: Nginx/Apache, PHP extensions: curl, openssl, json, mbstring.
• Config: Environment variables or RISE settings page for API keys, webhook secret, callback URL.

🧩 Installation Guide

1. Prerequisites: RISE CRM installed and working; a verified Paystack account.
2. Upload Files: Copy the module folder to your RISE add-ons/payment-methods directory as documented by your RISE version.
3. Activate: In RISE → Settings → Payment Methods, enable Paystack.
4. API Keys: Enter Public Key and Secret Key for Test and/or Live modes.
5. Webhook Setup: In the Paystack dashboard, add the Webhook URL shown in RISE and save. Ensure your server is reachable via HTTPS.
6. Currencies & Channels: Confirm your RISE default currency matches your Paystack account availability; enable desired channels in Paystack.
7. Try a Test Payment: Create a small test invoice and pay in Test Mode to validate status updates and logs.
8. Go Live: Switch to Live Mode, rotate keys if needed, and verify webhook deliveries.

📦 Deliverables

• Paystack payment method module for RISE CRM (PHP sources).
• Admin settings view (keys, mode, webhook URL, currency hints).
• Client-side checkout integration (redirect/lightbox as supported).
• Webhook controller with signature verification and logging.
• Readme/Quick-start with troubleshooting notes.

📱 Supported Platforms

• RISE CRM: Current stable versions that support external payment methods.
• Paystack Regions: Operates in Paystack-supported countries; channels vary by region.
• Browsers: Chrome, Firefox, Safari, Edge (current versions).
• Server OS: Ubuntu/Debian/CentOS recommended; Windows Server compatible.

🧠 Notes

• License: Distributed under the GPL for lawful use, study, modification, and redistribution per GPL terms.
• Customization Tips: Keep gateway calls in a dedicated service; map Paystack statuses to RISE invoice states; enable idempotency to avoid double-posting on retries.
• Security: Use HTTPS everywhere; store secrets outside VCS; verify webhook signatures; log and rate-limit callbacks.
• Accounting: Reconcile fees/charges from Paystack settlements; set exchange rate policy when using foreign-currency invoices.
• SEO Assurance: Public docs/landing pages include meta fields and clean URLs; client portal/checkout is private and should remain noindex.

👨‍💻 Original Developer Credit

We acknowledge the original developer and marketplace publisher as the authoritative source of this integration’s concept and roadmap.
For provenance and official updates, see the product page on
CodeCanyon (or the developer’s official site).

🔒 Disclaimer

This is a GPL redistribution intended for learning, testing, and compliant use under the GPL. We are not the original authors and do not claim endorsement or affiliation.
Trademarks belong to their respective owners. Before production, confirm regional eligibility, channel availability, and third-party dependency licenses; perform security and compliance reviews (e.g., PCI considerations, data protection).