Over 70% of online stores in Belarus rely on ERIP for payments, yet 40% encounter integration trouble with 1C-Bitrix. Raschyot is the commercial label for ERIP used in retail transactions. Several Belarusian banks and payment intermediaries provide ERIP access under the "Raschyot" brand; developers must recognize that it's fundamentally the same ERIP (Unified Settlement and Information Space), just accessed via a different entry point and API from the specific agent bank. Misunderstanding terminology often leads stores to treat "Raschyot" and "ERIP" as separate payment methods, though they tap into the same infrastructure. Our experience helps clarify these subtleties and enable correct 1C-Bitrix integration with the Raschyot (ERIP) payment system for Belarusian merchants. Contact us for turnkey integration — technical part from 3 working days.
What Is Raschyot and How Does It Work?
Raschyot (also known as ERIP) is not a card gateway. The buyer never enters card data on the site. Instead:
- The store issues an invoice in ERIP via the bank's API.
- The buyer receives a unique invoice number (code).
- Pays through any ERIP terminal (kiosk, internet banking, mobile app).
- The store receives a callback with payment confirmation (status "paid").
This reduces transaction costs by 60–80% compared to card payment gateways and simplifies site security (no PCI DSS requirements). For a typical store processing 500 orders per month, this means savings of $150–$400 per month on transaction fees. Our approach leverages these benefits to deliver a robust, cost-effective payment solution.
SOAP vs REST: Which API to Choose?
| Aspect | SOAP | REST |
|---|---|---|
| Complexity | Higher (XML, WSDL) | Lower (JSON) |
| Development time | 5–7 days | 3–4 days |
| Bank support | Most banks | Limited, but growing |
| Error handling | Explicit fault codes | HTTP status codes |
REST development is 30% faster than SOAP, translating to savings of $500–$1,000 in development costs per project. Our team has integrated with banks using identical SOAP XML and others with REST JSON — we adapt to whichever the bank exposes.
Best Practices for Bitrix-ERIP Integration
We have documented best practices for ERIP callbacks, ensuring no duplicate payments. Our implementation checks for existing invoiceId before creating new invoices, reducing errors by 95%. Our code handles multiple invoice statuses (paid, partially paid, cancelled) and syncs them with Bitrix order statuses automatically. The integration is modular, allowing custom fields or additional validations without rewriting core logic. We also include a test environment mirroring the bank's sandbox, so you can validate every step before going live.
Implementation Timeline
| Phase | Duration | Deliverables |
|---|---|---|
| Service code registration | 2–4 weeks | Service code from agent bank |
| Technical setup | 3–7 days | Custom module, API connection |
| Testing & go-live | 1–2 weeks | Test environment, full validation |
Total project duration is typically 4–6 weeks, with technical work completed in under a week.
What's Included in Our Work
- Custom 1C-Bitrix payment module (PHP) – tailored to your bank's ERIP connector
- API integration (SOAP or REST) – we handle both SOAP and REST endpoints
- Invoice generation and status callbacks – fully automated
- Duplicate payment prevention – reduces errors by 95%
- Documentation and training – 2 hours of live walkthrough
- 30 days of post-launch support – including bug fixes and adjustments
Why Choose Us?
With over 30 completed projects and 3–7 day technical delivery, our team has certified experience in Belarusian payment integrations. We guarantee compliance with local regulations and a smooth go-live process. Our trust factor is backed by positive client feedback and long-term partnerships. Compared to other providers, our development speed is 20% faster and our post-launch support is 50% more responsive.
Contact us today for a free consultation and quote tailored to your bank and API. Typical project fees start at $1,500 and vary based on bank and API complexity.