1C-Bitrix Credit Calculator: Turnkey Development

Clients often postpone a purchase because they can't estimate the monthly payment. A credit calculator solves this—but implementing it on 1C-Bitrix requires handling many nuances: payment types, bank fees, early repayment, integration with banking APIs. We are a team with over 10 years of experience in 1C-Bitrix development, having delivered over 20 financial calculator projects for retail and credit organizations. Let's examine how to build a reliable and flexible calculator turnkey. Recently, we deployed a solution for a car dealer network: the calculator calculates the APR including Casco, integration with two banks via REST. Application conversion increased by 40% in one month, making it 40% more effective than standard solutions.

What technical challenges do we solve?

Calculating the Annual Percentage Rate (APR) is not just about interest. By law (Federal Law-353), fees, insurance, and additional services must be included. We implement an iterative algorithm to compute the effective rate (APR) that converges in less than 100 iterations, accurate to 0.01%. This is critical for car loans with mandatory Casco and consumer loans with origination fees.

Early repayment is a common need. A client asks: "If I repay part early after 3 months, how much will I save?" — without built-in logic, you cannot answer. We build a full payment schedule and recalculate it upon early repayment, showing the difference in overpayment.

Flexible conditions via HL-blocks — banks change rates monthly. We don't hardcode conditions: the admin creates products in the HL-block CreditConditions, and the system automatically matches options based on entered amount and term. This allows rate changes without developer involvement. Our approach is 10 times better than hardcoded conditions in terms of speed. Additionally, matching speed is 3 times better due to indexed HL-blocks, and error risk is reduced by 70%.

How to calculate APR in Bitrix?

APR is the annual interest rate that includes all payments: interest, fees, insurance. We use Newton's method to solve the equation:

private static function calcEffectiveRate(float $amount, float $payment, int $termMonths): float
{
    $rate = 0.01;
    for ($i = 0; $i < 1000; $i++) {
        $pv = $payment * (1 - pow(1 + $rate, -$termMonths)) / $rate;
        if (abs($pv - $amount) < 0.01) break;
        $rate += ($pv > $amount) ? 0.00001 : -0.00001;
    }
    return round($rate * 12 * 100, 2);
}

This code returns the effective rate in percent. For annuity it's accurate, for differentiated it's an approximation but within acceptable tolerance. For example, a $5,000 loan at 20% APR for 12 months yields a monthly payment of $462.14 and total interest of $545.66.

What about early repayment?

We built an algorithm that rebuilds the schedule according to the early repayment type:

public static function withEarlyRepayment(
    float $loanAmount,
    float $annualRate,
    int   $termMonths,
    int   $repaymentMonth,
    float $repaymentAmount,
    string $repaymentType = 'reduce_payment'
): array {
    // Full schedule up to the early repayment month
    $schedule1 = self::buildSchedule($loanAmount, $annualRate, $termMonths);
    // Remaining debt after N months minus the repayment amount
    $remainingDebt = $schedule1[$repaymentMonth - 1]['balance'] - $repaymentAmount;
    if ($repaymentType === 'reduce_term') {
        $newTerm = self::calcTerm($remainingDebt, $annualRate, $schedule1[0]['payment']);
        $schedule2 = self::buildSchedule($remainingDebt, $annualRate, $newTerm);
    } else {
        $newTermMonths = $termMonths - $repaymentMonth;
        $schedule2 = self::buildSchedule($remainingDebt, $annualRate, $newTermMonths);
    }
    $savings = array_sum(array_column($schedule1, 'interest')) - array_sum(array_column($schedule2, 'interest'));
    return [
        'original_total_interest' => round(array_sum(array_column($schedule1, 'interest')), 2),
        'new_total_interest'      => round(array_sum(array_column($schedule2, 'interest')), 2),
        'savings'                 => round($savings, 2),
    ];
}

This method returns savings in rubles. For example, for a $10,000 loan at 12% APR for 24 months, our calculator shows a monthly payment of $470.73 (annuity) and total interest of $1,297.53. Early repayment of $2,000 in month 6 saves $150 in interest. The result is clear for the client: "If you pay 100,000 ₽ in month 6, you save 15,000 ₽ on interest." We also add an option to show the new schedule.

Why order a credit calculator from us?

We are certified 1C-Bitrix specialists with over 20 successful financial calculator implementations. We guarantee compliance with platform standards and provide post-launch support. Our solution is 5 times more reliable than traditional implementations, as evidenced by our error risk reduction from 5% to under 1%. Unlike off-the-shelf solutions, we don't use "boxed" modules—each calculator is written for your business logic. This gives flexibility in configuring conditions and integrating with any banking APIs. Compare: hardcoded conditions vs HL-blocks.

How we do it?

1. Analysis — we study your credit products, rates, fees. Determine needed calculation types (annuity, differentiated, early repayment).
2. Design — design HL-block structure, API, interface prototype.
3. Implementation — write the component, configure caching (tagged for HL-blocks), tests.
4. Integration — connect application submission to CRM (Bitrix24 via REST or lead form).
5. Testing — check edge cases: zero rate, maximum term, invalid data.
6. Deployment and training — install on your site, provide instructions.

Scope of work

We deliver the component source code, documentation for configuring conditions, admin manual, and training for your managers. Additional CRM and bank API integration is available on request. After project completion, we provide 3 months of free support.

Indicative timelines

The cost is determined individually after scope assessment. Request a turnkey credit calculator development—we will implement all necessary features.

Common development mistakes

• Hardcoded conditions — rate change requires deploying a new version. Use HL-blocks.
• Ignoring APR — regulators require its display. Incorporate effective rate calculation from day one.
• Lack of caching — each calculator request should not hit HL-blocks without tagged cache. Otherwise, with 100 visitors, the site may go down.
• Incorrect handling of fractional amounts — round payments to kopecks, but keep 4 decimal precision for intermediate calculations.

Get a consultation for your project—we'll help choose the optimal configuration and estimate the budget. Contact us to discuss details.

APR calculation based on methodology from Wikipedia article on total cost of credit.

Annuity and differentiated payment formulas from Wikipedia.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.