Robotic Partner operates on a strict zero-loss financial model for B2B retailers, aggregators, and enterprise telecom distributors. Because cellular recharge execution occurs in real-time, our software engine utilizes programmatic safeguards to guarantee complete balance protection.
1. Automated Zero-Loss Guarantee
When you dispatch a prepaid recharge transaction through our B2B API or merchant dashboard, funds are conditionally placed in a temporary escrow hold (temporary escrow hold). The wallet balance is never permanently debited until the upstream operator gateway returns an explicit SUCCESS telemetry code.
2. Automatic 30-Second Timeout Reversals (Rule 01)
Telecom networks occasionally experience carrier-side congestion or USSD bridge delays. If an upstream carrier gateway (Airtel, Jio, Vi, or BSNL) fails to deliver a deterministic execution confirmation within 30 seconds:
- The transaction is marked as failed due to timeout.
- 100% of the held balance is instantaneously unlocked and restored to your float ledger.
- No penalty fees, platform processing charges, or handling deductions are applied.
3. Operator Bridge Failures & Hardware Lockouts
If a Lapu SIM card encounters temporary operator downtime, insufficient carrier balance, or carrier rate throttling, the transaction dispatch engine safely fails closed. The system immediately rejects the order with HTTP 503 / 400 and automatically returns any reserved capital to the user wallet.
4. Double-Entry Ledger Stored Procedure Execution
All reversals execute through verified atomic database routines (automated secure refund). This guarantees double-entry ledger balance matching where every credit corresponds exactly to a recorded reversal row. There is zero risk of ghost balances or asymmetric deductions.
5. Disputed Recharge Verification & Inquiries
In rare scenarios where an upstream operator marks a recharge as SUCCESS but the end-subscriber reports non-delivery, merchants can lodge an inquiry via the Support desk quoting the unique Order Reference (Order Reference ID). Our NOC team cross-references the operator transaction number (UTR) with the carrier node within 24 business hours.
6. Cancellation Feasibility of Executed Orders
Due to the sub-second nature of automated cellular switching, a successful mobile recharge cannot be recalled or cancelled once accepted by the carrier network. Retailers and B2B clients must verify the destination 10-digit mobile number and circle denomination prior to submitting the API dispatch.