Skip to main content
At any point during an active subscription, a merchant may need to collect an additional amount for an add-on feature or service. Instead of modifying the customer’s existing subscription, the merchant can use a Single Pay Invoice to collect this one-time amount. A Single Pay Invoice is useful when the additional charge is independent of the customer’s recurring subscription amount.

​
When to Use a Single Pay Invoice

A Single Pay Invoice can be used when:
  • A customer purchases an additional feature.
  • The merchant provides an additional service outside the subscription.
  • The customer purchases an add-on that should not become part of the recurring subscription.
  • The merchant needs to collect an additional one-time amount during an active subscription.
The customer’s existing subscription remains unchanged. The Single Pay Invoice is created separately for the additional charge.
To change the existing subscription with the additional charge, the merchant should update the subscription plan instead of using a Single Pay Invoice.

​
Business Use Case

Consider a customer subscribed to a SaaS platform with the following plan: The customer is already subscribed to the ₹999 monthly plan. During the billing period, the customer requests an additional storage package. The merchant wants to collect ₹500 for this add-on but does not want the ₹500 to become part of the customer’s recurring subscription. In this scenario, the merchant can create a Single Pay Invoice for ₹500.

​
Flow

​
Single pay on subscription API

Merchant can use this API to create a new invoice on an ACTIVE subscription, that can be shared with a customer.