What is a Merchant Account and why is it necessary?

Configure the engine to map real estate token plans/charges to the correct RBI/NPCI UPI purpose code in its product/payment settings.

When generating the UPI intent/collect request, auto-attach this purpose code into the transaction metadata sent to the PSP/gateway.

Persist the tagged code on the invoice, payment record, and settlement entries, and expose it in exports/reports to simplify audits and regulatory checks.

At the time of initiation, the engine should check the transaction category and amount against a real-time UPI limit master for Real Estate Token payments.

If eligible for a higher cap, it should show a dynamic in-app/checkout message confirming the enhanced limit before UPI intent creation.

This check for eligibility needs to be API-driven, configuration-controlled, and audit-logged for compliance.

The mobile app checkout should map real estate token transactions to the correct RBI/NPCI UPI purpose code in its payment configuration.

At UPI intent creation, this code must be auto-attached to the transaction metadata sent to the gateway.

The tagged purpose code should be stored with the payment record and settlement logs for audit and compliance.

Enable daily aggregate threshold alerts when total UPI collections for real estate tokens approach or cross RBI/NPCI caps.

Set project-wise and gateway-wise volume alerts to detect abnormal concentration of payments.

Configure exception alerts for sudden spikes, high failure rates, or reversal-heavy days for immediate finance review.

Have the app fetch the effective-dated UPI limit table (post–15 Sep 2025) from your backend for the real estate token category at checkout.

Before creating the UPI intent, compare token amount + any prior same-day token UPI payments against that category limit.

If it breaches, block the UPI option, show a clear higher-cap / fallback message, and log the decision with category + date for audit.