Collections FAQs

UPI Collections

The FAQs in this sub-section pertain to the UPI Collections module

1. Who can use UPI for collections?

Any Indian business entity can use UPI to facilitate ad-hoc or one-time payments from its customers, vendors or any other player in their business ecosystem.

2. What are the benefits of using UPI for collections?

There are multiple benefits of UPI for collections like coverage across banks, ubiquitous knowledge from a customer perspective and more importantly, seamless customer experience

3. What are the primary use cases for UPI-based collections?

UPI-based collections are extremely convenient in powering use-cases like purchases, loan repayments, investments, and insurance premiums and offline use-cases like QR-based collections.

4. What is the customer journey for UPI-based collections?

UPI requires the payer to have UPI enabled on their mobile through a TPAP/PSP app like PhonePe, Google Pay, PayTm, etc. Payers can pay through any one of the below flows.

UPI Deep links where the payment can happen from a specific UPI app on their mobile
Generic payment link where the customer can choose the UPI app of their choice
Collection Request where the payment can be done from a UPI app of the payer's choice
QR-based payment through any preferred PSP app

5. Do all Remitter Banks support UPI?

Yes. All commercial banks in India support UPI. The payer must register their account on a UPI app and use it to pay merchants offline or online.

6. Can the UPI collections stack be set up on a platform's business account/s?

Yes. Decentro can power UPI collections on a current or a similar business account where Decentro already has integrations.

7. What is the maximum amount that can be collected via UPI?

The maximum amount that can be debited via a single presentation depends on the PSP handle and the remitter bank (where the payer has a bank account). Typically, most banks support UPI debits of at least 1,00,000 INR/day, with some supporting higher limits.

8. How are the funds settled to the beneficiary?

Decentro settles the funds to the registered beneficiary's bank account as per standard settlement cycles as agreed upon at the time of onboarding.

9. Does Decentro require a platform to use a virtual account for UPI collections as well?

Yes. Decentro uses the virtual account stack as a ledger account to maintain collections across different modes and transaction types at a single place. The platform can choose to create one or more virtual accounts and map the payment link to be generated against it.

10. Can the platform create the payer handle as per their naming convention?

Decentro follows a standard naming convention to be compliant with statutory guidelines set by NPCI (which regulates UPI) and its partner bank. Typically, the trade name or the legal name of the platform/merchant can be present in the handle.

11. Does Decentro provide SDKs for UPI collections?

Yes. Decentro has an SDK for UPI intent flow and collect requests that can be embedded in an app and used to collect using UPI.

12. Can a platform create payment links or collect requests using the Decentro dashboard?

Yes. Decentro has a readily available capability to generate payment links and collection requests through its dashboard which is shared post being onboarded.

13. How does the platform get to know the status of a UPI collection?

Decentro triggers a transaction status callback Transaction Status] to a pre-configured endpoint after the payment link/collect request is approved or rejected by the payer. In addition, Decentro also provides a Status Check] capability to check the status of a collection.

14. How do UPI deep links differ from generic payment links?

UPI deep links have a protocol for the key UPI apps which can be used by the platform to display the same on their app and the payer can choose to pay from a specific app. A generic payment link, however, allows the payer to choose the app of their choice to pay from.

15. What is the meaning if a payment link status is 'Pending'?

Decentro passes back the status of a collection as 'Pending' in the Check Payment Status API if the link or collect request is not authorized by the payer.

16. Does Decentro trigger a callback if the platform uses the Status check capability?

Decentro triggers a transaction status callback and account balance callback to the configured endpoints if a status check is done after the callback is triggered.

17. What is the minimum amount that can be collected via UPI?

The minimum amount to use UPI collections API is INR 5. Amounts less than INR 5 will not be supported either in the payment link or collection request.

The FAQs in this sub-section pertain to the ENACH capability of Decentro.

ENACH

1. Who can use NACH for payments?

Any Indian business entity can use NACH to facilitate recurring payments from its customers, vendors or any other player in their business ecosystem. This is in addition to regulated use cases like lending, investments, insurance, etc.

2. What are the benefits of using NACH for payments?

NACH-based payments are very convenient when you expect to collect payments frequently over a long period, either at specified intervals or Adhoc for specific scenarios. Customers do not need to approve a transaction every time, which reduces operational overheads and the risk of a payer not paying on time, etc.

3. What are the primary use cases for NACH-based payments?

NACH-based payments are extremely convenient for recurring payments like EMIs, subscriptions, expenses, etc. NACH settlement takes 1-2 working days but has higher amounts than UPI transactions. The payer cannot cancel, which is a major benefit in lending use cases.

4. What is the process flow for NACH-based payments?

NACH requires a customer (business or individual) to authorize a mandate digitally or physically once by providing bank account details. Once the registration is successful, the platform can collect payments into their account through Decentro's platform.

5. How can the NACH mandate be set up?

NACH mandates can be set up digitally if the customer’s bank supports either a Debit Card or Netbanking. Alternatively, the customer can authorize a mandate form offline by signing as per bank records. Decentro is also working to power the registration through Aadhaar-based e-sign.

6. What is the difference between physical and ENACH?

ENACH, also known as digital mandates, is done via API and facilitated fully digitally at the time of registration. On the other hand, physical NACH requires customers to sign the NACH form, which can be time-consuming, has much higher rejection rates, and requires considerable operational efforts.

7. What is the maximum amount that can be deducted via NACH?

The maximum amount that can be debited via a single presentation depends on the amount and the frequency of the mandate registered. However, multiple presentations can be done if the amount to be debited is higher than the registered amount.

ENACH supports maximum registration as well as debit up to 1CR.

8. Do all Banks support NACH?

NACH is supported by all the commercial banks that operate a payment system in India. The list of supported banks is here.

However, ENACH is supported by a specific set of banks ONLY. The list of banks live and at different stages of integration with NPCI can be found here.

9. What is the benefit of ENACH over physical NACH?

ENACH supports quick registration confirmation, does not require manual intervention like a physical NACH, and has much lower rejection rates than physical NACH due to issues like a signature mismatch. This is in addition to transaction limits of up to 1CR.

10. Does the platform need to create a new utility code?

The platform can create a new utility code through Decentro or move an existing utility code to Decentro. Decentro will help the platform with the process and ensure a smooth and seamless go-live from an operational and technical perspective.

Registration

1. Can the ENACH mandate be set up on business accounts?

Yes. Most banks that support ENACH allow registration where the current account is not a 2-FA account.

2. Does the platform need to open a new bank account for ENACH?

No. The platform can piggyback on Decentro’s PA escrow to collect payments, which is permissible per PA guidelines from RBI. However, if you prefer to have the collections done directly to your account, you must set up a bank account with the banking partners Decentro supports.

3. Can NACH registration fail for any reason?

Yes. ENACH registration can fail for many reasons, such as invalid account information, insufficient balance, blocked account, etc. This is in addition to scenarios like invalid netbanking credentials, debit card details, or an invalid OTP being entered.

Physical NACH registration primarily fails due to a signature mismatch between the mandate form and the bank account, insufficient funds, etc. In addition, physical NACH can also fail due to any beneficiary bank checks that are put in place by them.

5. What is the maximum period for which a NACH can be registered?

ENACH or even physical NACH can be registered for 40 years only. The platform needs to pass the end date in the request payload. The guidelines issued by NPCI on their website.

6. Is an end date mandatory for registration?

Yes. Remitters can no longer register a mandate as ‘Until Cancelled’ and must give a clear end date at the time of registration as per NPCI guidelines.

7. Is it possible to customize the mandate registration screen?

Decentro allows the platform to customize its UI template before redirecting to the NPCI portal, where actual bank account details are entered. Decentro, however, cannot customize the NPCI screen.

8. What is the maximum amount that can be deducted via NACH?

NACH supports registration up to 1CR.

9. In what ways can a payer register a mandate?

Decentro powers ENACH through the below modes of authentication.

Debit Card
Netbanking

Decentro is also working on the Aadhaar-based mandates, which will be rolled out shortly.

10.What does cancellation of a mandate mean?

Cancellation of a mandate results in the entire mandate being canceled and all subsequent presentations getting blocked. Cancellation can only be made by the payee, typically in lending-related usecases. Cancellation of a mandate cannot be undone, and the payer needs to register a new mandate.

11.What does amendment of a mandate mean?

Amendment of a mandate is done if there’s any change in the parameters like amount, frequency, date, etc. This is done in case there’s any change in the loan amount, tenure, etc. Amendment of a mandate requires the payer to go through the same experience as the registration flow.

12.What does the "Fixed" amount rule mean for mandates?

The "Fixed" amount rule means that the debit amount must be exactly the specified amount. The system will not allow debits that are more or less than this specified amount.

13.What does the "MAX" amount rule mean for mandates?

The "MAX" amount rule means that the debit amount can be less than or equal to the specified amount, but it cannot exceed the specified amount. This provides flexibility for debiting up to the specified limit.

Presentation

1. How do we handle Adhoc presentations using NACH?

NACH - physical or ENACH, allows the platform to set up payments with predefined frequency or Ad Hoc. By setting the frequency to Adhoc, the platform can present a mandate per the business requirements.

2. Can NACH facilitate instant settlements?

No. Unlike UPI or IMPS, NACH is designed to facilitate recurring payments of higher value. The payments take one working day to reflect in the credit account.

3. Can we present different amounts for each presentation?

Yes. Decentro allows the platform to present different amounts for each presentation if the mandate is registered with the amount type as 'Maximum.'

4. Can Decentro settle into any bank account after the presentation?

Decentro settles the funds to the relevant beneficiary based on the use case, which the platform will share before going live and after Decentro has approved the same after its due diligence.

5. Can Decentro settle to multiple bank accounts at an execution level?

Yes. Decentro allows the platform to settle funds into multiple bank accounts. However, this will be subject to the use cases and must comply with the guidelines.

6.Does the platform need to trigger any pre-debit notifications through Decentro?

No. ENACH/NACH requires the client to inform the payer of the debit at least 24 hours before the actual debit. This can be undertaken by the platform by communicating to the payer through SMS and/or email or any other standard modes of communication like Whatsapp or in-app notifications.

UPI Autopay FAQs

The FAQs in this sub-section pertain to the UPI Auto-pay/UPI 2.0 capability of Decentro.

Overview

1. Who can use UPI Auto-pay for payments?

Any Indian business entity can use UPI to facilitate recurring payments from its customers, vendors or any other player in their business ecosystem. This is in addition to regulated use cases like lending, investments, insurance, etc.

2. What are the benefits of using UPI-based payments?

UPI-based payments are very convenient when you expect to collect payments frequently over a long period, either at specified intervals or Adhoc for specific scenarios. Customers do not need to approve a transaction every time, which reduces operational overheads and the risk of a payer not paying on time, etc., and the experience is seamless.

3. What are the primary use cases for UPI-based mandates?

UPI-based mandates are extremely convenient for recurring payments like EMIs, subscriptions, investments, savings, expenses, etc. UPI settlement takes 1-2 working days, but the payer cannot cancel, a major benefit in lending use cases.

4. What is the process flow for UPI-based payments?

UPI Auto-pay requires a customer (business or individual) to authorize a mandate digitally or physically once by providing a VPA or authorizing it from a preferred UPI app of the payer. Once the registration is successful, the platform can collect payments into their account through Decentro's platform.

5. How can the UPI mandate be set up?

UPI mandates can be set up digitally using any leading UPI apps like Phonepe, GPay, Paytm, Amazon Pay, etc. Once set up, the platform can debit funds regularly with minimal hassles.

6. What is the difference between UPI and UPI Auto-pay?

UPI Auto-pay is built on top of the UPI platform and is designed to cater to recurring collection use cases where the payer doesn't have to authorize a transaction every time, unlike UPI.

7. What is the maximum amount that can be deducted via UPI Auto-pay?

The maximum amount that can be debited via a single presentation without any additional authorization by the payer is 15,000, as per guidelines. However, with additional authorization through the UPI MPIN, the platform can receive up to 1L.

8. Do all Banks and PSPs support UPI Auto-pay?

UPI Auto-pay is supported by all the leading PSPs and banks in the country. The complete list can be found here.

9. What is the benefit of UPI Auto-pay over ENACH?

UPI auto-pay is designed for a seamless registration flow with no manual intervention for debits up to 15K. In addition, UPI Auto-pay's coverage is also much more expansive compared to ENACH due to it being part of the UPI ecosystem.

Registration

1. Can the UPI based mandate be set up on business accounts?

Yes. Most banks that support UPI mandates allow registration where the current account is not a 2-FA account. UPI-based mandates can power any bank account linked to a UPI.

2. Does the platform need to open a new bank account for UPI Auto-pay?

No. The platform can piggyback on Decentro’s platform to collect payments, which is permissible per PA guidelines. However, if you prefer to have the collections done directly to your account, you must set up a bank account with the banking partners Decentro supports.

3. Can mandate registration fail for any reason?

Yes. UPI mandate registration can fail for many reasons like invalid MPIN, insufficient funds or an issue with the remitter bank.

4. Does the platform need to create a new VPA?

The platform can create a new utility code through Decentro. Decentro will onboard the platform and generate a VPA to ensure a smooth and seamless go-live from an operational and technical perspective.

5. Can the payer choose any UPI app for registration?

Yes. If they use the intent flow, the payer can choose the UPI app of their choice, and the platform just has to create a mandate registration request.

6. What is the maximum period for which a UPI Autopay can be registered?

ENACH or even physical NACH can be registered for a maximum period of 30 years. This is covered in the guidelines issued by NPCI here.

7. Is an end date mandatory for registration?

Yes. Remitters can no longer register a mandate as ‘Until Cancelled’ and must give a clear end date at the time of registration as per NPCI guidelines.

8. Is it possible to customize the mandate registration screen?

Decentro allows the platform to customize its UI template before redirecting to the NPCI portal, where actual bank account details, etc, are entered. Decentro, however, cannot customize this screen.

Presentation

1. How do we handle Adhoc presentations using Autopay?

Autopay, allows the platform to set up payments with predefined frequency or Ad Hoc. By setting the frequency to Adhoc, the platform can present a mandate per the business requirements.

2. Can NACH facilitate instant settlements?

No. NACH, unlike UPI or IMPS, is designed to facilitate recurring payments of higher value. The payments take one working day to reflect in the credit account.

3. Can we present different amounts for each presentation?

Yes. Decentro allows the platform to present different amount for each presentation if the mandate is registered with the amount type as 'Maximum'.

4. Can Decentro settle to any bank account after presentation?

Yes. Decentro settles the funds to the relevant beneficiary basis the use-case, which the platform will share before going live.

5. Can Decentro settle to multiple bank accounts at an execution level?

Yes. Decentro allows the platform to settle funds into multiple bank accounts. However, this will be subject to the use cases and must comply with the guidelines.

FAQs - Netbanking

This section outlines some of the most important FAQs pertaining to the Netbanking module. If you have any other queries, please reach out to us at [email protected].

The FAQs in this section pertain to the Netbanking module and its APIs:

Generate Netbanking Dynamic QR
Generate Netbanking Intent Link
Generate Netbanking Web Redirection Link (Netbanking 1.0)
Get Netbanking Transaction Status
Netbanking Terminal Transaction Status Callback/Webhook

What is Netbanking as a collection mode on Decentro?

Netbanking allows platforms to collect funds from payers directly through the payer's bank app, without requiring a UPI app or a virtual account transfer. It is part of Decentro's broader Collections suite and lets payers authorize payments using their preferred bank's netbanking credentials or bank app.

What are the different modes supported under Netbanking?

Decentro supports three distinct Netbanking collection modes:

QR Code – Best suited for Desktop Web and offline POS use cases. Displays a QR code that the payer can scan using any supported bank app.
Intent Link – Best suited for Android and iOS mobile apps. Invokes the bank applications installed on the payer's device.
Redirection (Netbanking 1.0) – Best suited for both desktop and mobile devices. Redirects the payer directly to the specific bank's netbanking portal for login and authorization.

Which banks are supported for each Netbanking mode?

Bank coverage currently differs by mode:

QR Code: HDFC, AXIS, and YES Bank (iOS and Android), plus ICICI Bank (Android only).
Intent Link: HDFC, AXIS, and YES Bank (iOS and Android), plus ICICI Bank (Android only).
Redirection: HDFC (HDFC), ICICI Bank (ICIC), Yes Bank (YESB), AU Small Finance Bank (AUBL), State Bank of India (SBIN), AXIS Bank (UTIB), and Federal Bank (FDRL).

Since bank coverage evolves, please check the latest supported bank list on the respective QR, Intent Link, and Redirection API reference pages, or confirm with your Decentro CSM.

What is the standard flow for a Netbanking transaction?

The Netbanking process follows a standardized lifecycle across all three modes:

The platform calls Decentro's Netbanking API (QR, Intent Link, or Redirection) with the consumer_urn, amount, reference_id, expiry, and purpose_message.
Decentro responds with a decentro_txn_id and a short_link_url/shorten_link_url, with the transaction initially marked PENDING.
The payer authorizes the payment by scanning the QR, opening the intent link, or logging into the netbanking portal.
Decentro sends a Terminal Transaction Status Callback/Webhook with the final status, or the platform can poll the Get Transaction Status API.

What are the key request parameters common to all three Netbanking APIs?

All three APIs (QR, Intent Link, Redirection) require:

reference_id – a unique ID assigned by the platform for every API request (5–50 characters, must be unique per request).
consumer_urn – the unique identifier assigned by Decentro during onboarding.
amount – the transaction amount to collect (minimum ₹1.00, up to two decimal places).
expiry – time in minutes after which the link/QR expires.
purpose_message – narration shown for the transfer (must be under 50 characters).

Optionally, all three support amount name/value breakup pairs and a redirect_url for where the payer lands after the payment session.

What is the maximum expiry time I can set for a Netbanking link or QR?

The maximum expiry for any mode cannot exceed 15 minutes.

Why is device_type required for the Intent Link API but not for QR or Redirection?

device_type (ANDROID, IOS, or DESKTOP) tells Decentro how the intent link should behave once opened, since Android and iOS handle app invocation differently. QR and Redirection don't need this parameter since they aren't tied to opening a native app on the device.

Why is bank_code mandatory for Redirection and iOS Intent Links, but optional for Android Intent Links?

For Redirection, bank_code is always mandatory since the API needs to know which bank's netbanking portal to redirect the payer to.
For Intent Link on Android, bank_code is optional — if omitted, the link opens an app drawer showing all bank apps that support Netbanking 2.0, letting the payer choose. If passed, the platform can direct the payer straight to a specific bank app.
For Intent Link on iOS, bank_code is mandatory, since iOS does not support a generic app-chooser drawer; Decentro needs the bank code to append the correct bank URI and redirect the payer to that specific app.

Can I break up the transaction amount into components (like fees, taxes, etc.)?

Yes. Across all three modes, you can optionally pass an amount breakup using name (describing the charge) and value (the specific breakup amount) fields. The sum of all breakup values must equal the total transaction amount.

What does the redirect_url parameter do?

redirect_url (supported on QR and Redirection APIs) lets you specify a custom URL where the payer is redirected after their payment session ends. Only HTTPS URLs are accepted.

How do I know the status of a Netbanking transaction?

Decentro triggers a Terminal Transaction Status Callback/Webhook to your pre-configured endpoint once the payer authorizes (or fails to authorize) the transaction. Alternatively, your platform can proactively poll the Get Transaction Status API using the decentro_txn_id.

What does a 'PENDING' status mean for a Netbanking transaction?

A transaction is marked PENDING as soon as Decentro generates the short link/QR/redirection URL. It remains in this state until the payer completes authorization at their bank app, after which Decentro updates it to a terminal status via callback.

What are the possible terminal statuses for a Netbanking transaction?

Based on the callback payload, a transaction can settle into one of the following states: SUCCESS, FAILED, EXPIRED. The transaction_attempt_status field (for individual attempts) can additionally show HOLD.

How many times does Decentro trigger the Terminal Transaction Status Callback?

Decentro triggers this callback up to 3 times per transaction. It is fired only when the transaction status moves to one of SUCCESS, FAILURE, or EXPIRED.

How should my platform acknowledge the callback, and what happens if I don't?

Your platform must acknowledge receipt of the callback by responding with CB_S00000. If any other value (or no valid acknowledgment) is returned, Decentro will retrigger the callback.

What if my platform can't process the callback at all?

If your endpoint is unable to acknowledge or handle the callback, you can always fall back to actively checking the transaction status using the Get Transaction Status API with the decentro_txn_id.

How do I identify which Netbanking mode (QR, Intent, or Redirection) a given transaction used?

Both the callback and the Get Transaction Status response include an initiation_type field, which indicates whether the transaction was completed via INTENT, QR, or REDIRECTION.

Should I rely on callbacks, polling, or both?

Decentro recommends relying primarily on the webhook/callback for real-time updates, since it's triggered automatically once the transaction reaches a terminal state. Use the Get Transaction Status API as a fallback — for example, if a callback wasn't received/acknowledged, or the transaction has remained PENDING longer than expected.

What should I do if a Netbanking transaction stays in 'PENDING' for a long time?

Poll the Get Transaction Status API using the decentro_txn_id. If the status still doesn't resolve, please reach out to [email protected] or your dedicated customer success representative with the transaction details.

What is bank_reference_number and when is it available?

bank_reference_number is the unique transaction reference number issued by the remitting bank. It is returned in both the Get Transaction Status response and the callback payload, but it will not be propagated in EXPIRED and certain FAILED scenarios.

How is Netbanking different from UPI collections?

UPI collections require the payer to have a UPI app (like GPay, PhonePe, PayTm) linked to their bank account. Netbanking, on the other hand, lets the payer authorize payment directly via their bank's netbanking portal or bank app login, which is useful for payers who prefer not to use UPI or don't have a UPI-enabled account.

Can Netbanking be used for both mobile and desktop journeys?

Yes. QR Code is best suited for desktop web/offline POS, Intent Link is built specifically for Android and iOS apps (when opened in desktop, it behaves exactly like QR), and Redirection works across both desktop and mobile devices — giving platforms flexibility to choose the right mode per channel.