1. Nature of the Wallet
The Wallet is a closed-loop running account maintained in Slenpay’s books. It records the rupee value of advances an Agent has paid to Slenpay and not yet applied towards Platform services. It is not a bank account, not a deposit insured by DICGC, and not a Reserve Bank of India authorised prepaid payment instrument unless Slenpay later publishes such an authorisation.
- Denomination: Indian Rupees Only.
- Purpose: solely to pay Slenpay for catalogue transactions (tickets, premium posting, enabled products, and Platform fees).
- Interest: No interest is payable on Wallet balance unless a separate written scheme says so.
- Transfer: Balance is not transferable to another Agent, Customer, or third person, except an approved Super-Distributor credit under clause 7.
- Third-Party Payments: Balance cannot be used to pay a third party directly.
2. Loading the Wallet
The Agent refills the Wallet only by methods enabled on the dashboard:
- UPI, IMPS, NEFT, or RTGS from a bank account held in the same name and PAN as the Agent KYC;
- A payment-gateway load-order generated in the Agent interface;
- A transfer from a mapped Super-Distributor Wallet, if that programme is enabled;
- Any other electronic method Slenpay notifies in writing.
Default rule: cash is not an accepted method to load the Wallet. The Agent may collect cash from a Customer, but the Wallet is loaded only electronically from the Agent’s own account.
A load is complete only when Slenpay’s payment partner or bank reconciliation credits the Wallet ledger. Minimum and maximum load amounts and velocity caps will be shown on the dashboard and may differ by risk tier. Loads that fail name-match, arrive from a third-party account, appear structured to evade caps, or are flagged by AML rules may be rejected.
The Agent shall not ask a Customer to transfer money to Slenpay’s account or to a staff member’s personal account in order to load the Wallet.
3. The Collect–Refill–Issue Loop
| Step | Rule |
|---|---|
| 1. Collect from the Customer | The Agent collects cash or other value under the Agent’s own arrangement with the Customer. That collection is not a Slenpay receipt. |
| 2. Confirm Wallet Balance | Balance must be equal to or greater than the net payable. If not, the Agent refills the Wallet from the Agent’s own bank, UPI, or Super-Distributor. |
| 3. Issue on the Platform | The Agent enters accurate passenger, policy, or application data and confirms. The Platform debits the Wallet and requests the Supplier. One debit maps to one reference. |
| 4. Deliver Proof | The Agent hands over the Platform confirmation and a receipt that prints the Agent Venue. |
| 5. Repeat | As balance falls, the Agent refills and continues. Slenpay does not extend float unless a signed credit addendum exists. |
Skipping step 2 is a breach. Using a Customer’s payment instrument as the source of a Wallet load is a breach.
4. Issuance Conditions
- Valid, unsuspended Agent session.
- Wallet balance at least equal to the net payable (Supplier fare plus taxes plus Platform fee, minus any instant commission configuration).
- Passenger names matching travel-document rules, and a contact mobile that can receive the PNR.
- No velocity-limit breach.
- Supplier inventory still available at click-time.
A travel service is issued when the Supplier PNR or ticket number is generated. An insurance premium is posted when the biller or insurer acknowledgement, or Slenpay’s success receipt, is generated. Until then, a Wallet debit is a pending fulfilment and will be auto-reversed if fulfilment fails, typically the same day to T+2.
The Agent is responsible for name spelling, age band, GSTIN claimed by the Customer, and policy number. Slenpay is not obliged to absorb a Supplier change fee caused by the Agent’s data error.
5. Commission
Commission, if any, is calculated as per the rate card on the dashboard or a signed commercial annex.
It may be netted at the time of debit or accrued to a commission ledger and paid to the Agent’s verified bank account on the cycle shown on the dashboard, after clearance. Slenpay may withhold commission against suspected fraud, chargebacks, Supplier debit memos, or unresolved Customer complaints.
Commission already paid may be clawed back by Wallet debit or payout set-off if the ticket is cancelled, the Supplier raises a debit memo, or the booking is proven fraudulent.
6. After-Issue Changes and Customer Settlement
Date change, cancellation, and refund follow the public Refund, Cancellation and Chargeback Policy and the Supplier fare rules.
Supplier refunds on Agent-issued tickets are credited to the issuing Agent’s Wallet. The Agent must settle the Customer within three working days of that Wallet credit, unless the fare was sold as non-refundable and that fact was disclosed before the Customer paid.
7. Super-Distributor
If Slenpay enables a two-tier network, a Super-Distributor may transfer Wallet value to mapped downline Agents. That transfer is an internal commercial allocation of advance between two KYC’d Agents. It is not a payment system for the public.
A Super-Distributor shall not take cash from the public “for Slenpay” and shall not advertise guaranteed returns for loading downline Wallets. Slenpay may cap, reverse, or freeze a transfer that appears to be layering or unauthorised deposit-taking.
Downline KYC remains Slenpay’s to approve.
8. Optional Credit Addendum
If Slenpay later offers a temporary issuance limit above Wallet balance, that facility is trade credit to the Agent, not a consumer loan to the Customer.
It requires a separate signed addendum stating limit, tenure, fee if any, and immediate stop-issuance on default. Until that addendum exists, the Wallet cannot go negative.
9. Dormancy
If the Wallet and Agent ID have no successful load or issuance for twelve consecutive months, Slenpay may mark the account dormant, freeze issuance, and after thirty days’ notice refund eligible balance to the last verified bank account or handle it as unclaimed under applicable law.
10. Records
The Wallet ledger on the Platform is prima facie evidence of loads, debits, commission, and reversals, subject to demonstrated system error. Agents should download statements. Ledger data is retained as described in the Privacy Policy.
11. Contact
Agent Operations:
support@slenpay.co.in
Subject: “Agent Support”
Grievance Officer Name: Kumar
Designation: Grievance Officer
Grievance Officer Email ID: grievance@slenpay.co.in
Grievance Officer Mobile No. : +91 93818 30014