repository·main·Indexed 19 days ago
https://github.com/maajiko/epayAn open-source payment gateway aggregator developed by Zhengzhou Zhuimeng Network Technology Co., Ltd. It provides a unified API and management backend to integrate multiple payment channels including Alipay, WeChat Pay, Tenpay, QQ Wallet, and UnionPay. Key features include RSA verification, risk control, plugin extensibility (such as Bepusdt for USDT TRC20), and an admin dashboard for real-time financial statistics and profit analysis.
The system offers several core capabilities for payment management:
The dashboard provides a high-level overview of the system's health and financial performance through several key metrics:
Note: Financial statistics (Balance, Settlement, and Income tables) are updated approximately every 1 hour.
The template/index2/index.php file serves as a public-facing landing page template for the Rainbow Easy Pay system. It is a PHP-based entrypoint that renders the site's homepage, including navigation, service descriptions, and FAQ sections.
Security Note: This file requires the constant IN_CRONLITE to be defined. If accessed directly without the proper environment context, the script will exit immediately to prevent unauthorized execution.
Key Features Rendered:
/user/reg.php), Login (/user/), Documentation (/doc.html), and Payment Testing (/user/test.php) if enabled.$conf configuration array to populate site metadata (title, keywords, description, sitename, etc.).<?php
if(!defined('IN_CRONLITE'))exit();
?>
<!-- HTML Content follows -->When developing or customizing payment templates in the epay system, you can access global configuration settings via the $conf associative array. These variables are injected into the template scope and allow you to dynamically display site-specific information.
Commonly used keys in $conf include:
sitename: The name of the payment platform.title: The HTML <title> of the page.keywords: Meta keywords for SEO.description: Meta description for SEO.settle_rate: The settlement fee rate (e.g., 0.03 for 3%).settle_money: The minimum amount required for automatic settlement.settle_fee_min: The minimum withdrawal/settlement fee.settle_fee_max: The maximum withdrawal/settlement fee.kfqq: The Customer Service QQ number used for contact links.test_open: A boolean flag to determine if the online testing link (/user/test.php) should be visible.footer: Custom footer text.Additionally, the following global constants are available for path resolution:
STATIC_ROOT: The base path for local static assets (CSS, JS, Images).cdnpublic: The base URL for assets served via a CDN.IN_CRONLITE: A security constant. If this is not defined, the script will exit immediately to prevent direct access.<!-- Example of using configuration variables in a template -->
<title><?php echo $conf['title']?></title>
<p>Settlement rate is as low as <?php echo $conf['settle_rate']; ?>%!</p>
<a href="https://wpa.qq.com/msgrd?v=3&uin=<?php echo $conf['kfqq']?>&site=pay">Contact Support</a>To prevent direct access to template files via a web browser, all template entrypoint files must check for the definition of the IN_CRONLITE constant. If this constant is not defined, the script will exit immediately.
This ensures that templates are only rendered through the system's core controller/routing mechanism.
<?php
if(!defined('IN_CRONLITE'))exit();
?>To prevent direct unauthorized access to template files, the system checks for a specific constant. If this constant is not defined, the script will terminate immediately.
if(!defined('IN_CRONLITE'))exit();Ensure that your entrypoint or controller defines IN_CRONLITE before including template files.
The dashboard provides a visual representation of settlement amounts using a spline chart (likely via ui-jq or a similar plugin integration).
Data Source: The chart data is generated server-side from the pre_settle table, selecting the last 9 settlement records for the current user.
Chart Configuration:
[index, money].max_settle + 10 to ensure visibility.The documentation is organized into several functional modules. Developers can navigate to specific implementation details for each:
When developing or customizing templates for the Rainbow E-pay system, you can access global configuration settings via the $conf associative array and system information via superglobals.
Commonly used keys in $conf include:
$conf['title']: The page title.$conf['keywords']: SEO keywords.$conf['description']: SEO description.$conf['sitename']: The name of the payment platform.$conf['test_open']: Boolean flag to determine if the online testing link (/user/test.php) should be visible.$conf['email']: Contact email.$conf['kfqq']: Customer service QQ number.$conf['hzlink1'], $conf['hzlink2']: Partner website links.$conf['hzhb1'], $conf['hzhb2']: Partner website names.$conf['footer']: Footer copyright or text.Other available variables:
$cdnpublic: Path to the CDN-hosted public assets.$STATIC_ROOT: Path to the local static assets directory.$_SERVER['HTTP_HOST']: The current domain name.$_SERVER['HTTP_HOST']: The current domain name.To prevent direct access to template files and ensure they are only rendered through the system's controlled lifecycle, all template files must define the IN_CRONLITE constant. If this constant is not defined, the script will exit immediately.
<?php
if(!defined('IN_CRONLITE'))exit();
?>When the mod is set to index, the application behavior is governed by the $conf['homepage'] setting:
1: Redirects the user immediately to the /user/ directory via JavaScript.2: Loads the URL specified in $conf['homepage_url'] within an HTML <frameset>.