Add-ons Crypoverse - Cryptocurrency Payment Gateway [BTC, LTC, ETH] v3.0.4

Crypoverse - Crypto Payment Gateway
Updates: v3.0.1 → v3.0.4

We've released several important updates addressing critical bugs and improving the payment logging system.

---

What's Fixed

v3.0.4 (October 9, 2025)

• Fixed RMMP product names showing "Order - XXXXX" instead of actual resource titles
• Fixed "Unknown user/profile" entries in payment logs
• Added payment initiation logging for better transaction tracking
• Removed unnecessary technical log entries

v3.0.3 (October 9, 2025)

• Fixed payment provider logs not appearing in Admin CP
• Improved XFRM resource name detection

v3.0.2 (October 8, 2025)

• Fixed server error: "Undefined constant PAYMENT_CANCELED"
• Restored detailed payment logging
• Fixed underpaid transaction handling

v3.0.1 (October 8, 2025)

• Fixed critical webhook error: "Undefined constant PAYMENT_PENDING"
• Fixed cancelled payment processing

---

Installation

1. Download the latest version
2. Upload files via Admin CP → Add-ons → Install/Upgrade
3. No configuration changes required

---

Key Improvements

• Better Product Names: All purchasable types (user upgrades, XFRM resources, RMMP) now show correct titles
• Cleaner Logs: Payment provider logs show proper user/profile information with better transaction tracking
• Stable Processing: All webhook constants fixed - no more server errors

---

Support & Resources

• Support: [email protected] (Response within 1 hour)
• Documentation: Best Crypto Payment Gateway & Processor for Businesses | Crypoverse
• Dashboard: Best Crypto Payment Gateway & Processor for Businesses | Crypoverse

Note: These are critical bug fixes. All users should upgrade to v3.0.4 immediately.

Crypoverse v3.0.1 - Update Complete
Critical Bug Fixed
Issue: Undefined constant XF\Payment\CallbackState:AYMENT_PENDING
Error Location: CryptoProvider.php:791
Impact: Server errors when underpaid/unknown payment statuses received
Cause: Used non-existent PAYMENT_PENDING constant (doesn't exist in XenForo)
Solution:
Removed all CallbackState:AYMENT_PENDING usage
For pending payments: Don't set paymentResult (let XenForo handle)
For errors: Use CallbackState:AYMENT_ERROR
New Feature: Underpaid Transaction Handling
Added comprehensive "underpaid" status support:
case 'underpaid':
$state->paymentResult = CallbackState:AYMENT_ERROR;
$state->logType = 'error';
$state->logMessage = 'Payment underpaid - Expected: 0.000261 Bitcoin, Received: 0.000228 Bitcoin...';
$state->logDetails = [
'expected_amount' => '0.000261',
'received_amount' => '0.000228',
'shortfall' => '0.000033'
];
Benefits:
Proper logging to Payment Provider Logs (not server errors)
Detailed underpayment information
Automatic shortfall calculation
Clear transaction tracking
Enhanced Status Handling
Now Supports:
completed → Payment received
pending → Awaiting confirmation
underpaid → Payment error with details
expired / timed-out → Cancelled
failed / error → Payment error
Unknown statuses → Logged with full raw data
Files Modified
addon.json
Version: 3.0.0 → 3.0.1
Version ID: 3000000 → 3000100
Payment/CryptoProvider.php
Fixed PAYMENT_PENDING error (lines 575, 791)
Added underpaid status handling (lines 779-807)
Added expired/failed status handling (lines 809-826)
Improved unknown status logging (lines 828-838)
Updated version comments to 3.0.1
_data/hashes.json
Updated addon.json hash: c88457495c36b178945018837f29d641
Updated CryptoProvider.php hash: a102902523067305b91edf87ad95da09
CHANGELOG.md (NEW)
Complete version history
Detailed 3.0.1 changes
Upgrade instructions

~Version: 3.0.1 Status: Production Ready Date: October 4, 2025