Overview

The Payments Report provides transaction-level payment data for every subscription payment event. Use this report to track payment statuses, understand failure reasons, access invoices, and monitor e-mandate details.

 Refresh Rate: Updates within 15 minutes

When to Use This Report

• Investigate payment failures and get specific failure reasons

• Download invoices for users (before 5-day expiry)

• Track e-mandate status and UMRN details

• Analyze payment methods and gateway performance

• Monitor debit trigger and response timelines

• Identify referrer-attributed subscriptions

Field Reference

User & Subscription Details

Field	Description
name	User name from subscription contact form
email	User email from subscription contact form
smallcase_name	Name of the smallcase
subscription_status	User's subscription status at time of payment
plan_type	AuM or Flat Fee
plan_duration	Duration of the plan (1m for all AuM plans)
auto_onetime	Whether user opted for auto-renewal
start_date	Subscription start date
end_date	Subscription end date

Payment Details

Field	Description
payment_method	UPI, Netbanking, Card, etc.
plan_amount	Plan amount (upfront amount for AuM cycles)
plan_charge_ratio	Charge ratio for AuM subscriptions
aum_fees	AuM fee charged for the cycle (AuM plans only)
payment_amount	Final amount paid after promo discounts
debit_trigger_date	Date on which payment debit was triggered
debit_response_date	Date of the latest debit response/status update
payment_status	Current payment status
payment_status_reason	Reason for payment status, if applicable
payment_gateway	Payment gateway used to process the payment

E-Mandate Details (Digio only)

Field	Description
mandate_id	E-mandate ID (Digio payment method only)
mandate_limit	Maximum limit of the mandate (Digio only)
mandate_status	Status of the e-mandate (Digio only)
umrn	Unique Mandate Registration Number (Digio only)

Offers & Attribution

Field	Description
referrer_name	Referrer attributed to this subscription, if any

Invoices

Field	Description
invoice_url	URL to subscription invoice PDF ⚠️ Expires 5 days after report generation
upfront_fee_invoice_url	URL to upfront fee invoice PDF ⚠️ Expires 5 days after report generation

Understanding Payment Status

payment_status Values

Status	Meaning	Action Required
PAID	Payment successfully collected	None
PENDING	Payment initiated but not yet confirmed	Monitor - may resolve automatically
FAILED	Payment attempt failed	Check payment_status_reason and reach out to user

Common payment_status_reason Values

When payment_status = FAILED, the payment_status_reason field provides details:

• Insufficient funds - User's account didn't have enough balance

• Bank declined - User's bank rejected the transaction

• Card expired - Payment card has expired

• Mandate cancelled - User cancelled the e-mandate

• Authentication failed - 2FA or OTP verification failed

• Technical error - Gateway or processing error

Working with Invoices

Invoice URLs

Two invoice types are available:

• invoice_url - Standard subscription invoice

• upfront_fee_invoice_url - Upfront fee invoice (AuM plans)

Critical: URLs Expire in 5 Days

• Invoice URLs are only valid for 5 days after the report is generated.

What's in an Invoice?

• Publisher's GSTIN

• Billing details (user name, PAN, state)

• Subscription description

• Fee breakdown (subtotal, IGST @18%, total)

• Invoice number and date

 Understanding E-Mandates (Digio)

• When payment_method = Digio, additional mandate fields are populated:

• Mandate_id

  • Internal identifier for the e-mandate created by the user.

• Mandate_limit

  • Maximum amount that can be debited through this mandate. Protects users from over-charging.

• Mandate_status

  • Current status of the mandate:

    • Active - Mandate is live and can be used for debits

    • Pending - Mandate created but not yet approved by bank

    • Cancelled - User or system cancelled the mandate

    • Expired - Mandate validity period has ended

• UMRN (Unique Mandate Registration Number)

  • National payment system identifier for the mandate. Used for tracking and reconciliation with NPCI.

 Common Use Cases

Investigate Payment Failures

• Filter: payment_status = FAILED

• Steps:

  • Check payment_status_reason for specific failure cause

  • Check payment_method and payment_gateway for patterns (e.g., specific gateway having issues)

  • Optionally reach out to user with specific failure reason and suggested resolution

Download All Invoices for a Date Range

• Filter: start_date or debit_trigger_date within your target range

• Action:

  • Export the report

  • Copy invoice_url and upfront_fee_invoice_url columns

  • Use a download script to fetch all PDFs within 5 days

  • Store locally for records

Analyze Payment Method Preferences

• Group by: payment_method

• Insights:

  • Which payment method is most popular?

  • Which method has highest failure rate?

  • Are UPI payments faster than Card payments (compare debit trigger vs response dates)?

Frequently Asked Questions

Q: Why can't I access an invoice URL?

• Invoice URLs expire 5 days after the report is generated. Re-download the Payments Report to get fresh URLs.

Q: What if payment_status stays PENDING for days?

• PENDING means the payment was initiated but not confirmed. If it stays PENDING for more than 2-3 business days, it likely failed or was abandoned but the gateway hasn't sent a final status yet. Treat as FAILED and reach out to the user.

Q: How do I find all payments from a specific user?

• Filter: email = [user email] or name = [user name]

• This will show all payment transactions for that user across all their subscriptions.

Q: What's the difference between plan_amount and payment_amount?

• plan_amount: Original subscription price (or upfront amount for AuM)

• payment_amount: Actual amount paid after applying offer discounts

• If there is no discount, they're equal.

Q: Why is aum_fees blank for Flat Fee subscriptions?

• The aum_fees field only applies to AuM-based subscriptions. For Flat Fee plans, all fees are captured in plan_amount.

Q: What if mandate_status shows "Cancelled" but the user is still subscribed?

• The user may have cancelled the e-mandate but paid for a particular subscription cycle. Check payment_method - if it's not Digio anymore, the mandate is no longer relevant.