Payment gateway, wallet recharge, coupon, fare, transaction status, webhook, refund, and receipt rules for MATO D2D checkout.
MATO D2D policy framework
This page explains the passenger, platform, payment, privacy, and journey rules that apply while using MATO D2D services.
Accepted payment modes
MATO D2D may support cards, UPI, net banking, wallets, payment gateway checkout, MATO Wallet balance, coupons, credits, and other modes enabled from time to time. Availability may differ by route, platform, passenger account, and provider status.
Gateway verification
A payment is considered successful only after secure gateway confirmation, signature verification, webhook validation, or trusted status check. A browser success screen alone is not final proof if server-side verification fails.
Fare and coupon validation
Displayed fare may include base fare, taxes, service charges, discounts, coupon reductions, wallet credits, and other applicable adjustments. Coupons, offers, memberships, and credits must be validated before payment or ticket release.
Ticket release
QR ticket, booking confirmation, seat inventory lock, and passenger journey record should be released only after payment is verified or an approved pay-later/business rule applies. Failed payments may release held inventory.
Wallet recharge
Wallet recharge is credited only after successful payment verification. Recharge may be restricted to supported limits, passenger account ownership, anti-fraud checks, and refund or chargeback rules.
Chargebacks and disputes
If a passenger raises a payment dispute, chargeback, or refund claim, MATO D2D may review booking records, payment references, boarding records, ticket usage, wallet ledger, and support history before taking further action.