# Special Rules Certain business categories may be classified as high-risk based on transaction behavior, industry type, regulatory exposure, dispute ratios, fraud patterns, settlement risks, or banking partner policies. High-risk merchants may be subject to additional operational, security, compliance, and payout controls to ensure platform stability and regulatory compliance. These rules help protect: * Banking infrastructure * Merchant operations * Customer transactions * Settlement systems * Regulatory obligations *** ## What is a High-Risk Merchant? A merchant may be categorized as high-risk due to factors such as: * High transaction volume * Elevated refund or chargeback ratios * Regulatory-sensitive industries * High payout frequency * International transaction exposure * Fraud-prone business models * Rapid transaction spikes * Unusual settlement patterns *** ## Examples of High-Risk Categories Examples may include: * Gaming platforms * Betting or fantasy systems * Forex-related services * International remittance services * Crypto-related businesses * High-volume digital services * Subscription-heavy platforms * Multi-level marketing systems * Adult-content related services * Aggregator payout systems Classification depends on: * Banking partner policies * Compliance review * Transaction behavior * Jurisdiction regulations *** ## Enhanced Verification Requirements High-risk merchants may require: * Extended KYC verification * Business ownership validation * Enhanced due diligence * Banking verification * Settlement review approval * Operational risk assessment Additional documentation may be requested during onboarding or periodic reviews. *** ## Transaction Monitoring High-risk merchant accounts may be monitored more aggressively for: * Unusual transaction spikes * Fraud indicators * Abnormal payout activity * High refund rates * Suspicious settlement behavior * Velocity anomalies Automated risk systems may temporarily: * Delay settlements * Restrict payouts * Trigger manual reviews * Require additional verification *** ## Payout Restrictions Additional payout controls may apply to high-risk merchants. Possible restrictions include: | Restriction | Description | | ------------------- | --------------------------------------------- | | Delayed Settlements | Settlement hold periods may apply | | Daily Payout Limits | Maximum payout caps may exist | | Rolling Reserves | Partial settlement reserves may be maintained | | Manual Review | High-value payouts may require review | | Geo Restrictions | Country-based payout controls may apply | *** ## Reserve Policies Certain merchants may be subject to reserve requirements. Reserve mechanisms help protect against: * Chargebacks * Fraud losses * Settlement disputes * Regulatory exposure Reserve types may include: * Rolling reserves * Fixed reserves * Delayed settlement reserves Reserve policies depend on: * Merchant category * Transaction history * Banking partner requirements * Risk profile *** ## Enhanced Security Requirements High-risk merchants should implement: * Strict IP whitelisting * Geo-restricted payout infrastructure * Multi-layer authentication * Advanced fraud monitoring * Webhook verification * Secure payout approval workflows KwikPaisa may require additional production security validation before activation. *** ## Infrastructure Recommendations Recommended infrastructure controls: * Dedicated production servers * Static public IP addresses * Country-specific payout infrastructure * Restricted administrative access * Audit logging systems * Real-time monitoring tools *** ## Compliance Requirements High-risk merchants may require: * Periodic compliance reviews * Transaction audit reports * Settlement reconciliation records * Regulatory reporting support * Source-of-funds verification * Beneficiary validation Failure to comply may result in: * Temporary restrictions * Settlement delays * Payout suspension * Account review *** ## Transaction Velocity Controls KwikPaisa risk systems may automatically monitor: * Transactions per minute * Payout frequency * Rapid balance movement * High-value transaction bursts * Unusual account activity Automated protection systems may temporarily: * Limit transactions * Pause payouts * Require manual review * Trigger enhanced verification *** ## Webhook & API Monitoring High-risk merchants should maintain: * Webhook audit logs * Transaction retry logs * API access monitoring * Security event tracking * Fraud detection systems Continuous monitoring is strongly recommended. *** ## Best Practices High-risk merchants should: * Maintain strong reconciliation systems * Validate all beneficiary details * Monitor fraud activity continuously * Review payout behavior regularly * Store detailed audit logs * Implement internal approval workflows *** ## Important Notes * Risk classification may change over time * Banking partner policies may vary * Additional controls may apply dynamically * Production access may require periodic review KwikPaisa reserves the right to: * Modify settlement policies * Adjust payout controls * Enforce additional compliance checks * Restrict unsupported business models based on operational, regulatory, or banking requirements. *** ## Recommended Production Controls KwikPaisa strongly recommends: ✅ IP Whitelisting\ ✅ Geo-Restricted Payout Access\ ✅ Webhook Verification\ ✅ Replay Attack Protection\ ✅ Idempotent Processing\ ✅ Audit Logging\ ✅ Fraud Monitoring\ ✅ Secure Credential Storage for all high-risk production merchants. *** ## Need Help? For high-risk merchant onboarding, settlement approvals, reserve policy discussions, payout enablement, or advanced compliance requirements, contact the KwikPaisa onboarding and risk management team. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://developers.kwikpaisa.com/v3-guide/high-risk-merchant-handling/special-rules.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.