1.1.8 UPI Circle

UPI Circle enables a primary UPI user to authorize a secondary user to initiate UPI payments from the primary user’s bank account, with defined limits and permissions.

This feature supports shared payment access while keeping the primary user in control through configurable spending limits and approval requirements.

Key participants

• Primary User: The account owner who grants and manages permissions for a secondary user. PSP(P) represents Primary User PSP.
• Secondary User: A user authorized to initiate payments from the primary user’s account under defined controls. The secondary user may have their own UPI-linked bank account or may use UPI without linking a bank account, depending on the supported configuration. PSP(S) represents Secondary User PSP.

Authorization options

Full Delegate

The primary user sets a monthly spending limit for the secondary user. The secondary user can complete transactions independently within the configured limit.

Partial Delegate

The primary user approves each transaction initiated by the secondary user before the transaction is processed.

Purpose code for delegate payments

In the UPI payment system, delegate payments initiated using UPI Circle are identified using purpose code 87.

• UPI Circle (Partial Delegation) APIs
  UPI Circle partial delegation APIs allow a primary user to add, update, or remove a secondary user linkage, with transactions requiring primary user authorization as applicable. Responses are made available to the TPAP or channel through the query service.
• UPI Circle (Full Delegation) APIs
  UPI Circle full delegation APIs allow a primary user to add, update, or remove a secondary user linkage, with transactions authorized under an active mandate and applicable limits. Responses are made available to the TPAP or channel through the query service.